Quick answer
A closed-loop referral needs three things exchanged between the referring and receiving systems: the referral request with clinical context, status updates as the referral is accepted, scheduled, and completed, and the outcome (usually the consult note). Today that exchange uses a stack of standards: Direct secure messaging for transport, HL7 v2 order messages or FHIR resources (ServiceRequest and Task) for the request and status, and C-CDA documents for clinical content. The ONC-sponsored 360X project defines how to combine them into a closed-loop referral workflow between different EHRs. In practice, adoption is uneven, so most referral platforms combine standards-based exchange with API integrations and fax intake to close every loop.
Key takeaways
- No single standard closes a referral loop; it takes transport, message, document, and workflow layers.
- 360X is the reference design for EHR-to-EHR closed-loop referrals using Direct, HL7 v2, and C-CDA.
- FHIR ServiceRequest represents the referral; FHIR Task is commonly used to track its status.
- Prior authorization has its own FHIR track (Da Vinci CRD, DTR, PAS), driven by CMS-0057-F.
- Ask vendors which standards they support in production with live customers, not just on a roadmap.
The referral interoperability stack
| Layer | Standard | What it carries | Where you see it |
|---|---|---|---|
| Transport | Direct secure messaging (with XDM packaging) | Encrypted point-to-point delivery between organizations | Most certified EHRs; HISPs |
| Transport / API | FHIR REST APIs, vendor APIs | Real-time read and write between systems | Modern EHR integrations and app marketplaces |
| Order message | HL7 v2 (for example OMG and ORM orders) | The referral request and status changes | Interface engines; 360X |
| Order resource | FHIR ServiceRequest | The referral itself as a structured resource | FHIR-based referral and order workflows |
| Status | FHIR Task; HL7 v2 status messages | Accepted, declined, scheduled, completed | Closed-loop tracking |
| Clinical document | C-CDA (Referral Note, Consultation Note) | Problems, medications, reason for referral, consult findings | Request and closure packets |
| Workflow guide | 360X implementation guide | How the pieces combine for closed-loop referrals | EHR vendors implementing closed-loop exchange |
| Network | TEFCA / QHINs, Carequality, CommonWell | Query and exchange across networks | Record retrieval; growing use for referrals |
What 360X is and why it matters
360X ("360 Exchange") is an ONC-supported project that produced an implementation guide for closed-loop referrals between different EHR systems. Its design is layered on standards most certified EHRs already have: Direct for transport, HL7 v2 messages for the referral order and status, and a C-CDA document sent at minimum with the referral request and with the referral closure. A shared referral identifier lets both systems associate every message with the same referral, and a defined set of states (requested, accepted, scheduled, completed, closed, and others) lets each system infer where the referral stands.
The project has piloted primary care to behavioral health referrals and has expanded its use cases to transitions such as hospital to skilled nursing and referrals to social services. The limitation is adoption: 360X only works when both the sending and receiving EHRs implement it, and many organizations have not turned it on.
Where FHIR fits
FHIR is the API-based standard behind most new interoperability work:
- ServiceRequest represents the referral or order (it replaced the older ReferralRequest resource in earlier FHIR versions).
- Task is commonly used to manage the workflow — whether the receiver accepted, scheduled, or completed the request.
- DocumentReference and Composition carry clinical documents, including C-CDA content.
- Appointment and Slot support scheduling exchange where systems allow it.
For prior authorization specifically, the HL7 Da Vinci project defines Coverage Requirements Discovery (CRD), Documentation Templates and Rules (DTR), and Prior Authorization Support (PAS). CMS-0057-F requires impacted payers — Medicare Advantage, Medicaid, CHIP, and qualified health plans on the federal exchanges — to stand up a FHIR Prior Authorization API by January 1, 2027. See our CMS-0057-F readiness post and prior authorization automation guide.
Why most referral loops still do not close
| Gap | Effect |
|---|---|
| Receiving practice is on a different EHR without 360X or FHIR referral support | Referral arrives by fax or as an unstructured Direct message |
| No shared referral identifier | Status and consult notes cannot be matched to the original order |
| Consult note sent as a generic document | Lands in an inbox, never linked to the referral |
| Status updates not sent at all | Referring office never learns the patient was seen |
| Specialist outside every network the referrer uses | No electronic path exists |
That is why a referral platform cannot rely on one standard. ReferralPoint connects to 20+ EHRs through Direct, API, FHIR, HL7, CDA, and CCD, reads inbound faxes with AI (see fax referral automation), and writes status and consult notes back to the referring chart regardless of which route the information took. Details are on our integration and security page.
Vendor checklist: questions to ask
- Which EHRs do you write referral orders and status back to in production, with live customers?
- Do you send and receive Direct messages with C-CDA attachments?
- Do you support HL7 v2 order and status messages through our interface engine?
- Do you use FHIR ServiceRequest and Task, and against which EHR APIs?
- Have you implemented 360X workflows with any EHR?
- How do you match status updates and consult notes back to the original referral?
- What happens when the receiving practice has no electronic path at all?
- For prior authorization, do you submit through payer APIs, and are you preparing for Da Vinci PAS endpoints required under CMS-0057-F?
Our EHR referral software implementation test plan turns these into test cases.
Bottom line
Standards are how referral loops will close at scale, but adoption is uneven and will stay that way for years. The practical goal is a platform that uses 360X, FHIR, HL7, and Direct where they exist, and still closes the loop where they do not. Request a demo to see a referral cross EHRs and return with the consult note.
FAQ
Q: What is a closed-loop referral standard? A: A set of interoperability specifications that let referring and receiving systems exchange the referral request, status updates, and outcome. The ONC 360X implementation guide is the main reference for EHR-to-EHR closed-loop referrals.
Q: What is 360X? A: An ONC-supported implementation guide that combines Direct messaging, HL7 v2 messages, and C-CDA documents to support closed-loop referrals and transitions of care between different EHRs.
Q: Which FHIR resource is used for referrals? A: ServiceRequest represents the referral; Task is commonly used to track its status. ReferralRequest was the earlier resource name in prior FHIR versions.
Q: Does FHIR replace HL7 v2 for referrals? A: Not yet. Many organizations still rely on HL7 v2 interfaces and Direct messaging, while FHIR adoption grows through EHR APIs and regulatory requirements.
Q: What standards support prior authorization? A: The HL7 Da Vinci implementation guides — CRD, DTR, and PAS — which underpin the FHIR Prior Authorization API that CMS-0057-F requires impacted payers to implement by January 1, 2027.
Q: Why do referral loops fail even with interoperability standards? A: Because both sides must implement the same standards, status updates must be sent and matched to the original referral, and many specialists sit outside the networks the referring organization uses.
Sources and notes
360X details are from the Office of the National Coordinator for Health IT's 360X project materials. FHIR resource descriptions follow HL7 FHIR R4. CMS-0057-F dates are from CMS. ReferralPoint integration capabilities are on our integration and security page.



