> ## Content Index > Fetch the complete content index at: https://www.healthdatacon.io/llms.txt > Use this file to discover other available public pages before exploring further. # TEFCA Passes 1.5 Billion Shared Documents and 23,000 Organizations, Moving U.S. Interoperability From Connectivity to Data Quality - URL: https://www.healthdatacon.io/tefca-passes-1-5-billion-shared-documents-and-23-000-organizations-moving-u-s-interoperability-from-connectivity-to-data-quality/ - Published: 2026-08-24T17:24:42.000Z - Updated: 2026-08-24T17:24:42.000Z - Description: More than 1.5 billion electronic health documents have been exchanged through the Trusted Exchange Framework and Common - Author: Kenneth R. Deans Jr. - Tags: Americas **Agreement since nationwide exchange went live in December 2023**, while 11 Qualified Health Information Networks now represent more than 23,000 organizations and more than 100,000 participating sites across the United States. The latest [RCE data](https://rce.sequoiaproject.org/onc-increases-funding-for-tefca-rce-in-new-contract-year/?ref=healthdatacon.io) show that a federal interoperability project that moved only about 10 million documents during 2024 and 464 million during 2025 has accelerated into national-scale infrastructure. The milestone changes the question facing U.S. health information exchange: whether records can move across networks is increasingly being replaced by whether the information that arrives is complete, computable, timely and trustworthy enough to improve care. The Trusted Exchange Framework and Common Agreement, or TEFCA, was created to provide a common legal and technical floor for exchange among previously separate health information networks. Instead of requiring every hospital, health information exchange, payer or digital health company to negotiate a unique agreement with every other organization, participating networks can exchange information through common rules and approved exchange purposes. On August 17, the Sequoia Project, which serves as the federal Recognized Coordinating Entity, announced that the Office of the National Coordinator for Health Information Technology had renewed the next contract option year with a **more than 15% funding increase**, citing continued growth, network integrity and development of additional use cases. Scale, however, is only one dimension of interoperability. A clinician can receive a technically successful record and still struggle to find the one result that matters. A population-health team can gain access to information while discovering that the same clinical concept is represented differently across organizations. A patient can direct records toward an application while encountering inconsistent identity matching or incomplete histories. The network can therefore become larger faster than the information inside it becomes uniformly useful. ## The network effect is now visible in the transaction curve TEFCA's early growth was gradual. The RCE reported roughly 10.4 million documents exchanged during 2024\. That total increased to approximately 464.3 million in 2025\. By August 2026, cumulative exchange had moved beyond 1.5 billion. The curve matters because network infrastructure becomes more useful as the number of reachable participants increases. A health system connected through one Qualified Health Information Network does not need a separate interface for every organization represented by another QHIN. The common framework is intended to make trust portable across networks. That is the practical meaning of a “network of networks.” The growth also raises the cost of inconsistency. A local interface problem affects the organizations using that interface. A data-quality problem carried through national infrastructure can be encountered repeatedly across states, care settings and vendors. The more successful exchange becomes, the more consequential semantics, provenance and completeness become. The RCE now lists permitted exchange purposes that include treatment, payment, healthcare operations, public health, government benefits determination and individual access. Those purposes are not interchangeable. A physician treating one patient needs different information and authorization patterns than a public-health agency conducting surveillance or a consumer directing information to an app. Governance therefore has to scale with transaction volume. ## August policy changes broaden who can query and who must respond Several TEFCA policy changes became effective August 3\. Updated treatment rules allow HIPAA-covered healthcare providers meeting applicable requirements to query using the treatment exchange-purpose code, while the associated vetting rules were also revised. The RCE's [TEFCA guidance](https://rce.sequoiaproject.org/rce/faqs/?ref=healthdatacon.io) explains that participating providers are required to respond to valid treatment queries in accordance with the Common Agreement and applicable law. Individual access changed at the same time. Version 3.0 of the Individual Access Services implementation procedure establishes requirements for identity verification and clarifies when QHINs, participants and subparticipants must respond to a consumer-directed query. The updated [IAS rules](https://rce.sequoiaproject.org/updated-individual-access-services-ias-implementation-sop-released/?ref=healthdatacon.io) matter because patient access introduces a different trust problem from provider-to-provider exchange. A clinician is authenticated through an organizational relationship; an individual directing records to an application must be matched accurately to the record and to the person claiming the identity. Those changes demonstrate that interoperability is not simply a matter of opening more endpoints. Each new use case creates its own combination of identity, authorization, purpose and responsibility. A national exchange framework becomes durable only if participants can trust not just the network but the reason a request is being made. ## Documents remain essential, but computable data are the next frontier Much of large-scale health information exchange still relies on clinical documents. That is not a technical failure. Documents are capable of packaging substantial clinical history and remain valuable during emergency care, transitions and referrals. The limitation appears when healthcare needs discrete data rather than a document. A longitudinal diabetes program may need A1C values over time. A medication-safety application may need active prescriptions and allergies. A quality program may need to identify a specific observation across thousands of patients. A clinician can read a PDF or consolidated clinical document; software needs a more predictable representation of the underlying data. That is why FHIR has become central to the next phase of U.S. interoperability. FHIR APIs allow systems to request more granular resources instead of retrieving an entire document. The value is not that one format is inherently better than every other format. It is that computable information can participate directly in analytics, workflow and decision support. A laboratory result illustrates the difference. A human can read “A1C 8.4%” in a document. A computable result can also carry the patient identifier, date, unit, code, reference information and provenance needed for software to recognize it as the same clinical concept across systems. Once data are being exchanged nationally, that semantic consistency becomes the difference between information that can be seen and information that can be used. ## More exchange makes provenance and quality harder to ignore A receiving organization needs to know where information came from, when it was recorded and whether it has been superseded. Medication lists expose the problem clearly. One organization may show a medication as active because it has not been formally discontinued. Another may have a newer reconciliation indicating the patient stopped taking it. A national exchange can successfully deliver both records. Connectivity does not resolve the contradiction. The same issue applies to diagnoses, allergies and problem lists. Data quality is partly a local documentation problem and partly an interoperability problem because the receiving system must decide how to present conflicting or duplicative information without creating unsafe certainty. The more data that arrive, the greater the risk of information overload. Clinical usability therefore depends on filtering, reconciliation and provenance as much as availability. That is one reason TEFCA's next phase is likely to be judged less by cumulative document counts and more by whether participants can convert those transactions into reliable workflows. ## The strongest interoperability metric may be what no longer has to happen Health information exchange creates value when it prevents unnecessary work or delay. A repeat CT scan avoided because the prior study is available. A medication history found before an emergency prescription is written. A public-health investigation accelerated because relevant records can be queried. A patient who no longer carries paper records between specialists. Those are consequences, not transactions. They are also harder to count. The **1.5 billion-document** milestone matters because it establishes that TEFCA has moved beyond a demonstration network. More than 23,000 organizations and 100,000 sites now participate in a common framework large enough to make nationwide exchange operationally significant. But scale exposes the next constraint. The United States has spent years building the ability to move health information. The next phase will require equal attention to whether the data can be interpreted, reconciled, governed and incorporated into care without adding another layer of complexity. TEFCA's success has therefore created a more demanding standard for itself. The question is no longer simply whether the network works. It is whether the healthcare system works differently because the network is there.