HealthIT.gov December 10, 2024
Micky Tripathi and Mariann Yeager

The “T” in Trusted Exchange Framework and Common Agreement™ (TEFCA™) is an important part of what drives our work. So too is the public-private engagement we have created over the past seven years. As we launched TEFCA last year we did so with the expectation that we would need to make iterative adjustments over time to help it grow. That’s why we’ve recently released a new standard operating procedure (SOP) to guide how organizations seeking to participate in specific “Exchange Purposes” within TEFCA are vetted (see: Vetting Process SOP).

The need for additional vetting became apparent as Qualified Health Information Networks® (QHINs™) operationalized “TEFCA Required Treatment” under the Treatment Exchange Purpose. Participation in this specific Exchange Purpose differs...

Today's Sponsors

LEK
ZeOmega

Today's Sponsor

LEK

 
Topics: ASTP/ONC, Govt Agencies, Health IT, HIE (Interoperability), Provider, Technology
Sequoia Project identifies priority interoperability use cases
Meditech reaches milestone in health data exchange
HHS final rule aims to boost interoperability
First federal health agency joins TEFCA via eHealth Exchange
Health Commons Project Completes Acquisition of OneHealthPort to Advance Healthcare Innovation and Access across Washington State

Share This Article