Earlier this month, Trusted Exchange Framework and Common AgreementTM (TEFCA®) Individual Access Services (IAS) Exchange connectivity was disrupted after the Qualified Health Information Networks® (QHINsTM) implemented the IAS SOP v3.0 technical changes due to implementation inconsistencies, including the approach to verifying IAS claims tokens. Connectivity has largely been restored, and the Recognized Coordinating Entity® (RCE®) is working with each QHIN to restore full exchange by the final compliance date of October 26, 2026.
Based on historical TEFCA Exchange volumes for IAS, the RCE estimates that as of October 19, 2026, more than 99 percent of IAS Exchange volume has been restored.
The following chart provides a snapshot of progress towards fixing the issues that led to the temporary disruption.
Why was IAS Exchange Connectivity Interrupted?
On June 26, 2026, the TEFCA QHIN Caucus and the TEFCA Participant/Subparticipant Caucus voted unanimously to approve a new version of the technical approach for how TEFCA Exchange takes place for Individual Access Services (IAS) exchange. The Exchange Purpose (XP) Implementation SOP: Individual Access Services (IAS) version 3.0 (IAS SOP v3.0) approved by the governing bodies included an October 1, 2026, date for the QHINs to move to a more reliable approach to identifying patients. This change was made to increase responsiveness to IAS Queries. Please see the RCE’s FAQs for more information about the Caucuses’ June approval of changes to IAS.
The RCE is working with the QHINs to fully understand the implementation and production challenges they experienced, including the technical variation amongst how QHINs implemented the updated SOP, in order to prevent any future disruptions with transitioning to new or updated SOPs. There were incompatibilities and different levels of readiness across the QHINs for the October 1 change that led to some lost connectivity. While the QHINs had engaged in partner testing ahead of October 1, it did not uncover differences such as varying levels of rigor in applying technical constraints. The RCE will leverage lessons learned to prevent any future disruptions to the network.
Has IAS Exchange Connectivity Been Restored?
As noted above, most QHINs have already made changes, and connectivity has largely been restored. However, the RCE continues to work with each QHIN to restore full IAS exchange, with regular touchpoints and daily status reporting. The RCE has also issued a TEFCA QHIN Compliance Bulletin that reiterates the requirements, addresses questions surfaced by the QHINs during implementation, and sets October 26 as the final compliance date.