Overdose scenes are where systems either work together or fracture in public view. Counties expanding harm reduction and overdose prevention systems need public safety protocols that prioritize life-saving response while preserving the trust that makes community-based SUD service models accessible. The operational goal is not âno law enforcement involvementâ or âlaw enforcement leads,â but a governed partnership model: clear scene roles, non-interference commitments, privacy limits, and measurable accountability so overdose response does not drift into deterrence-by-fear.
What partnership protocols must accomplish in real operations
Partnership protocols should reduce three predictable failure patterns. First, scene confusion: unclear authority, duplicated actions, or delays while roles are negotiated in the moment. Second, trust collapse: people avoid calling 911 or disengage from outreach because they expect punitive consequences. Third, data misuse: information gathered in a health context is inappropriately repurposed, undermining engagement and exposing agencies to legal and reputational risk.
Oversight expectations counties must design for
Expectation 1: Documented Good Samaritan and non-interference alignment. Oversight bodies increasingly examine whether local practice aligns with state protections and county policy, including whether on-scene behaviors discourage help-seeking.
Expectation 2: Clear governance and auditability of interagency practice. Counties must be able to show how the partnership works: who does what, when outreach is invited, what data is shared (and what is not), and how exceptions are reviewed and corrected.
Partnership design principles that keep the system credible
Define âlife safety firstâ roles with a written boundary. EMS leads medical response. Law enforcement role should be explicitly limited to scene safety and traffic control unless specific, documented threats exist. Outreach roles should focus on post-stabilization engagement and follow-up options, not interrogation or evidence gathering.
Separate public health operations from enforcement data flows. If counties expect people to engage with outreach and accept follow-up, they must clearly define what information is collected, who can access it, and what it will never be used for.
Build escalation rules for real risk. Protocols must still address violence risk, weapons, or unsafe environments. The key is that escalation is structured, documented, and proportionateârather than defaulting to broad enforcement posture at every overdose scene.
Operational Example 1: Overdose scene role protocol with non-interference safeguards
What happens in day-to-day delivery. The county adopts a scene protocol used by dispatch, EMS, and law enforcement. Dispatch codes overdose calls with a âmedical leadâ designation. EMS arrives and leads clinical care. Law enforcement presence, if dispatched, is limited to scene safety (for example, traffic management, crowd control) and is explicitly instructed not to question the patient about substances, not to run warrant checks related to the overdose event absent an independent safety justification, and not to seize personal items unless required by clearly defined safety rules. After stabilization, a trained outreach responder (peer or navigator) can be requested to provide naloxone reinforcement, safer use supplies information, and voluntary follow-up options.
Why the practice exists (failure mode it addresses). The failure mode is predictable: inconsistent on-scene behavior creates fear, people stop calling for help, and overdose risk increases. Non-interference safeguards reduce that chilling effect while still preserving scene safety.
What goes wrong if it is absent. Practice varies by shift, officer, and location. Communities experience mixed messages: âcall for helpâ campaigns conflict with punitive interactions. People using alone or in hidden locations become more likely to delay calling 911, leading to preventable deaths and higher-acuity clinical emergencies.
What observable outcome it produces. A governed role protocol increases willingness to call 911 (often evidenced indirectly through earlier call times, higher bystander involvement, and increased EMS reversals before respiratory arrest). QA can track complaint patterns, scene escalation events, and adherence to non-interference instructions documented in incident reports.
Operational Example 2: Post-scene outreach engagement pathway that is voluntary, fast, and measurable
What happens in day-to-day delivery. After a non-fatal overdose, EMS offers an opt-in follow-up pathway: the person can accept outreach contact using a preferred method (phone, text, meet-up location) or can accept information without sharing contact details. If contact is accepted, the referral is sent through a secure channel to an outreach team with a defined response window (for example, within 24â48 hours). Outreach follows a structured script: naloxone resupply confirmation, safer use planning, and options for MOUD or other supports. The system logs referral status changes (sent, acknowledged, contact attempted, contact made, next step scheduled) using coded outcomes rather than detailed narratives.
Why the practice exists (failure mode it addresses). The immediate post-overdose period is high risk for repeat events. The failure mode is that no one owns the âafterâ period, and follow-up is either absent or treated as coercive, leading to refusal and disengagement.
What goes wrong if it is absent. Counties rely on generic advice and assume people will self-navigate complex services after a traumatic event. Repeat overdoses rise, and the system cannot prove whether outreach offers were made, accepted, or completed. Public safety partners may then push for deterrence-based tactics, accelerating trust collapse.
What observable outcome it produces. A voluntary, closed-loop follow-up pathway increases contact completion rates and naloxone resupply confirmation after overdose. Evidence includes time-to-contact measures, closed-loop referral completion, and reductions in repeat overdoses among people successfully contacted (tracked through de-identified linkage where permitted).
Operational Example 3: Data-sharing limits and audit rules that protect trust and enable oversight
What happens in day-to-day delivery. The county establishes a written data boundary agreement: outreach and public health follow-up data is not accessible to law enforcement systems for enforcement purposes. Only minimum necessary information is shared for coordination (for example, referral timestamp, general location category, and coded outcome status). Access to any identifiable follow-up record is role-based and logged. A quarterly audit reviews a sample of referrals to confirm that data sharing followed policy, that access events were appropriate, and that any exceptions were documented with justification and corrective action.
Why the practice exists (failure mode it addresses). People avoid engagement when they believe their information will be used against them. The failure mode is data drift: information collected for care coordination gets repurposed or accessed inappropriately, even unintentionally, undermining trust across entire communities.
What goes wrong if it is absent. Outreach teams become perceived as an extension of enforcement. Engagement drops, services lose visibility of risk, and overdose prevention becomes less effective. Counties also face oversight risk when they cannot demonstrate data governance or explain access patterns.
What observable outcome it produces. Clear data limits preserve engagement and reduce privacy incidents. Evidence includes audit results (low inappropriate access rates), sustained follow-up acceptance rates, and fewer community complaints or refusals tied to fear of enforcement-related data use.
Assurance mechanisms that keep partnerships stable over time
Joint training with scenario practice. Tabletop exercises and ride-alongs help align behaviors across agencies, especially around non-interference rules and when escalation is justified.
Incident review and corrective action. Sentinel events (complaints, escalation failures, privacy incidents) should trigger structured review with documented learning actions, not informal blame.
Performance measures that do not incentivize coercion. Track response timeliness, follow-up offer rates, and closed-loop engagement outcomes rather than punitive outputs that undermine trust.
Public safety partnerships strengthen overdose prevention when designed as a governed protocol: life safety roles, non-interference safeguards, voluntary follow-up pathways, data boundaries, and audits that prove the system protects both people and public trust.