A recovery-oriented system of care (ROSC) can offer excellent clinical services and still produce poor outcomes if medication continuity is fragile. Most destabilization begins with small breaks: a missed refill, a pharmacy barrier, a coverage lapse, or an unclear responsibility for bridging medication after a missed appointment. When those gaps occur, people return to use to avoid withdrawal, risk escalates, and the system interprets the result as ânoncomplianceâ rather than an operational failure. Counties that improve stability treat MOUD continuity as a designed workflow with clear ownership, pharmacy coordination, and auditable controls. This article strengthens ROSC design and operating controls and aligns with community-based SUD service models that can maintain engagement through predictable fluctuations without reverting to punitive discharge.
Why medication continuity is a system function, not a clinician preference
Counties often treat MOUD continuity as the responsibility of individual prescribers and clinics. In practice, continuity is created (or broken) by the system: how quickly people can start medication, whether pharmacies reliably stock and dispense, whether coverage and prior authorizations are handled, and whether missed appointments trigger support or termination.
A ROSC that wants durable recovery outcomes must make medication continuity resilient to real-world variabilityâhousing instability, changing phone numbers, transport barriers, relapse episodes, and provider turnover. That resilience comes from standardized workflows and governance that protect continuity when conditions deteriorate.
Oversight and funder expectations shaping medication continuity
Expectation 1: Safety, diversion control, and clinical governance. Oversight bodies and funders expect counties to manage medication safety risks: duplication, unsafe combinations, loss/theft claims, and inconsistent dosing. A defensible ROSC can show how it balances access with safety through structured clinical review rather than blanket denial.
Expectation 2: Continuity measures that go beyond âprescriptions written.â Payers and county leadership commonly want evidence of continuity: time-to-start, refill timeliness, retention, and re-engagement after lapses. A ROSC that cannot measure continuity will struggle to improve it and will be vulnerable to criticism after adverse events.
Operational Example 1: Bridging and refill workflow that prevents withdrawal-driven relapse
What happens in day-to-day delivery. The county establishes a bridging workflow for predictable continuity threats: missed appointments, clinic closures, short-term crises, or coverage delays. When a participant misses a visit, the system triggers same-day outreach and a brief clinical triage to determine whether a bridge supply is appropriate and safe. The triage uses defined thresholds (recent stability, overdose risk, co-prescribing concerns) and assigns a responsible clinician for the decision. The participant receives a clear pickup plan and a rapid rescheduled appointment into protected capacity. All bridge actions are documented as continuity interventions, not exceptions.
Why the practice exists (failure mode it addresses). Many systems inadvertently create withdrawal by requiring a perfect attendance pattern to maintain medication. That approach drives relapse and overdose risk. Bridging exists to prevent the predictable failure mode where a missed appointment becomes a medication cliff.
What goes wrong if it is absent. People miss one appointment and lose medication access. They may return to illicit opioids to avoid withdrawal, increasing overdose risk. Programs then discharge the person for ânonadherence,â which further destabilizes them and pushes them back into crisis services and ED utilization.
What observable outcome it produces. Counties can track fewer involuntary medication interruptions, improved refill timeliness, and higher retention over 30â90 days. Case audits show whether missed appointments triggered continuity actions (outreach, triage, bridge, reschedule) rather than passive cancellation or discharge.
Operational Example 2: Pharmacy network playbook with stock, hours, and escalation routes
What happens in day-to-day delivery. The ROSC maintains a pharmacy playbook that identifies pharmacies willing and able to dispense MOUD reliably, including hours, stocking practices, holiday coverage, and contact routes for problem resolution. Navigators and clinics use the playbook to route prescriptions to pharmacies aligned with the participantâs location and transportation realities. When a dispensing failure occurs (stockout, identity barrier, unclear instructions), staff follow a defined escalation route: pharmacy contact, prescriber clarification, alternate pharmacy routing, and transport support if needed. The ROSC reviews dispensing failures monthly to identify systemic patterns and correct them.
Why the practice exists (failure mode it addresses). Pharmacy friction is a major hidden cause of continuity gaps. Even when prescriptions are written, people cannot always obtain medication due to supply, hours, stigma, or administrative hurdles. The playbook exists to prevent âprescribed but not dispensedâ failures that are otherwise invisible to leadership.
What goes wrong if it is absent. Participants are sent to random pharmacies that may not stock medication consistently or may be closed when the person can travel. Failed pickups lead to withdrawal and disengagement. Clinics assume âthe patient didnât follow through,â while the real problem is a pharmacy operations mismatch.
What observable outcome it produces. Counties can measure improved dispensing success rates, reduced stockout-related interruptions, and fewer emergency escalations due to pharmacy barriers. Pharmacy-related incident logs become actionable intelligence that informs routing decisions and partner engagement rather than anecdotal complaints.
Operational Example 3: Continuity governance that supports re-engagement without punitive discharge
What happens in day-to-day delivery. The ROSC adopts a continuity standard that requires programs to offer re-engagement pathways after relapse or missed contacts, with clear criteria for when higher-intensity support is needed. Staff use structured follow-up protocols (first-week contacts after restarts, barrier reviews after missed refills, clinical consult for risk escalation). Programs do not discharge solely for relapse; instead, relapse triggers a care plan adjustment (more frequent contact, stabilization routing, peer support intensification). Supervisors audit discharges and medication interruptions to confirm they meet policy and are not punitive defaults.
Why the practice exists (failure mode it addresses). Punitive discharge policies create churn and increase overdose risk. If participants learn that disclosing relapse will end their care, they hide risk until it becomes crisis. Continuity governance exists to prevent service models from selecting only stable clients and abandoning those who most need support.
What goes wrong if it is absent. Programs discharge people for missing visits, losing medication, or returning to use. The ROSC becomes a revolving door of repeated intake without stability. Counties see persistent overdoses and utilization despite âhigh service activity,â because continuity is not protected.
What observable outcome it produces. Counties can evidence higher retention and re-engagement rates, fewer involuntary discharges, and reduced high-risk medication gaps. Governance reviews show consistent application of standards and corrective actions when programs drift toward punitive policies.
Key controls that make medication continuity resilient
- Defined bridging rules: outreach and clinical triage before medication cliffs.
- Pharmacy routing intelligence: match dispensing realities to client logistics.
- Re-engagement standards: relapse triggers support escalation, not termination.
- Continuity metrics: track start timeliness, dispensing success, refill gaps, and retention.
Medication continuity is not a single prescriptionâit is a system capability. When counties design bridging workflows, manage pharmacy operations, and govern continuity standards that prevent punitive discharge, ROSC pathways become more stable, safer, and more defensible under oversight. The result is fewer medication gaps, fewer crisis escalations, and a recovery system that remains functional when real life interrupts.