A few weeks ago, our CPO, Tim Bond, was quoted in TechTarget's SearchCIO on a problem showing up in nearly every enterprise AI conversation right now: companies want to move fast on AI, but their data isn't ready for it. Not because the models are weak but because the data underneath them is messy, inconsistent, and locked in formats nobody quite owns.
We're seeing the exact same failure pattern show up in a completely different conversation: the January 1, 2027 FHIR compliance deadline for health insurance payers.
It's not a coincidence. It's the same root cause wearing a different mask.
The deadline everyone's racing toward
CMS-0057-F — the Interoperability and Prior Authorization Final Rule — requires every Medicare Advantage, Medicaid, CHIP, and Marketplace payer in the country to have four live FHIR R4 APIs in production by January 1, 2027: Prior Authorization, Provider Access, Payer-to-Payer, and an expanded Patient Access API. HL7 FHIR (Fast Healthcare Interoperability Resources) is a healthcare interoperability standard designed to support the exchange of health information across systems using structured interoperability resources. CMS estimates the shift will save the U.S. healthcare system roughly $15 billion over the next decade by finally retiring fax- and phone-based prior authorization for good.
The deadline isn't the hard part. Most payers can build an API endpoint. The hard part is what has to flow through it.
The part nobody's talking about
Talk to payers who are behind schedule (and most are) and the conversation almost never stays on APIs for long. It moves to the data underneath: claims still running on decades-old EDI X12 transactions, medical necessity criteria buried in PDFs and proprietary tools, patient records that don't match cleanly across systems that were never designed to talk to each other.The challenge is not simply implementing an API (application programming interface). The real issue is preparing the underlying health data so it can be transformed into usable FHIR data and exchanged through modern interoperability frameworks.
That's not a FHIR problem. That's a data readiness problem. It's the same one Tim was describing to TechTarget, just wearing a compliance deadline instead of an AI roadmap.
A few examples of where it shows up:
- Claims data is still in EDI X12 — authorizations in EDI 278, claims in EDI 837, attachments in EDI 275. The mandate requires a FHIR API, but the data feeding it often isn't a FHIR resource. Payers must reliably transform legacy data into standardized interoperability resources while maintaining accurate data exchange across systems.
- Business rules are locked away, not written down. The Da Vinci DTR guide requires payers to surface their actual medical necessity criteria inside a provider's EHR workflow — but that criteria usually lives in a PDF policy document or a proprietary tool, not in structured, machine-readable form.
- Patient identity doesn't match across systems. When a member switches plans, their new payer has to pull historical records from the old one. Without a universal patient ID, matching that person accurately — especially across a name change, a move, or a common name — is a genuine data problem, not an API problem.
None of these get solved by standing up an endpoint. They get solved by fixing what feeds it.
The pattern is the point
Whether it's an AI initiative that stalls because the training data is inconsistent, or a compliance deadline that's at risk because claims data can't be cleanly transformed into FHIR resources, the failure mode is identical: teams invest in the technology layer and skip the data layer underneath it, then wonder why the technology doesn't deliver.
FHIR provides a common specification for representing and exchanging healthcare information, but successful FHIR implementation depends on the quality and structure of the underlying data. A FHIR resource can only deliver value when the health record and supporting information are accurate, consistent, and accessible across systems.
Seven in ten payers are behind on FHIR readiness right now, by most industry estimates. The ones who close that gap in time won't be the ones who found the best FHIR platform. They'll be the ones who got their data ready to feed it — the same unglamorous, unavoidable work Tim was describing weeks ago, just under a different deadline.
If your team is staring down January 2027 and isn't sure whether the blocker is the APIs or the data behind them, that's worth a real look before the deadline makes the decision for you.
FAQs
Is Your Data Ready for FHIR Compliance?
Prepare your healthcare data for seamless interoperability with Adeptia’s data integration solutions. Connect, transform, and manage complex health data workflows to support FHIR readiness.