Skip to main content

Q&A: Transparency remains the key to TEFCA, says ONC chief

"The bottom line: TEFCA makes health data sharing faster, easier and more secure," says National Coordinator for Health IT Dr. Thomas Keane. "This supports better care coordination, decreased costs and improved efficiency."
By Andrea Fox , Senior Editor
Dr. Thomas Keane, National Coordinator for Health IT

Dr. Thomas Keane is the National Coordinator for Health IT.

Photo: ONC

The Trusted Exchange Framework and Common Agreement is designed to establish a standard policy and governance underlying the technical foundation for nationwide health information exchange. 

But participants in TEFCA have sometimes been at odds about just how the network is being used. And some healthcare organizations have urged the U.S. Department of Health and Human Services to implement stricter TEFCA onboarding requirements to prevent the fraudulent exchange of protected medical data.

Dr. Thomas Keane, the National Coordinator for Health Information Technology at HHS, says the primary challenges to trust are not technical – they're inherent in the process of exchanging data between unaffiliated parties.

But transparency is key to promoting trust, he says, and ONC is "actively exploring options to layer in more network oversight moving forward."

We asked Keane recently not just about trust and transparency, but about how ONC is stepping up enforcement of information blocking rules, how it's aligning TEFCA with new interoperability initiatives from the Centers for Medicare & Medicaid Services initiatives – and about improving patient access and strengthening the national health data infrastructure more generally.

Q: You've used the term "data liquidity." Please explain what you mean by that, and how TEFCA is making it a reality for patients, health systems, payers and public health agencies.

A. Data liquidity means that the right health information is available to the right person at the right time. 

This means that a hospital far from home can access your health data, with your consent, if you seek care at that hospital while vacationing. And it means that when you get back home, your [primary care physician] can access the treatment records generated by that hospital. 

In either situation, a patient should expect they'll be seen by a healthcare provider who has access to their medical history, medications and allergies, and, as such, can make the most informed decision about their care. 

It's 2026. Patients deserve to receive care from healthcare providers who have the full picture of their health.

TEFCA, the national health information exchange network administered by ONC, provides key functionality to enable data liquidity. Through TEFCA, providers can exchange health information across data networks in a secure and private manner. 

At the beginning of 2025, approximately 10 million records had been exchanged on TEFCA. Today, 16 months later, nearly one billion records have been exchanged. The growth has been tremendous, and we couldn't be more excited about the enthusiasm for TEFCA across the healthcare ecosystem.

Your question notes that there are players in the healthcare system other than patients and providers, such as public health agencies and payers. They are already benefiting from TEFCA. 

There are currently six approved exchange purposes on TEFCA (exchange purposes being reasons why health data can be exchanged). These include treatment, payment, operations, individual access, government benefits determination and public health. 

Currently, the Social Security Administration is using TEFCA to facilitate disability benefits determination. The disability determination process used to take weeks or months; now, it can take place in under a day thanks to TEFCA. Similarly, public health agencies will be able to tap into TEFCA's scale to rapidly collect information for disease tracking or case investigations.

Q: What do you see as the main challenges to trust in TEFCA exchange? How can HHS ensure that data is securely exchanged for approved purposes?

A. The challenges are not technical in nature, but rather inherent to the process of exchange between counterparties that may not otherwise be affiliated. 

TEFCA's design must facilitate trust between such counterparties, who should have assurances that the health data they exchange will remain private and secure and will be used for the benefit of the patient. We've tried to address these types of concerns by making TEFCA transparent. 

The "rules of the road" for TEFCA participation – namely the Common Agreement, technical standards and standard operating procedures – are all publicly available. They are all developed collaboratively with participants and are all enforced by ONC and its recognized coordinating entity (RCE). 

Every TEFCA participant, from the largest tech company to the smallest provider, must agree to and be bound by the same set of legally enforceable rules. By taking this approach, we have developed a network that meets the market where it is and that allows participants to work collaboratively to allow for mutually beneficial, efficient health information exchange.

As mentioned, we've empowered an operational organization – the RCE – to enforce the TEFCA agreements. Every data request made within TEFCA is a legally binding assertion that can be audited to ensure its legitimacy. The TEFCA agreements delineate means for bringing concerns about counterparties to attention and specify processes for dispute adjudication, including mandatory cooperation with investigations. 

If parties are found to violate network protocols, they can be immediately disconnected and, if need be, permanently barred. 

