TEFCA: What It Means for Health Apps and the Teams Building Them

TEFCA is the national network-of-networks for health data, and apps can reach it only through a QHIN. What product teams need to know about roles, exchange purposes, Individual Access Services identity rules and FHIR.

In short

  • TEFCA is a voluntary nationwide framework for exchanging health records between networks, and an app can join it only as a Participant or Subparticipant under a Qualified Health Information Network (QHIN).
  • Every TEFCA request carries an exchange purpose, and the one consumer apps care about, Individual Access Services, comes with strict identity rules: proofing to NIST IAL2 through an approved credential service provider and authentication at AAL2.
  • FHIR is arriving in stages, starting with Facilitated FHIR where a QHIN helps find the patient's records and the app then queries each FHIR endpoint directly.

For a health app, TEFCA means there is now one national set of rules for pulling a patient's records from many networks at once, but you cannot plug into it directly. An app joins as a Participant or Subparticipant under one of the designated Qualified Health Information Networks (QHINs), states an exchange purpose with every request, and, if it serves consumers, meets strict identity proofing rules before it can query anything. For most product teams the practical decision is which QHIN or participant to partner with and which exchange purpose fits the product.

This guide is for founders, product managers and CTOs who keep hearing TEFCA in sales calls and need to know whether it changes their roadmap. Every fact below comes from ASTP/ONC, the federal regulation, or the Recognized Coordinating Entity's published documents, linked at the end. The rules change often, so check the current versions before you commit to a design.

What is TEFCA, in plain terms?

TEFCA stands for the Trusted Exchange Framework and Common Agreement. HealthIT.gov describes it as a nationwide framework for health information sharing that makes it easier for providers, patients, public health agencies and payers to exchange records electronically. It has two halves. The Trusted Exchange Framework is a set of high-level principles for trusted exchange between networks. The Common Agreement is the legal agreement that networks sign to share data with each other.

The program now has a regulation behind it. 45 CFR part 172 implements section 3001(c)(9) of the Public Health Service Act. It sets the minimum qualifications for a health information network to be designated as a QHIN, the onboarding and designation procedures, and a voluntary process for QHINs to attest that they follow TEFCA. The Sequoia Project is the Recognized Coordinating Entity (RCE) under a five-year ONC contract awarded in August 2023. The RCE maintains the Common Agreement, manages QHIN applications and designations, and updates the QHIN Technical Framework.

The first QHINs were designated in December 2023, and HealthIT.gov notes that data began flowing among them within days. The RCE lists eleven designated QHINs: eHealth Exchange, Epic Nexus, Health Gorilla, KONZA, MedAllies, Kno2, CommonWell, eClinicalWorks, Surescripts, Netsmart and the Oracle Health Information Network.

Where does an app fit: QHIN, Participant or Subparticipant?

TEFCA has three tiers, and the regulation defines each one:

  • QHIN: a health information network that has been designated. QHINs sign the Common Agreement with the RCE and exchange data with each other.
  • Participant: a U.S. entity that has entered into the Participant/Subparticipant Terms of Participation and connects through a QHIN. HealthIT.gov lists hospitals, health systems and public health agencies as examples.
  • Subparticipant: a U.S. entity that has signed the same Terms of Participation and connects through a Participant. HealthIT.gov gives regional health information exchanges as an example of a Participant that may have Subparticipants.

Becoming a QHIN is not a realistic goal for most apps. HealthIT.gov says it requires a U.S. entity, an application, onboarding, designation and signing the Common Agreement, and that it typically takes about 12 months. A digital health company usually joins as a Participant of a QHIN, or as a Subparticipant of an organization that is already a Participant. In either case your contract terms flow down from the Common Agreement, so read them before you sign.

What are the exchange purposes, and why do they matter to product design?

Every request on TEFCA states why the data is being requested. HealthIT.gov says the purpose must be indicated in each request for data, and the regulation defines an exchange purpose as the reason authorized by a Framework Agreement and its standard operating procedures (SOPs). The initial exchange purposes are:

  • Treatment.
  • Payment, which the RCE describes as a subset of HIPAA payment activities (utilization review).
  • Health care operations, also a subset (quality assessment and improvement, business planning and development).
  • Public health.
  • Government benefits determination.
  • Individual Access Services.

The purpose decides who can ask, what they must prove and who must answer. A clinician-facing tool used by a health system will usually ride on treatment, under that health system's participation. A consumer app that lets people gather their own records uses Individual Access Services. A payer tool might use payment or operations, within the subsets the RCE defines. Pick the purpose first, then design the product around its rules.

What does Individual Access Services require of a consumer app?

