The open-loop problem
Consider a common scenario. A caseworker at a county Department of Social Services meets with a mother managing diabetes. During the intake, the caseworker identifies that the family also needs food assistance, mental health support, and help with transportation to medical appointments. The caseworker prints a list of community resources — a food pantry, a counseling center, a transit voucher program — and hands it to the mother.
That’s a referral. In most county systems, it is counted as three referrals. The caseworker has done their job. The activity metric is satisfied.
But nobody knows what happens next. Did the mother reach the food pantry? Was it open when she arrived? Did the counseling center have capacity? Could she afford the bus fare to get there? If she didn’t connect with any of those services, her diabetes management deteriorates. Her kids’ nutrition suffers. She ends up in the emergency department. The county spends ten times more on the ER visit than the food assistance and counseling would have cost.
This is open-loop. The referral leaves the system and never comes back. The caseworker doesn’t know. The county doesn’t know. The Medicaid program paying for the eventual ER visit doesn’t know. Nobody learns anything — not whether the referral worked, not whether the resource was appropriate, not whether the family’s needs were met.
Open-loop referrals create three compounding failures:
- People fall through cracks. When no one tracks whether a referral results in service delivery, vulnerable people — those with transportation barriers, language barriers, cognitive challenges, or simply too many crises to manage at once — disproportionately fail to connect. The people who most need coordinated support are the least likely to navigate a fragmented system on their own.
- Agencies can’t learn what works. Without completion data, counties cannot identify which community resources are effective, which are overloaded, or which referral pathways lead to better health outcomes. Resource allocation decisions are based on volume of referrals made, not value of referrals completed.
- Funders can’t justify investment. Medicaid waivers, federal grants, and state social care initiatives increasingly require evidence that services reach people and produce outcomes. Open-loop systems can’t provide this evidence. When the state asks “did your CIE investment improve population health?”, an open-loop county can only answer “we made more referrals.”
Open-loop vs. closed-loop: a direct comparison
| Dimension | Open-loop referral | Closed-loop referral |
|---|---|---|
| Definition | Referral is made; no confirmation of service delivery | Referral is tracked from initiation through service completion with confirmation |
| Data flow | One-directional: agency → person → resource | Bidirectional: agency ↔ resource, with status updates back to referring party |
| What you know | How many referrals were made | How many people received services, how long it took, and what barriers existed |
| What you don’t know | Whether anyone was actually helped | Minimal gaps — system flags unresolved referrals for follow-up |
| Completion rate | Unknown (typically estimated at 10–30% in literature) | Measurable (TogetherNow / Monroe County: ~70% across 40+ providers) |
| Outcome measurement | Activity metrics only (referrals made, screenings completed) | Outcome metrics (services delivered, health improved, barriers resolved) |
| Medicaid waiver compliance | Cannot demonstrate that services reached people | Provides the evidence base required by 1115 and other waivers |
| Technology requirement | Spreadsheet, paper list, or basic resource directory | CIE platform with bidirectional data exchange, consent management, and workflow tracking |
The contrast is stark. But the gap between 3% and 70% isn’t explained by effort or intention — it’s explained by infrastructure. Open-loop systems aren’t failing because caseworkers don’t care. They’re failing because the technology doesn’t exist to close the loop.
How closed-loop referrals actually work
A closed-loop referral system requires four capabilities that most county HHS agencies don’t currently have in a single platform:
1. Consent-based information sharing
Before any data moves between organizations, the person must consent. This is both an ethical requirement and a legal one — HIPAA, 42 CFR Part 2, and state privacy laws all constrain how personal information can be shared across agencies. A closed-loop system must manage consent at the individual level: who authorized what information to be shared, with which organizations, for what purpose, and for how long. Without this, the loop can’t close because the receiving organization can’t confirm service delivery back to the referring agency.
2. Bidirectional referral tracking
The referring agency sends a referral to a community resource. The receiving organization acknowledges receipt, accepts or declines the referral, schedules the service, delivers it, and confirms completion — all within the same system. If the person doesn’t show up, the system flags it. If the resource is at capacity, the system routes to an alternative. If there’s a barrier (transportation, language, eligibility), the system captures it so the referring agency can address it. This bidirectional flow is what distinguishes a CIE from a resource directory.
3. Cross-agency interoperability
The referral chain often spans multiple sectors: a county DSS office, a community health center, a food bank, a mental health provider, a housing authority. Each has its own systems. Closed-loop referrals require interoperability standards — HL7 FHIR for health data, HSDS (Human Services Data Specification) for community resources — so that different systems can exchange referral status without requiring manual data entry or phone calls. Without interoperability, “closing the loop” means a caseworker calling the food pantry to ask whether someone showed up. That doesn’t scale.
4. Outcome measurement
The most mature closed-loop systems go beyond tracking whether a referral was completed. They measure whether the service improved the person’s situation. Did the food assistance stabilize the family’s nutrition? Did the mental health referral reduce crisis events? Did the combination of housing support and employment services prevent a return to homelessness? This is the leap from process metrics to outcome metrics — and it’s what Medicaid waivers, federal funders, and state legislatures increasingly demand.
What 70% looks like: TogetherNow in Monroe County
Monroe County, New York offers the clearest picture of what closed-loop referrals produce when the infrastructure exists.
TogetherNow, a Rochester-based nonprofit born from the IBM Smarter Cities Challenge in 2015, operates the MyWayfinder platform on IBM Connect360 infrastructure. The network connects 40+ providers across health, human services, education, and community organizations in a single coordinated network. Referrals flow bidirectionally. Consent is managed at the individual level. Every referral is tracked through completion or flagged for follow-up.
The result, attributable to TogetherNow’s operating discipline as much as the platform: a nearly 70% referral completion rate.
To appreciate what that number means, consider the baseline. Published research has documented closed-loop rates as low as 3% in hospital settings before systematic intervention. National estimates of social service referral completion hover between 10% and 30%, though precise measurement is inherently difficult in open-loop environments because no one is tracking completion. The Monroe County result doesn’t just represent a better number — it represents a fundamentally different model of service delivery.
The outcomes are tangible. Medicaid members with chronic conditions are achieving better health outcomes through coordinated interventions. A man managing both diabetes and depression — previously cycling through emergency departments — now receives integrated case management connecting his primary care, mental health services, nutrition support, and housing assistance. His hospital readmissions have decreased. His housing has stabilized. He describes feeling like someone finally sees his whole situation rather than treating him as a collection of separate problems.
This outcome didn’t emerge from a single referral. It emerged from coordination across multiple systems. His Medicaid enrollment data connects to social service platforms. His caseworker can see his engagement with mental health services, whether he’s accessing food assistance, and whether barriers like transportation are preventing medical appointments. Community organizations providing housing support communicate directly with his healthcare team. Information flows securely across organizations with his consent, creating a unified approach to supporting his wellbeing.
The pattern is consistent: when services coordinate around the person rather than requiring the person to coordinate services, health improves.
Why closed-loop referrals are a 2026 imperative
Three converging forces are making closed-loop referrals a requirement rather than an aspiration:
Medicaid waivers now require it. Oregon’s 2022–2027 1115 Medicaid waiver explicitly requires closed-loop referrals for health-related social needs. New York State’s 1115 Waiver is driving CIE adoption through Monroe County and beyond. As more states pursue Medicaid waivers that address social determinants of health, the expectation that counties can demonstrate service delivery — not just service referral — will become standard.
Federal policy demands evidence. CMS, HRSA, and SAMHSA are all moving toward outcome-based accountability. The SNAP work requirement changes of 2025 demonstrated how quickly federal policy can shift — and how unprepared open-loop systems are to adapt. Counties that can prove their referral infrastructure works will be better positioned for federal funding. Those that can’t will face increasingly difficult conversations with legislators and funders.
The AMA is studying it. In 2025, the American Medical Association’s Council on Science and Public Health produced a formal report on closed-loop referral systems for addressing social determinants of health. The report identified technology interoperability, consent management, and community organization capacity as critical barriers — and called for incentivizing the development of consistent approaches to closed-loop referrals. When the AMA formally studies a coordination model, it signals that the healthcare system is preparing to require it.
What counties need to get there
Moving from open-loop to closed-loop is not a software purchase. It requires three investments:
A CIE platform built for government. Resource directories are not CIE platforms. A resource directory tells a caseworker where to send someone. A CIE platform sends the referral, tracks whether it was received, confirms whether the service was delivered, captures barriers when it wasn’t, and feeds that data back into the system so the next referral is smarter. The platform must be HIPAA/HITRUST/42 CFR Part 2 compliant, support HL7 FHIR and HSDS interoperability, and manage consent at the individual level.
Community partner engagement. Technology alone can’t close the loop. The food pantry, the counseling center, and the housing authority have to participate — accepting electronic referrals, confirming service delivery, and sharing status updates. This requires trust, shared governance, and often technical assistance to help small CBOs adopt digital workflows. The most successful implementations — including the Monroe County deployment — are community-led: the technology serves the relationships, not the other way around.
A commitment to measuring outcomes, not activities. The cultural shift is as important as the technical one. Traditional HHS systems have been optimized around process metrics: applications processed, referrals made, screenings completed. Closed-loop systems surface uncomfortable truths — that many referrals don’t result in services, that some resources are overloaded, that certain populations face barriers the system isn’t addressing. Agencies that embrace this transparency improve. Those that resist it perpetuate the open-loop illusion that activity equals impact.
How Connect360 closes the loop
IBM Health and Human Services Connect360 is a Community Information Exchange and closed-loop referral platform purpose-built for state and local government. It is the infrastructure behind TogetherNow’s MyWayfinder in Monroe County, LA County’s Domestic Violence Project, and Sonoma County’s ACCESS program.
Connect360 doesn’t replace existing systems. It acts as the connective layer between them — enabling referrals to flow bidirectionally across agencies, CBOs, healthcare providers, and 211 networks with consent-based data sharing and real-time status tracking. When a caseworker determines that someone with diabetes qualifies for food assistance, the system identifies relevant community services, enables a closed-loop referral with the person’s consent, and tracks whether they engage with diabetes education, nutrition counseling, and local food resources. It creates visibility into whether those referrals are helping, whether barriers still exist, and what additional support might improve outcomes.
The platform’s architecture is built for this kind of coordination:
- HIPAA / HITRUST / 42 CFR Part 2 compliant — handles the most sensitive health and behavioral health data
- HL7 FHIR and HSDS interoperable — connects health systems and community organizations using standards
- Hosted on Microsoft Azure with IBM 24/7 managed services
- Configurable workflows — each agency can define its own referral routing, eligibility logic, and consent rules
- 30-day deployment via Azure Marketplace — no multi-year IT procurement required
Frequently asked questions
What is a closed-loop referral?
A closed-loop referral is a referral that is tracked from the moment it is initiated through confirmation that the person received the service. The referring agency learns whether the connection was made, how long it took, and what barriers existed if it wasn’t. This enables agencies to measure outcomes rather than just activity.
What is an open-loop referral?
An open-loop referral is a referral where the referring agency has no mechanism to confirm whether the person received the service. The agency sends someone to a resource — a food pantry, a counseling center, a housing program — and never learns what happened. Most social service referral systems in the United States operate in open-loop.
What is a typical referral completion rate?
Published research has documented closed-loop rates as low as 3% in hospital settings before systematic intervention. National estimates of social service referral completion typically range from 10–30%, though precise measurement is difficult in open-loop environments. TogetherNow’s network in Monroe County, built on IBM Connect360, achieves a nearly 70% completion rate across 40+ providers.
What is a Community Information Exchange (CIE)?
A CIE is a technology platform that connects health and human services agencies, community-based organizations, and residents through shared data, closed-loop referrals, and coordinated care workflows. Unlike a resource directory, a CIE enables bidirectional communication: agencies can refer, track, and measure whether services were delivered and whether outcomes improved.
Do Medicaid waivers require closed-loop referrals?
Increasingly, yes. Oregon’s 2022–2027 1115 Medicaid waiver explicitly requires closed-loop referrals for health-related social needs delivery. New York State’s 1115 Waiver is driving CIE adoption. As more states pursue Medicaid waivers addressing social determinants of health, demonstrating actual service delivery — not just referral volume — is becoming a compliance requirement.
What is the difference between a resource directory and a CIE platform?
A resource directory tells a caseworker where to send someone. A CIE platform sends the referral electronically, tracks whether it was received, confirms whether the service was delivered, captures barriers when it wasn’t, and feeds that data back into the system. Resource directories support open-loop referrals. CIE platforms enable closed-loop referrals.