The Trusted Exchange Framework and Common Agreement, known as TEFCA, is a nationwide approach to health information exchange established under the 21st Century Cures Act and administered by the Assistant Secretary for Technology Policy / Office of the National Coordinator for Health IT (ASTP/ONC), with the Sequoia Project serving as Recognized Coordinating Entity. Qualified Health Information Networks — QHINs — are the designated networks that connect to each other under a single common agreement.
For specialty referrals, TEFCA changes one thing profoundly: retrieving a patient's records from an organization you have no direct interface with becomes routine rather than exceptional. It does not, by itself, make a referral arrive, get scheduled, or come back.
The Vocabulary, Defined
- TEFCA: the framework plus the Common Agreement that governs nationwide exchange. Overview material is published by ASTP/ONC's HealthIT.gov TEFCA resources.
- QHIN: a network designated under TEFCA that exchanges with every other QHIN. Designation status is maintained by the Sequoia Project's RCE program.
- Exchange Purpose: the permitted reason for a request. Treatment is the purpose most relevant to referral coordination; others include individual access services, health care operations, public health, and government benefits determination.
- FHIR-based exchange: TEFCA has been moving from document-oriented query toward HL7 FHIR APIs, which return discrete data elements rather than a bundled document.
What TEFCA Genuinely Solves for Referrals
Record retrieval across strangers
A specialist receiving a referral from an unaffiliated practice on a different EHR has historically had two options: request records by fax, or ask the patient to remember. Under TEFCA, a query for treatment purposes can return the relevant history without a bilateral agreement between the two organizations.
Reduced duplicate testing
Prior imaging and laboratory results that exist somewhere become findable. The clinical value is obvious; the financial value shows up in avoided repeat studies, which matters directly in risk-bearing arrangements.
Better context for triage
A specialty practice deciding urgency benefits from knowing what has already been tried. Inbound triage quality improves when the record is present at intake rather than three days later — a dynamic covered in inbound referral management for specialty practices.
Post-discharge and cross-market continuity
Patients who receive care outside your market — while traveling, or after moving — stop being informational dead ends.
What TEFCA Does Not Solve
This is where organizations misplan. TEFCA is a data-access framework. Referral management is a workflow discipline. The gaps are structural, not temporary.
Exchange is pull, not assignment. A QHIN query returns records. It does not tell a coordinator that a referral is waiting, who owns it, or when it becomes overdue.
No scheduling. Nothing in TEFCA books an appointment or tells a referring clinician which in-network specialist has capacity next week.
No specialist selection. The framework is silent on which specialist is the right one by access, cost, quality, or patient fit. That selection logic is what Auto IdealMATCH applies at the point of order.
No loop closure guarantee. Consult notes become more retrievable, but retrievability is not closure. Closure requires that someone verify the visit occurred, that the note is in the referring record, and that outstanding items are actioned. See closed-loop referrals as a value-based care metric.
No prior authorization. Authorization is governed by a separate rule set, not by TEFCA.
Directory quality is untouched. TEFCA does not fix wrong phone numbers or panels closed to new patients, a failure mode examined in provider directory accuracy and failed referrals.
Comparison: What Solves What
| Referral failure point | TEFCA / QHIN exchange | Referral workflow platform |
|---|---|---|
| Retrieving outside records | Solves | Consumes |
| Knowing a referral exists and who owns it | No | Solves |
| Selecting the right in-network specialist | No | Solves |
| Scheduling the appointment | No | Solves |
| Prior authorization | No | Solves |
| Consult note returned and reconciled | Partially — improves retrieval | Solves closure |
| Directory accuracy | No | Solves via measured data |
The honest reading: TEFCA raises the floor on data availability, which makes good referral workflow more effective and makes bad referral workflow no better.
A Practical Framework for Referral Leaders
1. Confirm how you connect
Most provider organizations reach TEFCA through their EHR vendor or an existing regional exchange that participates in a QHIN. Establish which QHIN your organization reaches, through what intermediary, and for which exchange purposes.
2. Decide what you will do with retrieved data
Retrieval without an operating decision produces noise. Define, per specialty, which external elements should be surfaced at triage: recent imaging, recent labs, medication list, prior specialty consults.
3. Make retrieval automatic at intake
If a staff member must remember to query, it will happen unevenly. The query should fire when a referral is received, and the result should attach to the referral record — the pattern used by Auto ReferralCOORDINATOR.
4. Keep closure separate from retrieval
Track loop closure on your own terms: visit confirmed, note received, note reconciled into the referring chart. Do not treat "records are queryable" as closure. AHRQ's patient safety work on referral communication breakdowns, available through the AHRQ Patient Safety Network, consistently locates harm in the handoff rather than in the archive.
5. Govern privacy and minimum necessary
Broader access widens the surface area for inappropriate use. Confirm your exchange purposes are constrained, your audit logging is real, and your access review cadence is scheduled. Our posture is described in integration and security.
6. Re-baseline your metrics after connection
Expect time-to-triage and duplicate-testing rates to move. Expect completion rate and time to appointment to move only if you also changed the workflow.
Where This Leaves Health Systems
The strategic mistake is treating TEFCA participation as a referral strategy. Participation is table stakes, comparable to having e-prescribing. The differentiation is what your organization does in the minutes after a referral is placed: whether the right specialist is chosen, whether the patient is contacted in their language on their channel, whether authorization is already moving, and whether the note comes back and is read.
Systems planning multi-market growth should treat exchange as an enabler of the coordination model described in referral management for health systems, not as a substitute for it.
Key Takeaways
- TEFCA is a nationwide exchange framework; QHINs are the designated networks that connect under it.
- It materially improves cross-organizational record retrieval for treatment purposes.
- It does not schedule, select specialists, handle authorization, or close referral loops.
- Automate retrieval at intake, or it will happen inconsistently.
- Measure loop closure independently of data availability.
- Participation is baseline infrastructure; referral performance remains a workflow discipline.
Frequently Asked Questions
Q: What is TEFCA in plain terms? A: TEFCA is the Trusted Exchange Framework and Common Agreement — a nationwide set of rules, established under the 21st Century Cures Act and administered by ASTP/ONC with the Sequoia Project as Recognized Coordinating Entity, that lets participating networks exchange health information with each other under one agreement instead of thousands of bilateral contracts.
Q: What is a QHIN? A: A Qualified Health Information Network is a network designated under TEFCA that connects to every other QHIN. Provider organizations typically do not become QHINs; they participate through their EHR vendor, a regional health information exchange, or another intermediary that connects to one.
Q: Does TEFCA close the referral loop? A: No. It makes consult notes and outside records easier to retrieve, which helps. Closure additionally requires confirming the visit occurred, ensuring the note reaches the referring clinician's record, and acting on the recommendations. That is workflow, ownership, and measurement — none of which the framework provides.
Q: Can we query records for a referral before the patient is seen? A: Requests must be tied to a permitted Exchange Purpose. Treatment is the purpose that generally supports retrieving records for a patient you are preparing to see. Your organization's participation agreement and privacy policies govern the specifics, so confirm scope with your compliance team rather than assuming.
Q: Does TEFCA replace the need for a referral management platform? A: No. The two operate at different layers. TEFCA governs whether data can move between organizations. A referral platform governs whether the referral is routed to the right specialist, scheduled, authorized, tracked, and closed. Better data raises the ceiling on workflow performance; it does not create the workflow.
Q: How does TEFCA relate to CMS-0057-F? A: They are separate. TEFCA governs nationwide clinical data exchange among participating networks. CMS-0057-F obligates certain payers to expose prior authorization and claims APIs. Both use HL7 FHIR, and both feed the same referral pathway, but neither requirement satisfies the other.
Q: What should we measure after connecting? A: Time from referral receipt to triage decision, share of inbound referrals with outside records attached at triage, duplicate imaging and laboratory rates, and — held separately — referral completion rate and loop closure rate. The first three should improve from exchange; the last two move only with workflow change.
To see how retrieved outside records are surfaced inside a live referral workflow, request a walkthrough.
