TEFCA and QHINs: how the nationwide exchange framework works, and what ONC’s October 2026 rule changed

TEFCA connects Qualified Health Information Networks under one Common Agreement, overseen by ONC and a Recognized Coordinating Entity. ONC’s rule of October 28, 2026 replaces “ASTP/ONC” with “ONC” throughout 45 CFR part 172, effective December 28, 2026.

The Trusted Exchange Framework and Common Agreement, known as TEFCA, is a nationwide framework for health information sharing. ONC created it to remove barriers to sharing health records electronically among providers, patients, public health agencies and payers [1]. It is a network of networks: organizations connect to a Qualified Health Information Network, and the QHINs exchange with one another under common rules.

The parties and their roles

  • ONC is responsible for TEFCA overall: it sets TEFCA policy, supports network governance, works with the Recognized Coordinating Entity to expand TEFCA, and coordinates with other federal agencies [1].
  • The Recognized Coordinating Entity (RCE) develops, updates and maintains the Common Agreement, runs the QHIN application and designation process, monitors designated QHINs and updates the QHIN Technical Framework. ONC states that The Sequoia Project serves as RCE under a five-year contract awarded in August 2023 [1].
  • QHINs are the central connection points. To become one, a network must be a U.S. entity, complete the application, onboarding and designation process, and sign the Common Agreement; ONC says the process typically takes about 12 months. The first QHINs were designated in December 2023 [1].
  • Participants and Subparticipants are the organizations that connect through a QHIN, such as hospitals, health systems and public health agencies. A regional health information exchange that participates may have its own subparticipants [1].

The three governing documents

ONC describes three foundational documents, published in January 2022 and updated in November 2023 [1]:

  • the Common Agreement, the legal contract every QHIN signs, setting baseline legal and technical requirements, the infrastructure model and governance;
  • the Trusted Exchange Framework, the principles behind TEFCA, including standardization, openness and transparency, cooperation and non-discrimination, privacy, security and safety, access, equity and public health;
  • the QHIN Technical Framework, covering exchange among QHINs, including patient identity resolution, authentication and performance measurement, with some requirements that flow down to participants and subparticipants. It is incorporated by reference into the Common Agreement [1].

Each request for data must state its purpose. The initial Exchange Purposes are treatment, payment, health care operations, public health, government benefits determination and individual access services [1].

What 45 CFR part 172 regulates

Part 172 was added by the rule published December 16, 2024 and effective January 15, 2025, which implemented TEFCA provisions and amended the information blocking regulations to include definitions for a TEFCA manner exception [3]. It applies to Applicant QHINs, QHINs, terminated QHINs and the RCE. Its stated purposes are to ensure full network-to-network exchange of health information and to set a voluntary process for a QHIN to attest to adoption of TEFCA [2]. The main provisions:

  • Qualifications (172.201). A QHIN must be a U.S. entity not under foreign control. From the time it applies, directly or through its parent, it must be able to exchange information among more than two unaffiliated organizations, exchange all Required Information, already exchange for at least one authorized Exchange Purpose, and respond to other QHINs for all authorized purposes. It must also maintain governance, policies, capacity, dispute resolution and change management, privacy and security and breach response policies, and adequate financial and personnel resources, including financial reserves or insurance-based cybersecurity coverage.
  • Individual Access Services (172.202). A QHIN that offers them must obtain express consent from the individual, publish a privacy and security notice meeting minimum TEFCA standards, and delete the individual’s information on request, with listed exceptions.
  • Applications (172.301 to 172.307). An incomplete application is flagged in writing within 30 calendar days of receipt, a timeframe that may be extended by written notice. A denied applicant may reapply no sooner than six months after the date on the written denial.
  • Suspension and termination (172.401 and 172.502). ONC, or the RCE with ONC’s prior authorization, may suspend a QHIN responsible for a Threat Condition. A designation is terminated if a QHIN fails to remedy a material breach of part 172 within 30 calendar days of written notice, with up to 30 more days if it is diligently working on the remedy, or breaches a material provision of the Common Agreement that cannot be remedied.
  • Appeals (172.600 to 172.607) by a QHIN or Applicant QHIN, decided by a hearing officer.
  • Attestation (172.700 to 172.702). A QHIN may attest that it has adopted the Common Agreement and Trusted Exchange Framework; within 15 calendar days of notifying a QHIN that its submission has been accepted, ONC publishes at least the QHIN’s name in a QHIN Attestation Directory [2].

TEFCA also appears in the information blocking rules. Under the TEFCA manner exception in 45 CFR 171.403, an actor that limits the manner of fulfilling a request to TEFCA alone is not information blocking if both parties are part of TEFCA, the requestor can receive the information via TEFCA, the request is not made via the standards adopted in 45 CFR 170.215, and any fees and licensing meet the fees and licensing exceptions [5].

What the October 28, 2026 rule says about TEFCA

ONC’s final rule “Health Data, Technology, and Interoperability: ONC Deregulatory Actions To Unleash Prosperity”, published October 28, 2026, is mostly about the Health IT Certification Program. Its TEFCA content is narrow [4]:

  • The regulator’s name. The rule explains that on April 1, 2026 HHS published a reorganization that removed the Assistant Secretary for Technology Policy title and restored ONC as a singularly titled office. It therefore removes all references to ASTP in part 172: “ASTP/ONC” becomes “ONC” wherever it appears, and the definition of Applicant QHIN is revised to match. ONC found good cause to make these changes without a proposed rule, because the ASTP title no longer exists [4].
  • When. The rule is effective December 28, 2026, except for amendatory instructions 7, 10 and 12, which take effect January 1, 2027. The part 172 changes are instructions 23 and 24, so they take effect December 28, 2026 [4]. Part 172 as shown in the eCFR on November 14, 2026 still reads “ASTP/ONC” [2].
  • No new TEFCA policy. ONC treated comments on TEFCA policies as out of scope, stating that it did not propose any new standard, certification criteria or requirements in the rulemaking [4].
  • A certification criterion named in TEFCA measures. The rule notes that the clinical information reconciliation and incorporation criterion, 45 CFR 170.315(b)(2), is specified as an example of a criterion that may be used to support the HIE Bi-Directional Exchange and Enabling Exchange under TEFCA measures in Medicare Promoting Interoperability and MIPS. ONC did not finalize its proposed removal; it removed the criterion’s references to exchange standards, making it a functional criterion, and said keeping it ensures certified functionality is available for certain CMS measures [4].

In our view, the practical effect of the 2026 rule on TEFCA, for a health system or network, is mainly to update documents and procedures that cite “ASTP/ONC” in part 172. The qualifications, timelines and processes above are unchanged by it [4]. The rule’s certification changes are covered in our HTI-5 explainer.

This explainer describes the framework and the rules; it is not legal advice, and organizations should confirm with counsel how they apply to them.

Moraph’s teams help organizations with work like this. See our solutions.

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

  • TEFCA
  • QHIN
  • ONC
  • 45 CFR part 172
  • Common Agreement
  • Recognized Coordinating Entity
  • HTI-5