Emergency departments and inpatient units are where overdose risk is most visibleâand where system failures show up fast. Counties strengthening harm reduction and overdose prevention systems get far more impact when hospitals can deliver consistent, governed harm reduction practice that connects directly into community-based SUD service models. A consult team model works when it is treated as an operational pathway (roles, escalation, documentation, closed-loop referrals, and QA), not as goodwill from individual clinicians.
What an ED/inpatient harm reduction consult team must do in practice
A consult team is a bridge service with three core functions. First, it reduces immediate risk before discharge (naloxone access, overdose education, safer use messaging that fits the personâs reality, and practical planning for the next 24â72 hours). Second, it starts or stabilizes evidence-based treatment when the person wants it, using rapid access pathways rather than âhereâs a number to call.â Third, it closes referral loops: the team must know whether the next step happened and re-engage when it did not.
Oversight expectations the model must satisfy
Expectation 1: Hospitals and county funders must be able to evidence consistent, non-discriminatory access. A consult team cannot exist only during business hours or only for âeasyâ patients. Oversight will look for equitable coverage by shift and by population, with clear eligibility rules and documented timeliness standards.
Expectation 2: Privacy-safe coordination with an auditable trail. Consult teams often coordinate with outreach, peers, and providers. Oversight expects minimum-necessary information sharing, role-based access, and documentation that shows who shared what, for what purpose, and what happened next.
Key design choices that prevent ânice serviceâ drift
Define trigger criteria and response time. Consult teams fail when referrals depend on individual clinicians remembering to call. Reliable models use triggers (overdose presentation, opioid withdrawal, high-risk polysubstance use, repeated ED visits, injection-related infection) and a response standard (for example, consult initiated within a defined window).
Make discharge risk-reduction a standard bundle. The bundle should be operationally simple: naloxone provision, brief coaching, a documented follow-up plan, and an explicit âwho owns next contactâ decision.
Use closed-loop referrals with escalation. If the receiving service does not acknowledge a referral, the pathway must escalate (second attempt, alternate provider, outreach re-engagement) rather than silently failing.
Operational Example 1: ED overdose consult workflow with a discharge-ready risk reduction bundle
What happens in day-to-day delivery. A person presents after a non-fatal overdose and is stabilized. The ED triggers an automatic consult. The consult team (often a peer specialist plus a clinician or nurse) meets the person in the ED, confirms immediate priorities, and completes a discharge-ready bundle: naloxone is dispensed or confirmed, overdose response and safer use advice is tailored to the personâs context, and a follow-up plan is agreed. The team documents the bundle in a structured template and schedules the next contact (phone, text, outreach meet-up, or clinic appointment) before the person leaves.
Why the practice exists (failure mode it addresses). The predictable failure mode after overdose is âdischarge into the same conditionsâ with no operational bridge. People often leave with vague advice, no confirmed naloxone access, and no scheduled follow-up, even when motivation is high in the moment.
What goes wrong if it is absent. The ED records an overdose visit, but the system creates no downstream action. The person returns to high-risk use without tools or connection, increasing repeat overdose risk. Hospitals and counties then invest in warm handoffs that look good on paper but remain inconsistent in delivery because no standardized bundle exists.
What observable outcome it produces. A bundled consult workflow increases the percentage of overdose presentations leaving with confirmed naloxone, a documented follow-up plan, and a scheduled next step. Outcomes are evidenced through structured documentation completion rates, follow-up contact completion, and reduced repeat overdose presentations over defined time windows.
Operational Example 2: Inpatient consult pathway for infection admissions that converts crisis care into engagement
What happens in day-to-day delivery. A patient is admitted with an injection-related infection. The consult team is triggered early (for example, within 24 hours). The team coordinates with the primary medical team to align withdrawal management, pain control considerations, and realistic discharge planning. If the patient wants MOUD, the consult pathway enables initiation during admission with an appointment scheduled for continuation in the community. If MOUD is not desired, the team still completes harm reduction planning: naloxone access, safer use advice, wound follow-up, and a plan for re-contact after discharge through a county partner.
Why the practice exists (failure mode it addresses). Infection admissions often represent a critical âpause pointâ where people may be open to stabilizing supports. The failure mode is that hospitals treat the medical problem but do not build an operational bridge to reduce the risk of rapid relapse, early discharge against medical advice, or unsafe re-entry to the community.
What goes wrong if it is absent. Patients leave without coordinated follow-up, miss wound care visits, and re-present with preventable complications. Systems then interpret repeated admissions as ânonadherence,â when the operational reality is that no one owned the transition or removed the administrative barriers that predictable instability creates.
What observable outcome it produces. The inpatient consult pathway improves documented follow-up attendance for wound care or infectious disease visits, increases voluntary MOUD continuation when started in hospital, and reduces avoidable readmissions linked to failed transitions. Evidence includes closed-loop referral status, appointment attendance confirmation, and trend analysis of repeat admissions for similar causes.
Operational Example 3: Closed-loop referral governance between the hospital, county outreach, and MOUD providers
What happens in day-to-day delivery. The consult team uses a closed-loop referral tracker that records referral sent, received, scheduled, attended, and escalated outcomes. The receiving provider acknowledges within a defined timeframe and updates the tracker with coded status (no clinical detail). If an appointment is missed, the system triggers re-engagement: the consult team or county outreach partner contacts the person using the preferred method, offers alternative options, and documents the outcome. Supervisors review weekly exceptions (unacknowledged referrals, repeated no-shows, long waits) and implement corrective actions with partner services.
Why the practice exists (failure mode it addresses). The most common breakdown is silent failure: referrals are âmadeâ but not received, not scheduled, or not completed, and nobody sees the failure pattern. Without a closed-loop mechanism, teams cannot learn which partners are responsive or where capacity constraints are collapsing access.
What goes wrong if it is absent. Hospitals can only report âreferrals provided,â which is not the same as engagement. Counties cannot evidence impact for settlement funds or grants because conversion is unknown. Meanwhile, patients experience repeated administrative friction that reduces trust and increases reliance on crisis care.
What observable outcome it produces. Closed-loop governance increases referral acknowledgement, shortens time-to-appointment, and reduces the proportion of people lost after discharge. Evidence includes referral completion rates, exception logs with corrective actions, and improved equity of access by shift and location.
Assurance mechanisms that keep the model defensible and scalable
Documentation standards. Use structured templates that prove the pathway ran: bundle delivered, naloxone status confirmed, follow-up plan agreed, referral status tracked.
QA sampling. Monthly sampling should test whether consult triggers worked, whether discharge bundles were completed, and whether referrals closed or were escalated appropriately.
Capacity agreements. Consult teams are only as strong as downstream access. Counties should negotiate reserved bridge slots, response-time expectations, and escalation routes with partner providers.
ED and hospital consult teams reduce repeat overdose when designed as a governed operating model: consistent triggers, discharge-ready risk reduction, closed-loop referrals, privacy-safe coordination, and QA that proves the system works at real speed.