CMS-0057-F · Payer Compliance
The deadline doesn't move. Your data should.
Every Medicare Advantage, Medicaid, CHIP, and Marketplace payer must expose four live FHIR R4 APIs by January 1, 2027. The blocker isn't the API. It's the legacy EDI X12 and clinical data underneath it. That's exactly where Adeptia works.
What This Means
What CMS-0057-F actually requires
Every impacted payer must expose four production-live FHIR R4 APIs by January 1, 2027, and fully retire fax- and phone-based prior authorization.
- Prior Authorization API
Providers check requirements and submit requests electronically — no fax or phone.
- Provider Access API
In-network providers pull a patient's full claims and clinical history in bulk.
- Payer-to-Payer API
When a member switches plans, their history follows automatically.
- Patient Access API (expanded)
Members track prior authorization status through third-party health apps.
“Every payer must expose FHIR APIs by January 1, 2027 — most haven't started the data work that makes that possible.”
Why Now
The hard part isn't the API. It's the data underneath it.
Your claims and clinical systems still run on legacy EDI X12 — not FHIR. Someone has to transform that data reliably, on a fixed deadline. That's not an API problem. It's a data transformation problem. And it's exactly what Adeptia does.
How Adeptia Helps
Where Adeptia fits
- X12-to-FHIR Translation
Your prior authorization and claims systems run on X12 278/837. Adeptia's translation engine maps Da Vinci PAS FHIR resources bidirectionally to X12 — no system replacement required.
- Turn Policy PDFs Into Structured Rules (DTR)
Medical necessity criteria trapped in PDFs or InterQual/MCG doesn't work inside a provider's EHR. Adeptia's Intelligent Document Processing converts policy documents into structured, auditable data for Da Vinci DTR Questionnaires.
- Patient Identity Matching ($member-match)
No universal health ID makes cross-payer matching hard and privacy-sensitive. Adeptia's EMPI-style matching resolves identities accurately for Payer-to-Payer compliance — with minimal manual IT intervention.
- Bulk FHIR at Scale
The Provider Access API means sharing data for entire clinic groups at once. Adeptia stages legacy data into a scalable FHIR store and serves Bulk FHIR (NDJSON) requests without touching core production systems.
Evaluation Criteria
What to look for in any FHIR compliance vendor
- HL7 Da Vinci compliance out of the box (CRD, DTR, PAS)
- Security and consent via SMART on FHIR, OAuth 2.0, OpenID Connect
- Scalable enough to handle peak prior authorization traffic without lag
- Works with your existing systems — no core replacement required
Frequently asked questions
- What exactly does CMS-0057-F require?
It requires impacted payers to run four production-live FHIR R4 APIs — Prior Authorization, Provider Access, Payer-to-Payer, and an expanded Patient Access API — and to fully retire fax- and phone-based prior authorization, all by January 1, 2027.
- What happens if we miss the January 1, 2027 deadline?
The date is a fixed federal deadline with no announced extensions. Non-compliant payers face CMS enforcement and audit exposure, and — just as costly — providers and members increasingly expect the electronic prior-authorization and data-access experience the rule mandates.
- Do we have to replace our core claims/clinical systems?
No; CMS explicitly allows a translation layer in front of existing systems.
- How is Adeptia different from FHIR-native platform vendors?
We don't build your API endpoints; we make sure the data feeding them is clean, structured, and compliant.
- How long does implementation take?
It depends on the state of your source data, but because Adeptia connects to your existing claims and clinical systems rather than replacing them, most payers scope this in weeks — not the multi-quarter timelines a core-system replacement would require. A 30-minute readiness assessment gives you a concrete estimate.