Recovery-Oriented Systems of Care (ROSC) often describe “whole-person” support, yet in day-to-day delivery, medical care still sits outside the recovery pathway. People cycle through urgent care and emergency departments for infections, chronic conditions, or wound care while SUD services operate in parallel—each side missing the other’s risk signals. Counties that improve stability treat primary care and infectious disease care as ROSC infrastructure, with explicit workflows, shared accountability, and measurable completion. This article aligns with ROSC design standards and operating controls and connects to community-based SUD service delivery models that can absorb real-world variability while sustaining clinical continuity.
Why medical integration is a ROSC reliability requirement
Medical instability is not a side issue in recovery; it is a predictable destabilizer. Untreated hepatitis C, unmanaged diabetes, chronic pain, endocarditis risk, and wound infections create recurring crises, disrupt attendance, and increase reliance on emergency care. If a ROSC cannot deliver medical follow-through, it becomes a fragmented set of services rather than a functioning system.
Integration does not require every clinic to “do everything.” It requires counties to define how screening happens, how referrals become attended appointments, how lab results and treatment plans move across providers, and who owns follow-up when people disengage or miss care.
Oversight and funder expectations that shape integrated ROSC delivery
Expectation 1: Demonstrable care coordination and reduced avoidable utilization. Counties are increasingly expected to show that high-need populations receive coordinated care that reduces preventable ED use and admissions. “We referred to primary care” is not defensible when people continue to present with untreated infections or complications that could have been managed in community settings with continuity.
Expectation 2: Equitable access to evidence-based screening and treatment. Funders and oversight stakeholders often expect counties to demonstrate that screening (HIV, hepatitis, STIs, TB risk where relevant) and treatment initiation are not limited to the easiest-to-engage clients. Integration must include practical mechanisms that reach people with unstable housing, limited phones, and inconsistent appointment attendance.
Operational Example 1: “One-visit” medical screening workflow embedded in SUD access points
What happens in day-to-day delivery
Counties embed a medical screening workflow into high-volume SUD touchpoints such as access hubs, MAT induction clinics, mobile outreach, or recovery support centers. Staff use a short protocol: consent capture, standardized screening questions, point-of-care testing where available, and immediate lab orders for confirmatory testing. Results are routed into a shared tracking queue managed by a designated clinical coordinator. Before the person leaves, the team schedules the next clinical step (primary care intake, infectious disease consult, or nurse visit) into protected capacity and provides a practical arrival plan (time, address, transport options, what to bring).
Why the practice exists (failure mode it addresses)
Traditional models rely on separate medical referrals after SUD engagement begins. In real life, people may not return for a “later” appointment, may lose paperwork, or may be unreachable. The one-visit workflow exists to prevent the predictable drop-off that occurs between identification of need and initiation of care.
What goes wrong if it is absent
Screening becomes sporadic and dependent on individual staff habits. People with infections remain untreated until symptoms become acute, leading to ED presentations and admissions. The ROSC loses credibility because “whole-person care” remains aspirational rather than operational, and providers lack a reliable mechanism to close the loop.
What observable outcome it produces
Counties can evidence higher screening completion, improved confirmatory testing rates, and faster time-to-treatment initiation. Audits show completed steps (screen, confirm, schedule, attend) and identify where failures occur, allowing targeted fixes such as adding protected appointment capacity or improving contact capture.
Operational Example 2: HCV treatment initiation pathway with shared task ownership
What happens in day-to-day delivery
When a person screens positive or has known hepatitis C, the ROSC triggers a defined initiation pathway. A care coordinator confirms insurance/coverage status, schedules labs, and books an initiating visit (either in primary care or a partnered infectious disease clinic). Pharmacy coordination is built in: prior authorizations, medication ordering, and pickup planning are completed through a single workflow. Peer or navigator support is assigned for the first two weeks to ensure attendance and medication start, with documented check-ins to confirm dosing has begun and side effects are managed.
Why the practice exists (failure mode it addresses)
HCV treatment fails operationally not because treatment is ineffective, but because initiation requires multiple steps that fall between roles: lab ordering, coverage verification, prior authorization, pharmacy pickup, and follow-up labs. The pathway exists to prevent “incomplete initiation,” where people are identified but never start or complete treatment.
What goes wrong if it is absent
Clients are told they “need treatment” but receive no practical plan. Providers assume another agency is handling authorizations, while pharmacies await missing paperwork. People disengage due to complexity and distrust, and the county continues to see repeat infections, ongoing transmission risk, and medical crises that could have been prevented through coordinated initiation.
What observable outcome it produces
Counties can measure time from positive screen to treatment start, initiation completion rates, and follow-up lab completion. The pathway creates an audit trail of task completion (labs done, authorization submitted, medication dispensed, follow-up scheduled), making performance defensible under review.
Operational Example 3: Shared care plan and escalation workflow for chronic conditions that destabilize recovery
What happens in day-to-day delivery
For clients with chronic conditions (diabetes, COPD/asthma, chronic wounds, hypertension, chronic pain), the ROSC uses a shared care plan template that identifies: current medications, warning signs, who to contact, and what actions to take before crisis escalation. Community SUD teams and primary care teams agree on escalation triggers (missed meds, repeated high glucose readings where monitored, wound deterioration, shortness of breath). When triggers occur, staff use a defined escalation route: same-day nurse call, urgent primary care slot, mobile visit, or coordinated ED presentation when necessary. Completion is documented, and supervisors review escalations for appropriateness and timeliness.
Why the practice exists (failure mode it addresses)
Chronic conditions often destabilize recovery through predictable episodes that could be managed early if risk signals are seen and acted on. The shared plan exists to prevent missed deterioration, where SUD teams observe decline but do not have a structured route into medical response, or medical teams are unaware of recovery destabilizers.
What goes wrong if it is absent
Clients bounce between urgent care and ED with repeat crises. SUD engagement drops because appointments are missed due to symptoms, and recovery teams become reactive rather than stabilizing. The county experiences high-cost utilization and poor outcomes despite significant service activity.
What observable outcome it produces
Counties can evidence fewer avoidable ED visits for chronic exacerbations, improved follow-through on primary care appointments, and increased stability indicators (fewer crisis contacts, improved medication continuity). Review meetings can identify system gaps (lack of urgent slots, unclear escalation ownership) and implement corrective actions.
Governance controls that keep integration real, not symbolic
- Defined completion measures: screening completed, treatment started, follow-up attended, escalation actions documented.
- Protected capacity: urgent primary care and infectious disease slots reserved for ROSC pathway clients.
- Role-based information sharing: minimum-necessary data flows that support coordination without overreach.
- Case review cadence: regular review of medical drop-off cases to identify workflow failures and fix them.
Medical integration inside ROSC is not achieved by adding referral lists. It is achieved by designing workflows that move people from screening to treatment initiation to sustained follow-up, with clear task ownership and governance that can withstand volatility. Counties that operationalize these interfaces reduce preventable crises, protect recovery stability, and create defensible evidence of whole-person system performance.