TEFCA (the Trusted Exchange Framework and Common Agreement) was designed to handle clinical data exchange across the US healthcare system through Qualified Health Information Networks (QHINs). For Payer-to-Payer Data Exchange under CMS-0057-F, TEFCA offers a path that reduces the bilateral payer engineering work in exchange for participating in a shared network. Several payer-to-payer solutions in 2026 integrate with TEFCA, with varying depth. Here are the leaders. For broader context, more on payer-side workflow integration covers the surrounding architecture.
What "TEFCA-Integrated" Actually Means
A TEFCA-integrated Payer-to-Payer solution can route transfers through a QHIN rather than requiring direct bilateral connections between every pair of payers. The QHIN handles authentication, network identity, and often Member Match across the network. The receiving payer connects once to the QHIN; the QHIN routes the request to the right prior payer or payers.
The depth of integration varies. Some solutions use TEFCA for network discovery and authentication, then run the actual data transfer point-to-point. Others run the full data flow through the QHIN. The depth has trade-offs for performance, control, and operational simplicity.
1. CommonWell Health Alliance
CommonWell is one of the foundational US clinical data networks and operates as a QHIN under TEFCA. CommonWell's Payer-to-Payer support leverages the existing CommonWell membership for network identity and routes requests to participating payers. For payers already in CommonWell for clinical data exchange, the Payer-to-Payer extension is a natural fit.
2. eHealth Exchange
eHealth Exchange is another large QHIN with deep payer participation. The platform handles authentication, query routing, and member lookup across the network. For payers with existing eHealth Exchange relationships, the Payer-to-Payer pattern uses the same connections.
3. Konza
Konza is a QHIN with strong payer-side focus and growing Payer-to-Payer specific tooling. The platform is newer than CommonWell or eHealth Exchange but moving faster on CMS-0057-F-specific patterns. For payers without existing QHIN relationships, Konza is often shortlisted alongside the larger networks.
4. Onyx with TEFCA Integration
Onyx Technologies built its Payer-to-Payer solution with TEFCA integration as a first-class option. Onyx handles the FHIR ePA stack and the payer-side platform; the TEFCA layer plugs in for network connectivity. This pattern fits payers that want a single vendor relationship with TEFCA-mediated transport.
5. Particle Health (Bilateral TEFCA Bridge)
Particle Health offers a TEFCA bridge for payers that want to participate without becoming full QHIN participants directly. The pattern routes the payer's requests through Particle's QHIN connectivity rather than the payer joining the QHIN itself. Best fit for smaller payers that want TEFCA benefit without the network membership cost.
What TEFCA Integration Buys and What It Costs
TEFCA integration reduces per-relationship engineering work. Without TEFCA, each payer-to-payer relationship requires bilateral agreements, authentication setup, and operational coordination. With TEFCA, the payer connects once to the QHIN and gains access to all participating payers.
The cost comes in three dimensions. Commercial: QHIN participation has subscription costs and per-transaction or per-member fees. Operational: the QHIN sits in the data path, which adds latency and a dependency. Control: the payer cedes some operational visibility to the QHIN compared with direct bilateral connections.
For most mid-size payers in 2026, the math favors TEFCA participation for the volume of payer-to-payer transfers expected post-2027 enrollment. For very large payers with concentrated transfer volume to a few specific counterparties, direct bilateral may still be cheaper.
How to Evaluate the TEFCA Path
A useful evaluation pattern is to model three years of post-2027 transfer volume under TEFCA and under direct bilateral, including the bilateral overhead of relationships with the top 10 to 20 partner payers. The deltas often favor TEFCA at typical mid-market scale.
For the broader question of TEFCA versus direct API as the architectural choice, the TEFCA vs Direct API comparison lays out the trade-offs. For the Member Match strategies that work both inside and outside TEFCA, the Top 5 Member Match strategies covers the algorithmic layer.