Individual Access Services (IAS) is the purpose that lets a person use TEFCA to get their own records. The regulation defines it as services provided to an individual by a QHIN, Participant or Subparticipant that has a direct contractual relationship with that individual. The IAS SOP calls any of them that offers these services an IAS Provider. The RCE announced version 3.0 of the IAS implementation SOP with an effective date of August 3, 2026. Its requirements for IAS Providers include:

  • Use only credential service providers (CSPs) approved by an RCE-selected CSP approval organization, and have an agreement with one.
  • Make sure the CSP proofs each person's identity to at least Identity Assurance Level 2 (NIST IAL2) as defined in NIST SP 800-63A.
  • Authenticate individuals with processes set to at least Authenticator Assurance Level 2 (AAL2).
  • Verify identity to IAL2 before the person's first use of TEFCA, again when their verified demographics change, and again after their credentials expire.
  • Include the IAL2 claims token, issued by the CSP in OpenID Connect format, in every IAS query.
  • Include at least these IAL2-verified demographics in each query: first name, last name, date of birth, street address, city, state, ZIP code, and either an email address or a mobile phone number.

The SOP also adds a Demographics Double-Check, with a compliance date of August 1, 2026. When a responding node returns a patient match, the IAS Provider must compare the returned demographics with its own verified and self-asserted data using its own algorithm. If they do not match, it must reject the response, must not keep the patient identifier, must stop querying that node and must notify the organization behind it.

If a person tells the app that someone else's data was attributed to them, the IAS Provider must notify the organization associated with the responding node and have a process to purge the wrong data. The SOP notes that the responding organization would then likely need to follow the HIPAA Breach Notification Rule for a one-person breach, unless it identifies other mitigation factors. General privacy and security requirements for IAS Providers sit in a separate IAS Provider Requirements SOP and the Common Agreement, so read those too.

How does FHIR fit into TEFCA?

TEFCA started with document-based exchange, and FHIR is being added in phases. ONC and the RCE released version 2 of the FHIR Roadmap for TEFCA Exchange on December 11, 2023. It describes three phases:

  • Facilitated FHIR: QHINs provide the network infrastructure. The requester asks its QHIN who holds the patient's information, discovery happens between QHINs, and the requester then queries each FHIR endpoint directly, without going through the QHIN.
  • QHIN-to-QHIN FHIR exchange: QHINs use FHIR between themselves, while their internal networks can keep other approaches.
  • End-to-end exchange: Participants and Subparticipants exchange FHIR data across the TEFCA network through QHINs and other intermediaries.

The RCE's FHIR page lists the technical building blocks for Facilitated FHIR: the RCE Directory Service for finding endpoints, security based on the HL7 UDAP Security implementation guide, FHIR Provenance, and the HL7 US Core implementation guide, with USCDI as the default data set. It also lists the Bulk Data Access, IHE MHD and Da Vinci Payer Data Exchange guides as optional. The IAS SOP requires that all IAS exchange follow the QHIN Technical Framework and the Facilitated FHIR Implementation SOP.

For an app team this means skills you may already have: FHIR R4, US Core profiles and OAuth-based security. The new parts are UDAP-style trust and certificates, directory lookups and handling responses from many endpoints that each describe the same patient slightly differently.

Should your product join TEFCA at all?

TEFCA participation is voluntary. A few questions usually settle whether it belongs on your roadmap now:

  • Do your users need records from organizations you have no direct connection to? If you only ever talk to one EHR at one customer, a direct integration is simpler.
  • Is your product consumer-facing? Then Individual Access Services is your path, and the identity proofing flow becomes part of onboarding. Budget for the CSP and design for people who fail proofing.
  • Are your customers already on TEFCA? Health systems and networks connected through a QHIN may let your tool work under their participation for treatment use. Ask them before you build anything.
  • Can you carry the obligations? The Terms of Participation, SOPs and IAS Provider requirements come with your contract. Someone on your team has to own them.

What changes in your architecture if you do join?

  • Identity: an integration with an approved CSP, the IAL2 claims token stored and attached to queries, and re-proofing when demographics change or credentials expire.
  • Patient matching: your own matching algorithm for the Demographics Double-Check, with clear rules for when to reject a response.
  • Purpose tagging: every outbound request labeled with its exchange purpose, and product features limited to what that purpose allows.
  • Data from many sources: deduplication, provenance kept per record, and a way to show the patient where each item came from.
  • Wrong-patient handling: a support flow for reports of someone else's data, notification to the responding organization, and a purge process.
  • Records of activity: who requested what, under which purpose and when, so you can answer questions from your QHIN or a patient.

None of this replaces HIPAA. The IAS SOP says nothing in it alters a covered entity's obligations under applicable law. If your app handles PHI for a covered entity, you still need a BAA and the HIPAA safeguards. We sign a BAA before anyone on our team sees PHI and run a penetration test before launch, and TEFCA does not change either step.

Planning a TEFCA connection?

If you are deciding whether TEFCA, a direct EHR integration or an aggregator fits your product, talk to one of our engineers. Onix Systems has built software since 2000 with more than 370 engineers, and our free five-day technical audit ends with a written report on your integration options and what each one would take to build.