Who is on the clock

CMS-0057-F applies to the government-program side of the payer market. If a plan falls in one of these buckets, the 72-hour and 7-calendar-day decision timeframes already govern it, and the 2027 API mandate is coming for it next.

The CMS-0057-F deadline timeline

1. Jan 1, 2026 · Live

   Decision timeframes take effect

   Impacted payers must decide expedited prior authorization requests within 72 hours and standard requests within 7 calendar days. Every urgent request your team submits to a covered payer now carries a regulatory clock, not just a contractual one.

2. Mar 31, 2026 · Live

   First public PA metrics posted

   Public prior authorization metrics reporting for CY2025 was due March 31, 2026. For the first time, each covered payer's own prior authorization performance is published, in the payer's own numbers, on the payer's own site.

3. Aug 2026 · You are here

   The window to act on the data

   The metrics are public, the clocks are enforceable, and most provider organizations have not pulled either into their appeals or contracting workflows yet. This is the gap worth closing before the January 2027 API wave arrives.

4. Jan 1, 2027 · Ahead

   Four FHIR APIs must be live

   The Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization APIs are due January 1, 2027. The Prior Authorization API will expose documentation requirements machine-readably for the first time.

The four APIs due January 1, 2027

Why the published metrics are leverage, not trivia

For years, provider organizations argued about payer turnaround behavior with anecdotes. As of March 31, 2026, that era is over for MA, Medicaid, CHIP, and FFM QHP plans. Each covered payer has published its own CY2025 prior authorization metrics under CMS-0057-F. That means an appeal letter can now cite the payer's own published performance, and a network negotiation can put the payer's own numbers on the table next to your practice management data. When a covered payer misses the 72-hour expedited or 7-calendar-day standard timeframe on a 2026 request, you are no longer pointing at a vague industry norm. You are pointing at a federal rule, CMS-0057-F, and at the payer's own public reporting. Providers who pull, archive, and track these postings now will negotiate 2027 contracts from a different position than providers who never looked.

Operator to-do list for prior authorization teams

1. Pull the published CY2025 PA metrics from every covered payer you are contracted with, and archive dated copies so the baseline cannot quietly change.
2. Build a one-page payer scorecard comparing each payer's published performance against the 72-hour expedited and 7-calendar-day standard clocks.
3. Timestamp every prior authorization submission and decision in your own system, so you can prove a clock breach independently of the payer's records.
4. Add a standard paragraph to appeal templates citing CMS-0057-F decision timeframes and the payer's own published metrics where relevant.
5. Rank your payers by prior authorization volume to decide which Prior Authorization API connections to build or buy first in 2027.
6. Ask each covered payer, in writing, for its January 1, 2027 API implementation plan and developer onboarding process now, while there is still lead time.