TEFCA and national exchange: outlook to 2027

TEFCA passed 2 billion documents shared and nearly 25,000 organizations in 2026; for 2027 the RCE has scheduled stricter vetting, FHIR security and governance rules, while CMS keeps TEFCA optional.

Eleven networks, two candidates, and a slower designation pipeline

TEFCA went live on December 12, 2023, with the first five designated Qualified Health Information Networks (QHINs): eHealth Exchange, Epic Nexus, Health Gorilla, KONZA National Network and MedAllies [2]. ONC's fact sheet lists six later designations: CommonWell Health Alliance and Kno2 on February 12, 2024, Netsmart on August 5, 2024, eClinicalWorks on January 16, 2025, Surescripts on April 15, 2025 and Oracle Health Information Network on November 28, 2025 [2]. As checked on 16 November 2026, the Recognized Coordinating Entity's (RCE's) designated QHIN page shows 11 networks and says the list may change as new applicants are designated [3]. Its candidate page lists two organizations in project planning and testing, Metriport and Zus Health, and says a listing does not guarantee designation [4] [8].

The RCE's August 2026 pipeline slide showed one application in definitive review, one accepted, none in conformance or partner testing and no active letters of intent [6]. ONC says the process typically takes about 12 months [1]. The RCE said in August 2026 that it had designated two QHINs in its most recent contract year and that ONC had awarded it the next option year with funding more than 15% higher [9].

Moraph's view

Moraph's view: the QHIN count will grow slowly through 2027 and matters less than it did. Most large EHR vendors and the established national networks are already on the list, so a health system's choice in 2027 is mostly which existing QHIN, or which participant under one, to connect through, not whether a network exists that reaches its trading partners.

Volumes: what the counts measure

Neither ONC nor the RCE publishes a TEFCA dataset; the figures come from slides, fact sheets and releases, each with its own cutoff. The RCE counts documents shared, organizations live and unique connections [6] [8].

Volumes: what the counts measure
PublishedDocuments shared since go-liveOrganizations liveUnique connections
January 20, 2026 (RCE) [5]More than 323 million, of which 10,378,545 in 2024 and 312,820,999 in January to November 2025 [5]Not stated [5]Not stated [5]
February 11, 2026 (ONC fact sheet) [2]464 million by the end of 2025 [2]Over 71,000 sites or organizations through 11 QHINs [2]Not stated [2]
August 18, 2026 (RCE) [6]1.5 billion [6]23,000 [6]100,000 [6]
September 15, 2026 (RCE, chart through July 2026) [7]Over 1.7 billion [7]23,000 [7]104,000 [7]
October 20, 2026 (RCE, chart through August 2026) [8]Over 2 billion [8]24,500 [8]107,000 [8]
November 5, 2026 (ONC) [10]More than 2 billion health records [10]Nearly 25,000 [10]Nearly 110,000 [10]

The measures are not interchangeable. The RCE's August release headline spoke of more than 100,000 organizations, while its text gave more than 23,000 organizations and more than 100,000 sites [9], and ONC's earlier fact sheet counted 71,000 sites or organizations [2]. QHIN Technical Framework version 2.1, effective December 4, 2025, added a requirement to report transaction volumes by Exchange Purpose [14], but as checked on 16 November 2026 neither ONC's TEFCA page nor the RCE's slides publish volumes by purpose [1] [8].

Moraph's view

Moraph's view: the document count rose from under half a billion at the end of 2025 to more than 2 billion by late summer 2026, roughly a fourfold rise in eight months, while organizations live grew by about 2,000 between August and November. Volume is growing much faster than membership, which suggests that organizations already connected are querying more. Health systems should read the headline totals as a sign of query load on their own responding systems, not as evidence that every purpose is in use. Until volumes by purpose are published, nobody outside the networks can tell how much of the total is payment, operations, public health or individual access.

Six purposes, and only two that compel an answer

Every TEFCA request must carry an Exchange Purpose code [1] [12]. The six purposes are treatment, payment, health care operations, public health, government benefits determination and individual access services [1] [2]. Version 5.1 of the RCE's Exchange Purposes SOP, effective August 3, 2026, lists 17 codes including sub-purposes such as HEDIS reporting, electronic case reporting and Social Security determination [12].

The response duties differ sharply by code [12]. Nodes operated by or associated with a health care provider must respond to required treatment queries (T-TRTMNT), and all responding nodes must respond to individual access queries (T-IAS); neither may be charged for [12]. For general treatment, health care operations, public health and government benefits determination, responding nodes should respond; for payment, they may; and for payment, operations, public health and benefits, a responder may charge the initiator fees [12]. Where a response is required, the required information is at least the USCDI v3.1 data a node maintains, and a node controlled by a health plan must also return claims and encounter data without provider remittances or enrollee cost sharing [12]. For codes that need no response, the non-discrimination provisions do not apply, which the RCE describes as partner-based exchange between organizations that choose each other [7] [12].

Government benefits determination gained an implementation SOP in December 2025, with a Social Security determination sub-purpose for disability benefits [23]. Under the SOP, a responding node that has opted into the Social Security code and completed coordination with SSA must respond, and SSA may pay for the records [12]. On November 5, 2026, ONC said the Department of Veterans Affairs and the Department of War had joined TEFCA, alongside the Indian Health Service, the Consumer Product Safety Commission and SSA [10], and ONC expects VA's use to extend to benefits determination led by the Veterans Benefits Administration [11].

Moraph's view

Moraph's view: for a health system, TEFCA in 2027 is mostly a treatment and individual access obligation with optional business uses around it. Payers that want claims-adjacent clinical data through TEFCA will find that providers may decline payment and operations queries or charge for them, so payer use will grow through negotiated partner-based exchange rather than through the network's default rules. Disability and veterans' benefits queries are the purpose most likely to add volume a health information management team notices in 2027.

What the RCE has scheduled for 2027

Four changes set dates in or near 2027 [8] [13] [6].

  • Vetting for required treatment queries. Under version 2.0 of the vetting SOP, published July 8, 2026, required treatment (T-TRTMNT) is the only vetted purpose [8]. From August 1 to December 31, 2026, an entrant may show either a standard X12 or NCPDP transaction within the last 90 days or a listing in a CMS directory; from January 1, 2027, only the transaction evidence is accepted, with an objection period of at least 5 business days [8].
  • FHIR security. Version 2.0 of the Facilitated FHIR SOP states an effective date of March 8, 2026, and ONC's February 2026 update lists it with that date, although the file the RCE posts is named "Draft" [13] [14]. The SOP says that as of Q1 2027 all registration, authentication and authorization of FHIR clients must follow the HL7 SSRAA implementation guide 1.1.0, with QHINs able to onboard SSRAA-based authentication by November 1, 2026 and every new FHIR node published to the production directory after January 1, 2027 required to support it [13]. Many of its conformance requirements stay optional during the transition, adopters may choose their own FHIR exchange partners until July 1, 2026 in staging and January 1, 2027 in production, and a FHIR advisory group may recommend changes to these dates [13].
  • Directory identifiers. Directory Service Requirements Policy SOP version 1.1, effective September 14, 2026, requires an IRS-issued employer identification number for each organization in the RCE Directory, except tribal or government agencies that have none, with six months for existing participant and subparticipant nodes and twelve months for existing child profiles once the Directory accepts the field [6].
  • Governance SOPs. The RCE's October 2026 plan targets votes in January 2027 on new Inquiries and Investigations and Restricted Participant List SOPs, in March 2027 on Dispute Resolution and Governance updates, and in late spring (June) 2027 on a Treatment SOP version 3.0, for which the RCE and ONC are defining the scope and approach for input from providers that are not covered entities, with all dates marked as anticipated and subject to change [8].

The Individual Access Services SOP version 3.0, effective August 3, 2026, sets identity verification requirements for IAS providers and says when nodes must respond to individual access queries [24]. In August 2026 the RCE said ONC had tasked it with a time-limited assessment of QHIN compliance practices, including cybersecurity, directory currency, IAS provider compliance and oversight of participants [6].

Moraph's view

Moraph's view: 2027 is the year TEFCA turns from growth to policing. Transaction-based vetting, a restricted participant list and an investigations SOP all point the same way: fewer loosely vetted requesters asserting treatment. For health systems that is good news on privacy complaints, and it also means their own directory entries, identifiers and outbound query attestations will be checked.

Where federal rules point to TEFCA

45 CFR part 172 took effect January 15, 2025, under ONC's TEFCA final rule [15]. ONC's HTI-5 final rule of October 28, 2026 removed references to the Assistant Secretary for Technology Policy from part 172, effective December 28, 2026 [17]. The HTI-5 proposal of December 2025 had proposed removing the TEFCA Manner Exception at 45 CFR 171.403 [16]; the final rule amends only parts 170 and 172 and contains no amendment to section 171.403, so the exception stood as checked on 16 November 2026 [17].

CMS uses TEFCA as one of two network pathways in its hospital program [18]. For CY 2024, 68.8 percent of reporting eligible hospitals and critical access hospitals reported the HIE Bi-Directional Exchange measure and 4.6 percent reported Enabling Exchange Under TEFCA [18]. The FY 2027 hospital inpatient rule removes the two referral loop measures from the CY 2029 EHR reporting period, a year later than proposed, so hospitals will then meet the objective through HIE Bi-Directional Exchange or Enabling Exchange Under TEFCA [18]. CMS said it is appropriate to recognize more than one network pathway at this time, and that it plans to evaluate moving both measures from attestation to performance-based measures [18]. The CY 2027 physician fee schedule notes that the MIPS Promoting Interoperability category includes an Enabling Exchange Under TEFCA measure under the Health Information Exchange objective, and describes how a Shared Savings Program ACO can count a clinician's "Yes" to that measure toward its bi-directional exchange metric [19].

CMS's separate Interoperability Framework invites networks to pledge as CMS-Aligned Networks, with FHIR access under US Core and USCDI v3 or later in effect from July 4, 2026, and acceptance of IAL2 digital credentials [21]. ONC said in December 2025 that every organization that had become a QHIN had also pledged, and that the pledge complements TEFCA rather than replacing it [20]. The RCE says participants in CMS's ACCESS Model are vetted for required treatment queries against the same criteria as any other entity [8]. CMS's July 2026 ACCESS webinar slides say participants must establish or maintain connectivity to an HIE, a CMS Aligned Network or a similar trusted network by July 6, 2027, and that designated QHINs also meet this requirement [25]. CDC's September 2026 request for information names TEFCA and QHINs among the data intermediaries that already do or could support public health, as it evaluates how intermediaries can support public health data exchange, with comments due November 20, 2026 [22].

Moraph's view

Moraph's view: no federal rule will require a hospital to join TEFCA in 2027. The pull is indirect and cumulative: a hospital that has neither a bi-directional HIE connection nor TEFCA participation has until the CY 2029 reporting period before the referral loop measures go, and CMS has said measures may become performance-based. Hospitals that report Enabling Exchange Under TEFCA today are a small minority, so the shift will show up as more hospitals connecting through their EHR vendor's QHIN in 2027 and 2028.

Interfaces and data operations

Moraph's view

Moraph's view, for the teams that run integration and health information management:

  • Plan for answering queries as well as sending them. A health system on TEFCA must answer required treatment and individual access queries at no charge, from every node tied to a provider. Query volume is growing faster than membership, so capacity, record location and patient matching on the responding side are where the work goes.
  • Keep two exchange formats. Documents are still what the RCE counts, while FHIR moves to mandatory SSRAA security for new nodes from 2027 and CMS's pledge criteria push FHIR APIs. Expect to run C-CDA document exchange and FHIR side by side through 2028.
  • Clean the directory. Employer identification numbers, node ownership and child profiles in the RCE Directory now carry deadlines and compliance consequences for the QHIN, which will pass them down to participants.
  • Separate purposes in logging. Release-of-information and privacy teams should log the Exchange Purpose code on every inbound request, since duties, fees and information blocking exposure differ by purpose.

What this means for you

  • Health systems: Size responding capacity and patient matching for required treatment and individual access queries, which must be answered without fees [12]. Decide before the CY 2029 EHR reporting period whether HIE Bi-Directional Exchange or Enabling Exchange Under TEFCA will meet the hospital exchange objective [18].
  • Health information management and privacy teams: Record the Exchange Purpose code on each inbound request and set policies for payment, operations and general benefits queries, where a response is optional and fees are allowed [12]. Expect benefits determination queries from SSA and, later, VA [11] [23].
  • Integration and EHR teams: Get directory entries ready for employer identification numbers within the RCE's deadlines [6]. Plan new FHIR endpoints on SSRAA dynamic registration, required for new production FHIR nodes after January 1, 2027 [13].
  • Payers: Plan TEFCA use for payment and operations as partner-based exchange with willing providers, since those codes carry no duty to respond [7] [12]. A health plan that responds to required queries returns claims and encounter data as well as USCDI data [12].
  • Digital health and IAS providers: Meet the identity verification requirements of IAS SOP version 3.0, effective August 3, 2026 [24], and expect stricter vetting under the new treatment and investigations SOPs scheduled for 2027 [8].

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 75% Open

    The RCE or ONC publishes a cumulative TEFCA exchange figure of at least 4 billion documents or health records shared since December 2023.

    How we will check: An RCE monthly information call deck, an RCE page or release, or an ONC page or release dated on or before September 30, 2027 states a cumulative figure of 4 billion or more.

    Basis: The cumulative count passed 1.5 billion in the August 2026 deck and 2 billion in the October 2026 deck, with data through August 2026 [6] [8]; ONC repeated more than 2 billion on November 5, 2026 [10].

  2. P2 By Confidence 60% Open

    The RCE or ONC reports at least 30,000 organizations live on TEFCA.

    How we will check: An RCE deck, RCE page or ONC release dated on or before December 31, 2027 gives an organizations-live count of 30,000 or more (counts of sites or unique connections do not qualify).

    Basis: The RCE reported 23,000 organizations live in August and September 2026 and 24,500 in October 2026 [6] [7] [8]; ONC said nearly 25,000 on November 5, 2026 [10].

  3. P3 By Confidence 65% Open

    At least one organization on the RCE's candidate QHIN page as of November 16, 2026 (Metriport or Zus Health) is designated a QHIN.

    How we will check: The RCE's designated QHIN page or an RCE or ONC announcement on or before December 31, 2027 shows Metriport or Zus Health as a designated QHIN.

    Basis: Both are listed as candidates in project planning and testing [4]; ONC says designation typically takes about 12 months [1]; the RCE designated two QHINs in its last contract year [9].

  4. P4 By Confidence 60% Open

    The RCE publishes a Treatment Exchange Purpose Implementation SOP version 3.0 with an effective date on or before December 31, 2027.

    How we will check: The RCE resource library or Topics in Change Management page shows a Treatment XP Implementation SOP version 3.0 (or later) with an effective date no later than December 31, 2027.

    Basis: The RCE's October 2026 project plan targets a late spring (June) 2027 vote on Treatment XP SOP version 3.0, for which the RCE and ONC are defining scope and approach for input from providers that are not covered entities, with all future dates marked as anticipated [8].

  5. P5 By Confidence 85% Open

    No CMS final rule published in 2027 makes Enabling Exchange Under TEFCA the only way for eligible hospitals and critical access hospitals to meet the Health Information Exchange objective.

    How we will check: Federal Register CMS final rules published in 2027 (in particular the FY 2028 hospital inpatient rule) still list HIE Bi-Directional Exchange or another non-TEFCA measure as a way to meet the objective.

    Basis: In the FY 2027 hospital inpatient rule CMS said it is appropriate to recognize more than one network pathway at this time, kept two pathways and delayed the referral loop removal to CY 2029 [18]; only 4.6 percent of reporting hospitals used the TEFCA measure for CY 2024 [18].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • TEFCA
  • QHIN
  • Recognized Coordinating Entity
  • 45 CFR part 172
  • exchange purposes
  • FHIR
  • individual access services
  • Promoting Interoperability
  • health information exchange