Healthcare Interoperability in 2026: TEFCA, FHIR, and What's Next
2026 is the year healthcare interoperability stops being aspirational and starts being mandatory. TEFCA (Trusted Exchange Framework and Common Agreement) is operational, CMS interoperability rules have hard compliance deadlines, and payer-to-payer data exchange requirements are in effect. If you are building or operating healthcare technology, here is what you need to know.
TEFCA: The National Network Is Live
The Trusted Exchange Framework and Common Agreement (TEFCA) is the federal government's initiative to create a nationwide framework for health information exchange. After years of development, TEFCA is now operational with designated Qualified Health Information Networks (QHINs) actively exchanging data.
What TEFCA Does
TEFCA creates a "network of networks" model. Instead of point-to-point connections between every health system, provider, and payer, organizations connect to a QHIN, and QHINs exchange data with each other under a common set of rules.
The key exchange purposes defined by TEFCA:
| Exchange Purpose | Description | Status |
|---|---|---|
| Treatment | Clinician-to-clinician data exchange | Active |
| Payment/Operations | Claims, eligibility, prior auth | Active |
| Public Health | Reporting to public health agencies | Active |
| Individual Access | Patient right to their own data | Active |
| Government Benefits | Social services and benefits | Emerging |
What This Means for Your Organization
If you are a health system or provider, TEFCA participation is becoming the default expectation. While not yet legally mandatory for all entities, CMS is strongly incentivizing participation through quality programs and payment models.
If you are a health tech company, TEFCA changes how you think about data exchange. Instead of building custom integrations with each health information exchange (HIE), you can connect through a QHIN and reach a national network. This reduces integration effort but introduces new governance requirements.
Practical considerations:
- TEFCA uses FHIR R4 as the primary data standard, but also supports C-CDA for legacy exchange
- Each QHIN has its own onboarding process and technical requirements
- Data quality varies — not all participants send equally structured or complete data
- Privacy and consent management across state lines remains complex
CMS Interoperability Rules: The Deadlines Are Real
CMS has been tightening interoperability requirements through a series of final rules. The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) is now in effect, with key provisions phasing in through 2027.
What CMS Requires
Patient Access API (Already Required): Medicare Advantage plans, Medicaid managed care plans, state Medicaid/CHIP programs, and Qualified Health Plan (QHP) issuers on the federal exchange must provide patients access to their claims and clinical data via FHIR R4 APIs.
Provider Access API (2026): Payers must make patient data available to in-network providers at the patient's request via FHIR API. This is a significant shift — providers can now pull payer-held data programmatically rather than through fax and portal workflows.
Payer-to-Payer Data Exchange (2026): When a patient switches health plans, the old plan must transfer the patient's data to the new plan via FHIR API within a specified timeframe. This requires both plans to support standardized FHIR-based bulk data exchange.
Prior Authorization API (2027): Payers must implement a FHIR-based prior authorization API that allows providers to submit and check authorization requests electronically. This must include the specific reason for denial, turnaround time requirements, and decision status tracking.
The Technical Stack
CMS has standardized on specific FHIR implementation guides:
- CARIN Blue Button IG — for patient access to claims data
- Da Vinci PDex — for provider-payer data exchange
- Da Vinci PAS — for prior authorization
- US Core — as the baseline clinical data profile
If you are building for payers or provider-payer exchange, you need to be fluent in these implementation guides, not just base FHIR R4.
Payer-to-Payer Exchange: The Most Complex Mandate
The payer-to-payer data exchange requirement is technically the most challenging new mandate. When a patient enrolls in a new health plan, the new plan can request up to 5 years of clinical and claims data from the previous plan.
The Technical Challenge
Data volume: Five years of claims, encounters, medications, lab results, and clinical notes for a single patient can be substantial. Bulk FHIR export and import mechanisms are required.
Consent management: The patient must explicitly request the transfer. Both plans need to verify member identity, authenticate the request, and log the exchange.
Data mapping: Different payers code and structure data differently. A medication that one payer represents as a generic NDC code might be represented as a brand name by another. Reconciliation logic is non-trivial.
Timeline compliance: CMS specifies maximum turnaround times. Payers cannot drag their feet on data sharing.
Architecture Implications
Organizations implementing payer-to-payer exchange typically need:
- A FHIR server capable of bulk export and import (HAPI FHIR, Smile CDR, or cloud-native FHIR services)
- A member matching service to verify patient identity across plans
- A consent management system to capture and enforce patient data sharing preferences
- Data transformation pipelines to normalize incoming data into your internal data model
- Audit infrastructure to prove compliance with exchange timelines and data handling requirements
What's Coming Next
FHIR R5 Adoption (Slow but Steady)
FHIR R5 was released in March 2023 and introduces subscriptions (replacing the older Subscription resource with a topic-based model), improved medication management resources, and better support for clinical decision support. However, EHR vendor adoption has been slow. Epic has not yet committed to a full R5 timeline. For now, R4 remains the production standard.
AI and Interoperability
The intersection of AI and interoperability is the most interesting emerging trend. With TEFCA and CMS mandates increasing data liquidity, organizations are building AI models that leverage cross-system patient data. This creates new opportunities (population health analytics, predictive models) and new risks (bias from inconsistent data quality, privacy concerns with aggregated datasets).
State-Level Innovation
Some states are moving faster than federal mandates. California, New York, and Massachusetts have state-level HIE requirements that go beyond CMS rules. If you operate across multiple states, you need to track state-specific requirements alongside federal mandates.
How to Prepare
- Audit your current FHIR capabilities — can you import and export FHIR R4 bundles? Do you support the required implementation guides (CARIN, Da Vinci)?
- Inventory your data exchange partners — who are you exchanging data with today, and through what mechanisms? Where can you consolidate through TEFCA?
- Evaluate your consent infrastructure — do you have the systems to capture, enforce, and audit patient consent for data sharing?
- Budget for compliance — these mandates have hard deadlines. If you are behind, the time to invest is now, not Q4.
- Monitor the regulatory landscape — CMS continues to issue guidance and clarifications. Designate someone on your team to track changes.
Navigating the interoperability landscape? 1Putt Health helps health plans, health systems, and digital health companies design and implement FHIR-based data exchange systems that meet CMS mandates and TEFCA requirements. Book a Discovery Call to discuss your interoperability strategy.