If you run IT or compliance for a health plan, “the four FHIR APIs” is the phrase that now defines your 2027. CMS-0057-F — the Interoperability and Prior Authorization Final Rule — requires impacted payers to run four FHIR R4 APIs in production by January 1, 2027. Here’s what each one actually is, in plain English.
Who this applies to
Medicare Advantage organizations, Medicaid and CHIP managed care, state Medicaid agencies, and QHP issuers on the federally facilitated exchanges. If you’re one of these, the four APIs are not optional.
The four required APIs
- Patient Access API. Lets your members pull their own claims, encounter, clinical, and prior-authorization data into third-party apps they choose. It extends the earlier Patient Access requirement to include prior-auth information.
- Provider Access API. Lets in-network providers pull member data from you to support care — claims, encounters, clinical data, and prior-auth — with the right attribution and opt-out handling.
- Payer-to-Payer API. Lets you exchange a member’s data with their prior or concurrent payers, so history follows the member instead of starting over at every plan change.
- Prior Authorization API. A FHIR-based prior-authorization workflow built on the HL7 Da Vinci implementation guides — automating the request, documentation, and decision exchange between provider and payer.
What’s already in force (don’t forget these)
The API deadline gets the attention, but two operational requirements are already live: prior-authorization turnaround times (72 hours for urgent, 7 calendar days for standard) and public reporting of prior-authorization metrics. If you’re not meeting those today, that’s the more immediate exposure.
Why this is harder than it looks
The APIs themselves are the visible part. The hard part is underneath: mapping legacy claims and encounter data to FHIR R4, building the pipelines and reconciliation that keep those APIs accurate, and passing conformance and security review — all while your internal team is already at capacity. Plans that treat this as a data-and-integration program (not just an API project) are the ones that make the deadline calmly.
The four APIs are the requirement. A clean, reconciled data layer feeding them is what actually gets you there.
Want to see where your four APIs stand? Take the 2-minute CMS-0057-F readiness check, or book a readiness assessment — we map your current state, flag the top gaps, and lay out a prioritized path to January 2027.
This article reflects CMS-0057-F as generally published; confirm specifics against current CMS guidance before acting.