Further, misuse of the network can expose one to civil and criminal penalties enforced by the government. We believe that this layering of agreements and enforcement is an effective mechanism to prevent bad actors from abusing the network and can ensure that improper access and use can be quickly detected, stopped and, if need be, referred for civil and criminal penalties.

That said, ONC will continue to dedicate resources to ensure TEFCA works as intended and that data is securely exchanged for approved purposes amongst trusted participants in the network. Oversight mechanisms will advance as appropriate to support TEFCA's continued growth, and we are actively exploring options to layer in more network oversight moving forward.

Q: The department has pledged to step up information blocking enforcement in 2026 and put resources behind it. How will it do this, and what compliance tips do you have for readers?

A. While TEFCA is a critical enabler of data liquidity, information blocking is one of the biggest obstacles to achieving data liquidity. 

We don't believe anyone – whether it's a doctor, hospital or an electronic health record company – should be able to hoard health information for their own gain. 

Patients, in particular, have a right to their electronic health information. To facilitate the proper movement of data, ONC has an online Report Information Blocking Portal. The majority of complaints received through the portal so far have come from patients.

To address this, we are partnering with our colleagues at the HHS Office of Inspector General to intensify our enforcement activity. We want to ensure that actors – including EHR vendors, providers and health information exchanges – comply with the regulations. 

If a party is found to engage in information blocking, OIG can level fines of up to $1 million per instance.

Separately, ONC administers a Health IT Certification Program whose participants are prohibited from information blocking. If a vendor of certified health IT is found to be engaging in information blocking, we can pull their certification, in which case their customers become ineligible for certain government payment incentives. 

Earlier this year, we began issuing notices of potential non-conformity to developers of certified health IT who were reported as information blockers on our complaint portal. Based on the responses we get to these notices, we can place the accused vendors on corrective action plans or can decertify their products outright. We are working with vendors, the market more broadly, and with our colleagues at OIG, to make sure that information blocking becomes a thing of the past.

Anyone aware of information blocking by an actor is encouraged to share their concerns with us via the Report Information Blocking Portal on our website.

Q: How do TEFCA and the CMS Health Tech Ecosystem – a fast-paced FHIR-focused initiative addressing many complicated aspects of data exchange – complement each other? How will the ecosystem benefit TEFCA?

A. Both TEFCA and the CMS-Aligned Networks are built around the same objective: supporting patients, providers and other authorized entities in securely accessing and exchanging EHI needed to improve patient care and reduce administrative burden in the healthcare system. 

From that shared purpose, CMS created its pledge criteria to give any network a pathway to accelerate interoperability capabilities. TEFCA, for its part, leverages Qualified Health Information Networks to facilitate information exchange. These QHINs go through a rigorous, uniform onboarding process to participate in TEFCA. 

However, the 11 organizations that have become QHINs under TEFCA have also pledged to be CMS-Aligned Networks, so there is synergy between these two efforts, which complement each other. 

Think of it like this: TEFCA is a rising tide that lifts all boats; CMS-Aligned Networks are more akin to speedboats speeding out ahead to tackle specific milestones. It boils down to pace and structure.

TEFCA is methodical, progressing through a formal, stepwise governance process, whereas CMS-Aligned Networks evolve through rapid testing, learning and refinement. TEFCA will ultimately benefit as CMS-Aligned Networks achieve their pledges and, similarly to TEFCA, advance efforts to empower patients with their EHI.

Q: In what other ways will HHS continue to advance TEFCA and ensure its success?

A. As participation and exchange volume grow, so do the exchange purposes. 

As I mentioned, there are six approved exchange purposes – treatment, payment, healthcare operations, public health, government benefits determination and individual access services – within TEFCA. 

We are ramping each of these up, but I am particularly excited about that last one – the IAS exchange purpose – and how it will enable patients to use an authorized website or app to directly retrieve and manage their health records from multiple providers. 

I myself have used an IAS-enabled app to download my own records through TEFCA; it's immensely gratifying to see the system working firsthand.

The "T" in TEFCA stands for trusted; trust is essential to ensuring its continued success. 

We are acutely aware that TEFCA is built on trust and that trust is, as the saying goes, "hard-earned and easily lost." That's why ONC and the RCE are working with the broader community every day to build and maintain trust by building transparency in processes and in network governance.

Andrea Fox is senior editor of Healthcare IT News.
Email: [email protected]
Healthcare IT News is a HIMSS Media publication.