CMS-0057-F is often described as “the 2027 deadline,” but that’s a simplification. The rule phases in across several dates, and some requirements are already enforceable today. If you’re a regional health plan, missing the early operational dates is a more immediate risk than the headline API deadline. Here’s the full timeline, what’s actually in force, and what happens if you’re late.
What’s already in force
Two sets of requirements took effect ahead of the API deadline, and they apply now:
- Prior-authorization turnaround times — 72 hours for expedited/urgent requests and 7 calendar days for standard requests. Plans must also give a specific reason for any denial.
- Public prior-authorization reporting — plans must publicly report aggregate metrics on prior-auth requests, approvals, denials, and appeal outcomes.
These are operational and reporting obligations — they don’t require the FHIR APIs, but they do require your prior-auth workflow and data reporting to already be in shape.
The January 1, 2027 deadline
By January 1, 2027, affected plans must have four FHIR APIs running in production:
- Patient Access API (expanded to include prior-auth data)
- Provider Access API
- Payer-to-Payer API
- Prior Authorization API (the Da Vinci FHIR workflow — see our deep dive on CRD, DTR, and PAS)
“In production” is the operative phrase. A sandbox that passes a connectathon is not compliance. The API has to be live, documented, and serving real requests from the compliance date.
Who the rule applies to
- Medicare Advantage organizations
- State Medicaid and CHIP fee-for-service programs
- Medicaid and CHIP managed care plans
- Qualified Health Plan issuers on the federally facilitated exchanges
What happens if you miss it
There is no single flat fine. The consequences are programmatic and reputational, which for a regulated plan can be worse than a penalty line item:
- Compliance action from CMS — non-compliance with program requirements can trigger corrective action plans and jeopardize contract standing for MA and Medicaid managed care.
- Public exposure — the prior-auth metrics are public, so gaps are visible to providers, members, and competitors.
- Operational drag — providers increasingly expect electronic prior auth; plans that can’t support it lose network goodwill.
Why the real deadline is sooner than 2027
Standing up four production FHIR APIs on top of legacy claims data is a 9–15 month program for most regional plans, not a quarter of work. If you want them live and tested by January 1, 2027, the practical start date is already behind you or arriving fast. The slowest part is almost never the FHIR layer — it’s getting the underlying claims and encounter data clean and mapped, which is why we treat data mapping as the real work.
Want to know exactly where you stand against each date? Take the 2-minute CMS readiness check or book a readiness assessment and we’ll map your gaps to the timeline.