Building a Cannabis Use Disclosure Protocol for Your Surgical Department

For department chairs, perioperative service line leaders, and quality officers, cannabis use screening is increasingly a operational priority — not because it requires a new clinical specialty, but because inconsistent intake and documentation create variability in care that quality metrics and patient safety reviews are starting to surface. This article outlines a practical approach to building a cannabis disclosure protocol for your surgical department.

The case for a department-level protocol

Individual clinicians asking about cannabis use ad hoc produces individual results. A department protocol ensures that every patient entering your surgical pathway is asked the same core questions, that answers are documented in structured fields, and that findings reach the anesthesiologist and surgeon before the day of surgery — when there is still time to adjust plans and set expectations.

[VERIFY] Quality improvement literature in perioperative medicine consistently identifies standardized intake processes as a lever for reducing unwarranted clinical variation. Cannabis use screening fits this pattern: the clinical response may differ by patient, but the question should not differ by provider.

Step 1 — Align stakeholders before writing the form

A disclosure protocol touches anesthesia, surgery, preoperative nursing, pharmacy, and health information management. Before drafting intake questions, convene representatives from each group to agree on:

• Which screening fields are required vs. optional
• Where data lives in the EHR (and who can view it)
• What triggers a flagged review vs. routine documentation
• How findings appear in the anesthesia preoperative evaluation
• Who owns protocol updates and staff training

Without this alignment, even a well-designed form will be bypassed or documented inconsistently.

Step 2 — Design intake questions that capture actionable data

Effective screening questions are specific enough to inform clinical conversations but do not embed institutional clinical thresholds in the intake itself. Recommended core fields:

• Current cannabis use (yes/no/prefer not to answer)
• Frequency category (daily / weekly / occasional / former user)
• Primary route (inhaled, oral, topical, other)
• Last use (date or relative timeframe as reported — not auto-converted to policy)
• Product type (THC, CBD, both, unsure)
• Medical cannabis card holder (yes/no, if applicable in your state)

Avoid yes/no questions alone — "Do you use marijuana?" without follow-up produces binary data that is rarely actionable. Layered questions with skip logic improve both disclosure and documentation quality.

Step 3 — Build documentation and handoff standards

Screening data should flow automatically into:

• The anesthesia preoperative note template
• The surgical team's preoperative briefing
• Postoperative pain service consult triggers (if your institution uses them)
• Patient-facing preoperative education materials

Define what happens when a patient reports active daily use vs. occasional use at the workflow level — not as a fixed clinical directive, but as a communication standard (e.g., "daily use triggers anesthesia attending review before day of surgery"). The specific clinical response remains at the discretion of the treating team and institutional policy.

Step 4 — Train staff and measure compliance

Roll out the protocol with brief, role-specific training:

• Preoperative nurses: How to ask non-judgmentally, how to document, when to escalate.
• Anesthesia: How to locate screening data in the EHR, how it integrates with existing preoperative evaluation workflows.
• Surgery: How screening findings appear in the surgical record and preoperative huddle.

Measure compliance with chart audits: percentage of surgical cases with completed cannabis screening fields, time from screening to anesthesia review when flagged, and patient-reported clarity about preoperative substance use conversations. Review metrics quarterly and update the protocol based on findings.

Step 5 — Pair the protocol with decision support

Screening generates data; decision support helps teams organize perioperative considerations consistently. Reference tools that map reported use patterns to the three standard domains — bleeding considerations, anesthesia planning, and postoperative pain management — reduce the cognitive load on individual clinicians without replacing judgment or institutional guidelines.

For the clinical framework underlying these domains, see Perioperative Cannabis Use: A Framework for Surgical Teams.

Implementation timeline and common pitfalls

A realistic rollout takes one to two quarters: stakeholder alignment (weeks 1–4), EHR build and testing (weeks 5–10), staff training (weeks 11–12), and phased go-live with audit feedback (ongoing). Common pitfalls include building the form before aligning anesthesia workflow, failing to train day-of-surgery staff who re-verify history, and not connecting screening data to postoperative pain handoffs.

Start with a single service line or procedure category if a department-wide rollout feels too large — prove the workflow on a defined population, then expand.