Everything you wanted to know about TEFCA (but were afraid to ask)
Photo: Lyniate
The Office of the National Coordinator for Health Information Technology made the Trusted Exchange Framework and Common Agreement available on January 18.
While TEFCA is structured to create national connectivity of electronic health records, it can't perform unless a network of provider organizations becomes a part of the Qualified Health Information Networks, or QHINs, which facilitate data sharing. Unfortunately, many providers still aren't familiar with the new agreement, industry observers note.
Drew Ivan, chief strategy officer at healthcare interoperability vendor Lyniate, is a TEFCA expert and knows data sharing well. Healthcare IT News interviewed Drew, asking him to do a deep dive into TEFCA so readers can get a better understanding of what the agreement means and requires.
Q. On January 18, the ONC announced the publication of TEFCA. What is TEFCA, and were there any surprises in the announcement?
A. ONC called for the creation of TEFCA under the 21st Century Cures Act, which was passed in 2016, and TEFCA drafts were released in 2018 and 2019. Healthcare leaders have been anticipating this for several years.
TEFCA was developed, in part, to create a nationwide system that enables safe and easy sharing of healthcare information across care settings with a goal of increasing access to data for improved outcomes.
It is made up of two parts: the Trusted Exchange Framework details standards that networks must follow when sharing data, and the Common Agreement is a legal agreement that governs data sharing between networks.
A common use case that represents the benefit of TEFCA is associated with travel. Let's say you live in Boston and travel to Orlando for a vacation and become sick or injured. You want your medical record to be available so that the doctor taking care of you in Orlando has all the information she needs to give you the best care in the context of any other care you receive.
Another example is when patients are transported from a rural care setting for treatment a long distance away. Connecting rural and urban care settings is an expected benefit. TEFCA will enable this type of complete and accurate understanding of an individual's medical history.
While this is happening to some extent through health information exchanges at regional and state levels, the frameworks for how data is shared are inconsistent, which hinders efficiency and efficacy.
TEFCA aims to bring learned best practices to others by establishing a framework for Qualified Health Information Networks. QHINs will all share information with each other and will be organized under an umbrella organization called the Recognized Coordinating Entity (RCE). In support of this initiative, the ONC has contracted with a private organization – the Sequoia Project – to serve as the RCE.
We were pleasantly surprised to see that ONC also released the TEFCA FHIR Roadmap, which outlines how TEFCA will accelerate FHIR adoption throughout the healthcare industry.
ONC recognizes that health data exchange today relies heavily on established standards – including Integrating the Healthcare Enterprise profiles and HL7 Consolidated Clinical Document Architecture – and that FHIR is a more modern approach. The road map outlines a three-year plan to accelerate adoption through what ONC calls "achievable, incremental steps."
As healthcare organizations learn how TEFCA will affect them, they should evaluate their interoperability strategy and apply best practices. Connecting to QHINs and participating in TEFCA will require a clear understanding of their data-sharing capabilities, which might mean looking outside the organization to trusted interoperability partners for help and to ensure success.
Q. TEFCA cannot work unless a network of provider organizations become a part of the QHINs, which facilitate data sharing. Yet there is not a mandate at this time for providers to participate. How will there be a critical mass of providers to make TEFCA work?
A. Incentives tend to be better drivers than mandates. If governmental and commercial payers offer incentives for providers to participate in a QHIN, that may be more of an encouragement to providers than a mandate. Or we may see health plans deciding to contract only with providers that connect with a QHIN.
Another driver will be patients. People want to manage their own health information, a trend that has grown since COVID-19. With some patients in rural areas having to travel outside their communities for care, they need access to their full medical records. Another example is vaccination status. Many of us now access our vaccine credentials via a smartphone app.
The more empowered consumers become by stewarding their own health data, the more they will expect this type of data access as the norm. If patients learn they can start getting their health information with less effort than it takes now, they will choose providers that participate in QHINs over those that don't.
Q. Why is it important for healthcare professionals to be educated on TEFCA and raise awareness?
A. It's important for healthcare leaders to stay up to date on TEFCA developments, not only because of the drivers noted earlier, but also because they should be focusing on the long-term goals and positive outcomes of participating in TEFCA, such as eliminating gaps in care, lowering the cost of care and delivering the best care for their patients.
Larger provider organizations will have more resources to educate themselves about connecting to a QHIN. Individual physicians or smaller provider networks may have more difficulty finding the time and resources to educate themselves.
I encourage these providers to visit the ONC website, healthIT.gov, check with other key players in health information exchanges, or count on their existing health IT vendors, which are likely to have efforts underway to enable data sharing through TEFCA. The RCE also is hosting informational webinars in the coming months.
Beyond educating themselves, providers will need a plan, which starts with understanding where their data is and how it is currently shared. Next, they will need to execute their plan. Doing this when they're trying to do everything else that's required of a provider is daunting, so I encourage providers to ask their professional organizations or vendor partners for assistance.
Q. How do you think TEFCA will play out in 2022 and 2023?
A. Large health IT networks can begin the application process to become a QHIN during the second quarter of 2022, and QHIN designation will be awarded toward the end of the year.
Later in 2022, QHINs will likely begin having conversations with each other about the technical connections required to connect QHIN to QHIN. Then there will be a slow and gradual build-out of connectivity over the next 18 months.
Whether TEFCA will be fully embraced by the healthcare industry in this time frame is to be determined, as this will require education, community buy-in and careful consideration of incentives for participation.
Something could catch us off guard, of course. But it's reasonable to expect that two years from now there will be a functioning infrastructure in place to share data across the nation.
Twitter: @SiwickiHealthIT
Email the writer: bsiwicki@himss.org
Healthcare IT News is a HIMSS Media publication.