Referral Tracking in Healthcare: FHIR Standards, Closed Loops, and What Is Changing
Quick Summary
Referral tracking follows a referral from creation through service delivery and resolution. Closed-loop tracking adds visibility into whether a referral was received, acted on, and completed. With CMS interoperability requirements taking effect and broader FHIR-based referral standards under discussion, healthcare organizations and CBOs need referral systems that support structured data exchange, outcome tracking, and referral-to-resolution visibility.
Referral tracking is the process of monitoring a healthcare referral from the initial referral through receipt, service delivery, follow-up, and resolution. As healthcare interoperability standards evolve and federal rulemaking moves referral and authorization data toward standardized, machine-readable formats, organizations are increasingly expected to track referrals across payers, providers, specialists, and community-based organizations, not just create them.
What Is Closed-Loop Referral Tracking?
Closed-loop referral tracking maintains visibility across the full referral journey, rather than treating the referral as complete once it is sent. The sequence is:
Referral → Receipt → Service → Follow-Up → Outcome → Resolution
A system is "closed" when the referring organization receives confirmation that the referral was received, the member was engaged, the service was provided, and the need was addressed. Without that feedback loop, the referring organization knows only that a referral was created: not whether anything happened as a result.
| Traditional Referral Tracking | Closed-Loop Referral Tracking |
|---|---|
| Fax and phone-based workflows | Structured electronic workflows |
| Limited visibility after referral is sent | Referral status visible from referral to resolution |
| Manual follow-up and phone reconciliation | Trackable follow-up with documented outcomes |
| Fragmented data across organizations | Connected referral ecosystem across payers, providers, and CBOs |
| Outcome reporting difficult or impossible | Outcomes documented and reportable |
What CMS-0057-F Requires for Referral Tracking
In January 2024, CMS finalized the Interoperability and Prior Authorization Final Rule (CMS-0057-F). It requires Medicare Advantage organizations, state Medicaid and CHIP programs, Medicaid managed care plans, and ACA marketplace insurers to build and maintain FHIR-based APIs: Patient Access, Provider Directory, Provider Access, Payer-to-Payer, and Prior Authorization.
The goal is to stop moving referral and authorization information through fax and phone calls and replace those workflows with standardized, machine-readable data exchange. Most compliance dates fall in 2026. The full API build-out, which requires payers to expose this data electronically, is due primarily by January 1, 2027.
This timeline is already shaping how health systems and health plans approach referral-tracking infrastructure.
What CMS-0062-P Proposes
In April 2026, CMS proposed a follow-up rule: CMS-0062-P, extending many of the same interoperability and electronic prior authorization requirements to prescription drugs. CMS-0062-P is still a proposed rule and has not been finalized.
The more significant detail for referral tracking appears not in the rule itself but in the comment letters. In its June 2026 response, the American Hospital Association flagged that HHS is considering extending FHIR standards beyond prior authorization to cover all referral certification and authorization transactions. The AHA expressed support, describing it as a logical next step toward consistent, interoperable workflows.
If that expansion is finalized, it would be the first time the referral handoff between a provider, a specialist, and a community-based organization has a federally recognized data standard, rather than a patchwork of faxes, portals, and PDFs.
Confirmed vs Proposed: CMS-0057-F is final law with compliance dates in 2026–2027. CMS-0062-P is a proposed rule. The extension of FHIR standards to all referral certification and authorization transactions is under discussion, not yet finalized. Healthcare organizations should follow CMS rulemaking directly for updates.
What Does FHIR Mean for Referral Tracking?
FHIR (Fast Healthcare Interoperability Resources) is a standardized framework for exchanging healthcare information electronically through APIs. For referral management, FHIR-based APIs mean that referral and authorization data can move between EHRs, payers, specialists, and community-based organizations through machine-readable, structured channels: rather than through fax transmissions, PDFs, or manual phone reconciliation.
The practical difference for referral tracking is significant. Structured electronic data is traceable: organizations can see whether a referral was received, acted on, and resolved. Fax-based data is not. A FHIR-based referral workflow gives the referring organization visibility into what happened after the referral was sent: which is the foundation of closed-loop referral tracking.
This also affects every system involved in referral workflows. If the underlying data standard shifts toward FHIR, EHRs, referral platforms, payer portals, and community organization tools all eventually need to work within that standard.
Why Referral Tracking Matters Beyond Compliance
It is straightforward to read CMS-0057-F as a payer IT project. The practical implications extend further.
First, the timeline is close enough to plan around now. Building reliable referral-tracking infrastructure at enterprise scale takes time, regardless of who implements it. Organizations that wait for finalized rules before beginning assessment may find themselves behind their own internal timelines.
Second, this is not limited to payers. Referral and authorization data flows between EHRs, referral platforms, specialists, and community organizations. If the data standard shifts, every system responsible for referral tracking eventually needs to support that standard, including CBOs receiving referrals from health systems.
Third, the AHA's comment letter is essentially describing standardized bidirectional referral tracking as a candidate for a federal requirement, not just a best practice. What has often been described as the right approach for care coordination is increasingly discussed in terms of what referral tracking systems are expected to support.
New York Social Care Network: What 1 Million Screenings Tell Us About Referral Tracking
In June 2026, New York's Department of Health announced that more than one million Medicaid members have been screened for health-related social needs through the state's Social Care Network program. The program organizes regional networks connecting healthcare providers, community-based organizations, and local partners to identify unmet needs- food insecurity, unstable housing, transportation barriers- and connect members to support through social care navigators.
The screening number is notable. But for anyone working in referral management, the more relevant question is what happens after the screening.
Screening is a single, well-defined event: a set of standardized questions is asked, the answers are recorded, and the count goes up. What determines whether a program like this improves health outcomes is what happens between a positive screen and a resolved need. Did the referral to a food pantry or housing program reach the right organization? Did that organization have capacity? Did the member receive the service? Did anyone confirm the need was met?
NCQA's HEDIS MY2026 measure for Social Need Screening and Intervention reflects this logic directly. It does not simply track how many people were screened for food, housing, and transportation needs. It tracks whether people with a positive screen received a corresponding intervention within 30 days. That 30-day window explicitly acknowledges that screening without a documented, timely connection to services does not count as addressing the need.
A program that screens one million people generates a large volume of referrals to the community organizations doing follow-up work. At that scale, tracking referrals from creation to resolution can't run reliably on phone calls, faxes, or disconnected spreadsheets. It requires a shared, structured system where the referring organization can see whether the member was reached and the receiving organization can confirm the outcome.
How SDOH Referrals Fit Into Closed-Loop Referral Tracking
Social determinants of health (SDOH) referrals to food banks, housing programs, transportation services, behavioral health organizations, and other community-based services follow the same referral tracking logic as clinical referrals, with one added complexity: they cross the boundary between the healthcare system and the community sector.
A social care navigator can make a connection, but a program's performance depends on whether community organizations have the tools and capacity to close the loop and report back. Screening volume is a health system and state metric. Loop closure is a community organization capability.
For CBOs, this creates both a responsibility and an opportunity. Organizations that can receive referrals electronically, track a member's progress, and confirm outcomes back to the referring organization are increasingly valued partners. The ability to participate in closed-loop referral tracking is becoming as relevant to funding and partnership decisions as the direct service capacity itself.
What Healthcare Organizations and CBOs Should Do Now
- Assess current referral workflows. Identify where referrals still depend on fax, phone calls, spreadsheets, or disconnected portals. These gaps are what regulatory changes and quality measurement frameworks are making visible. Understanding where manual processes exist is the starting point for any referral tracking improvement.
- Evaluate interoperability readiness. Organizations should understand what referral data needs to move between EHRs, payers, specialists, referral platforms, and CBOs, and whether the current technology supports structured, traceable data exchange. This applies to health systems and health plans evaluating compliance timelines and to CBOs evaluating whether they can receive and respond to referrals electronically.
- Measure outcomes, not just volume. Track more than referral creation and screening counts. Closed-loop referral tracking means monitoring receipt, member engagement, service completion, follow-up, and resolution. The New York milestone is a screening count. The next meaningful milestone is completion.
For organizations building toward connected referral coordination across medical and social care, GridSocial by SocialRoots.ai provides closed-loop referral management that tracks referrals from referral to resolution across clinical and community-based services.
The Bigger Picture
None of this happened overnight, and the referral-specific FHIR expansion is not finalized law. The direction across several years of rulemaking has been consistent: closing the gap between data that technically exists somewhere and referral tracking data that actually moves, on a standard, in a way that can be followed across organizations.
Referral tracking is gradually shifting from an internal operational choice to something closer to a shared industry expectation. For health systems, health plans, and community partners, it is a useful moment to take stock of where referral tracking currently stands, and how closed the loop actually is between referral and outcome.
Key Takeaways
- Referral tracking is increasingly tied to healthcare interoperability and standardized data exchange: what was once an internal operational choice is becoming an industry expectation.
- CMS-0057-F is already final, with compliance dates in 2026 and a full API requirement due January 1, 2027. It requires FHIR-based APIs for prior authorization and related data across major payer types.
- A potential extension of FHIR standards to all referral certification and authorization transactions is under discussion, but is not yet finalized. Healthcare organizations should monitor CMS rulemaking.
- The practical priority for health systems, health plans, and CBOs is not only regulatory compliance: it is knowing whether referrals are received, acted on, and resolved, not simply whether a referral was sent.
From Referral to Resolution
Federal rulemaking is making referral tracking increasingly visible as an infrastructure requirement, not just a best practice. Whether your organization leads a health system, a health plan, or a community-based organization, the question is the same: how closed is the loop between referral and outcome in your current process? GridSocial, a domain product of SocialRoots.ai, connects medical and social referrals in a closed-loop environment, giving care teams visibility from referral creation through service completion and resolution.
Frequently Asked Questions
Referral tracking is the process of monitoring a patient referral from creation through receipt, service delivery, follow-up, and resolution. It gives care teams visibility into whether a referred patient received the intended service, rather than stopping when the referral is sent.
Closed-loop referral tracking maintains visibility across the full referral journey: Referral, Receipt, Service, Follow-Up, Outcome, and Resolution. The loop is "closed" when the referring organization receives confirmation that the member was reached, engaged, and the need was addressed.
CMS-0057-F, finalized in January 2024, requires Medicare Advantage organizations, state Medicaid and CHIP programs, Medicaid managed care plans, and ACA marketplace insurers to implement FHIR-based APIs including Patient Access, Provider Directory, Provider Access, Payer-to-Payer, and Prior Authorization. Most compliance dates fall in 2026, with the full API requirement due primarily by January 1, 2027.
No. The potential extension of FHIR standards to all referral certification and authorization transactions was referenced in the AHA's June 2026 comment letter on CMS-0062-P. It is under discussion and has not been finalized. CMS-0062-P itself remains a proposed rule. Organizations should monitor CMS rulemaking directly for finalized requirements.
FHIR (Fast Healthcare Interoperability Resources) is a standardized framework for exchanging healthcare data electronically through APIs. For referral management, it means referral and authorization data can move between EHRs, payers, specialists, and CBOs through traceable, structured channels rather than fax and phone workflows.
CBOs receive referrals, confirm receipt, track member engagement, and report outcomes back to the referring organization. That bidirectional communication is what closes the loop. CBOs that can receive referrals electronically and confirm outcomes in a structured way are increasingly valued referral partners for health systems and health plans.
NCQA's HEDIS MY2026 Social Need Screening and Intervention measure tracks whether patients with a positive social need screen received a documented intervention within 30 days. This confirms that screening alone does not satisfy the measure: a closed, documented connection to services is required. This quality measure reinforces the importance of tracking referrals through to completion.