The highest-risk period after detox, ED, or inpatient discharge is not “sometime later”—it is the first 72 hours, when people are reorganizing housing, transportation, medications, and recovery supports all at once. Follow-up fails when systems confuse “we gave instructions” with “we ensured continuity.” High-performing regions treat early follow-up as an operational function with staffing, scripts, escalation rules, and measurable outcomes. This article explains how care transitions from detox, ED, and inpatient settings connect to community-based SUD service models through a designed 72-hour follow-up pathway that is auditable, repeatable, and resilient to weekend and after-hours variability.
Why “standard follow-up” usually fails
Most systems rely on inconsistent calls, generic discharge leaflets, or a single appointment scheduled far beyond the period of highest instability. The practical barriers are predictable: phones disconnected, transportation not arranged, pharmacy steps unclear, anxiety about withdrawal or cravings, and competing priorities like shelter rules or family obligations. If there is no operational owner for follow-up, failures present as “no-shows” and “nonadherence,” but the root cause is usually a design gap: no defined workflow for reaching people, resolving barriers, and documenting outcomes.
Oversight expectations that shape follow-up design
Expectation 1: Demonstrable continuity and reasonable efforts. Commissioners, Medicaid agencies, and managed care organizations often expect evidence that high-risk discharges received timely follow-up attempts and barrier resolution, not just that an appointment existed. Under contract management and utilization review, systems need documentation of outreach timing, contact outcomes, and escalation actions.
Expectation 2: Safety and risk management during transitions. Hospitals and county partners are expected to manage foreseeable transition risks: missed doses, withdrawal destabilization, and return to unsafe environments. Oversight typically focuses on whether there are escalation triggers (for example, missed contact plus known risk flags) and whether staff know what to do next, including when to involve clinical supervision or crisis services.
Core components of a 72-hour follow-up pathway
A workable model defines: (1) who owns follow-up (role and coverage); (2) contact methods (text, call, outreach, partner touchpoints); (3) a contact schedule (same-day, next-day, day-3); (4) barrier resolution routines (pharmacy, transport, ID, clinic hours); (5) escalation criteria (no contact, missed appointment, reported instability); and (6) documentation fields that produce a clean audit trail. The pathway must function across settings, which means shared definitions and shared “outcome codes” that make performance measurable.
Operational Example 1: ED discharge follow-up with multi-channel outreach and escalation
What happens in day-to-day delivery. Before ED discharge, a navigator confirms contact preferences and sends a test message (“This is your follow-up contact—reply YES to confirm”). The follow-up team runs a daily list of discharges with timestamps and risk flags. Within 24 hours, staff attempt contact using two channels (for example, text then call). If contact is made, staff complete a structured check: medication access, current symptoms, appointment status, and immediate barriers. If contact is not made, the case moves to escalation: a second-day attempt plus a partner touchpoint (shelter nurse, outreach team, or known provider) where consent allows.
Why the practice exists (failure mode it addresses). ED discharges often fail because the first contact attempt happens too late or uses a single channel that no longer works. The workflow exists to prevent “silent failure” where the system assumes the person will self-navigate during the most unstable period.
What goes wrong if it is absent. Without multi-channel outreach and escalation, missed contact is discovered only when the person returns to the ED or misses a later appointment. Staff then document “unable to reach,” but there is no evidence of reasonable efforts, no barrier resolution, and no trigger for alternative engagement methods.
What observable outcome it produces. Systems can measure time-to-first-contact, percent successfully contacted within 24 hours, and percent with documented barrier resolution. Over time, they see fewer missed first appointments, fewer rapid returns to crisis care, and better documentation quality during contract monitoring because each discharge has a follow-up outcome and escalation history.
Operational Example 2: Detox discharge follow-up focused on medication access and withdrawal stability
What happens in day-to-day delivery. A detox program assigns a follow-up owner who conducts a same-day “discharge stability call” and a next-day check. Staff use a structured script: confirm where the person slept, confirm medication access (including pharmacy location and hours), confirm next appointment details, and ask about withdrawal symptoms that may affect safety. If the person has not obtained medication or reports instability, the follow-up owner initiates a defined escalation: contact the receiving provider for an earlier slot, coordinate pharmacy troubleshooting, and alert clinical supervision for symptom guidance within scope and protocol.
Why the practice exists (failure mode it addresses). Detox discharges commonly fail because people leave clinically stabilized but operationally unsupported—pharmacies closed, transport absent, or symptoms worsening. The practice exists to prevent missed doses, unmanaged withdrawal, and rapid disengagement.
What goes wrong if it is absent. Without early stabilization checks, problems surface after the window for easy correction has passed: prescriptions expire, appointments are missed, and people re-enter crisis pathways. Staff may only learn about relapse or ED attendance after the fact, with no documented attempt to resolve barriers during the critical period.
What observable outcome it produces. Programs can evidence reduced “medication not obtained” incidents, improved kept-appointment rates, and fewer unplanned ED contacts within the first week. The audit trail shows contacts attempted, issues identified, actions taken, and confirmation that the handoff remained active until the receiving provider accepted ongoing care.
Operational Example 3: Inpatient discharge follow-up with appointment confirmation and no-show prevention
What happens in day-to-day delivery. An inpatient transition coordinator schedules the first community appointment before discharge and confirms it via a two-step process: (1) provider confirmation and (2) patient confirmation. Within 48 hours post-discharge, the follow-up team checks whether the appointment remains active and whether transport and documentation needs (ID, insurance, intake forms) are in place. If the appointment is at risk, staff use a “no-show prevention playbook”: reschedule to a nearer slot, switch to telehealth if allowed, or route to a walk-in option with documented acceptance criteria.
Why the practice exists (failure mode it addresses). Inpatient discharges fail when appointments exist on paper but are not practically reachable. The practice exists to prevent the common breakdown where a person misses the first appointment for solvable reasons (transport, paperwork, timing), then disengages entirely.
What goes wrong if it is absent. Without appointment confirmation and no-show prevention, the first appointment becomes a brittle single point of failure. Miss it once, and the system often defaults to passive rescheduling, long waits, and loss of engagement—especially when the person lacks stable phone access.
What observable outcome it produces. Systems can track reduced first-appointment no-show rates, faster rescheduling cycle time when appointments fail, and improved continuity measures (for example, percent seen within 7 days). Documentation demonstrates that the system took reasonable steps to make access real, not merely scheduled.
Making follow-up measurable without distorting delivery
Useful measures include: percent contacted within 24 hours; percent with barrier resolution documented; percent attending first appointment within 7 days; and percent requiring escalation. Systems also track “failure reasons” using standardized codes (unable to reach, transport barrier, pharmacy barrier, appointment cancelled, declined) to drive improvement. The goal is not punitive reporting; it is operational learning that reduces repeated breakdowns and supports defensible commissioning decisions.
Governance routines that keep the 72-hour pathway reliable
Reliability improves when leaders hold routine reviews of missed contacts, missed appointments, and rapid returns to crisis care. Strong systems run weekly huddles between ED, detox, inpatient teams, and community providers to review outliers, verify that escalation rules were followed, and agree corrective actions. They also test the pathway during known stress points—weekends, holidays, staffing shortages—to ensure coverage and documentation do not collapse under predictable pressure.