The CMS Interoperability and Prior Authorization Final Rule is the biggest technology mandate health plans have faced in years. Here is what it requires, when, and how to be ready.
The short version
CMS-0057-F — the CMS Interoperability and Prior Authorization Final Rule, finalized in January 2024 — requires impacted health plans to stand up four HL7 FHIR APIs and modernize prior authorization. The headline deadline is January 1, 2027, when the four APIs must be in production. A set of prior-authorization process requirements lands a year earlier, on January 1, 2026. For most payers this is a multi-quarter engineering effort, not a quarter-end checkbox, and the clock is already running.
Which health plans have to comply
- Medicare Advantage organizations
- State Medicaid and CHIP fee-for-service programs
- Medicaid and CHIP managed care plans
- Qualified Health Plan (QHP) issuers on the Federally-Facilitated Exchanges
Commercial and ERISA plans are not directly covered, but many adopt the same FHIR standards voluntarily because providers and members increasingly expect them.
The four APIs you have to build
- Patient Access API (expanded). You likely already have one from CMS-9115-F; CMS-0057-F now requires it to include prior authorization information.
- Provider Access API (new). Lets in-network providers retrieve claims, encounter, and clinical data for the patients they treat.
- Payer-to-Payer API (new). Exchanges a member’s data with their previous or concurrent plan when they switch coverage.
- Prior Authorization API (new). The hardest of the four: a FHIR interface built on the HL7 Da Vinci CRD, DTR, and PAS implementation guides that lets providers check whether a service needs prior auth, see required documentation, and submit the request directly from their EHR.
The prior-authorization requirements that hit in 2026
Separate from the APIs, CMS-0057-F tightens the prior authorization process starting January 1, 2026:
- Faster decisions — expedited requests answered within 72 hours, standard requests within 7 calendar days.
- Specific denial reasons — payers must tell providers why a request was denied.
- Public reporting — plans must publish prior-authorization metrics annually.
Why this is harder than it looks
- You need a conformant FHIR R4 server aligned to US Core and the Da Vinci guides, not a general API gateway.
- Your data has to be mapped to FHIR. Most payer data lives in claims systems, EDI/X12 feeds, and enrollment databases that look nothing like FHIR resources.
- The prior-authorization workflow spans systems — utilization management, clinical criteria, provider portals, and the EHR — all of which must speak the same FHIR dialect.
- Everything has to pass conformance and security testing before go-live, which takes time you have to plan for.
This is why payers that wait until 2026 to start are the ones who struggle. A realistic build-and-test cycle runs several quarters.
A readiness path that works
- Assess. Inventory what you have and map it against the four required APIs.
- Prioritize. The Prior Authorization API and its Da Vinci workflow carry the most risk, so scope those first.
- Build the data layer. Stand up or extend a FHIR R4 server and build the pipelines that map claims, clinical, and enrollment data into FHIR.
- Implement the APIs against the CMS and Da Vinci implementation guides.
- Test and certify — conformance, security, and real provider workflows — with margin before January 2027.
How EIXSYS helps
EIXSYS is a Round Rock, Texas technology company that builds CMS-0057-F and payer interoperability software end to end: the four required FHIR APIs, the data mapping across HL7, FHIR R4, and EDI/X12 that feeds them, and the automation and reporting to operate them. Delivery is SOC 2 Type II audited, HIPAA business-associate ready, and ISO 27001 aligned, with security verified by independent audit, which matters when you answer to regulators.
Every engagement starts with a free readiness assessment that maps your current stack against the 2027 requirements and lays out a prioritized, costed path, so you see the work before you commit.