Skip to content
ushealthcloud

AI Automation

Prior authorization automation under CMS-0057-F

Short answer

CMS-0057-F requires Medicare Advantage plans and Medicaid and CHIP programs, including their managed care plans, to decide prior authorization requests within 72 hours for urgent and 7 calendar days for standard requests from January 1, 2026, and to offer a FHIR-based Prior Authorization API from January 1, 2027. Drugs are excluded.

Published
Last reviewed
Reading time
3 min

Who counts as an impacted payer

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), published on February 8, 2024, applies to Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and issuers of qualified health plans (QHPs) on the federally facilitated exchanges (FFEs).

Not every provision applies to every payer. QHP issuers on the FFEs are excluded from the new decision timeframes, for example, although they must still report prior authorization metrics. The rule’s prior authorization provisions also exclude drugs.

What has applied since January 1, 2026

  • Decision timeframes: 72 hours for expedited (urgent) requests and 7 calendar days for standard requests. For Medicare Advantage, the standard timeframe was previously 14 days.
  • A specific reason for every denied request, however the request was submitted.
  • Public reporting of prior authorization metrics on the payer’s website every year. The first set of metrics was due March 31, 2026.

What applies from January 1, 2027

  • Prior Authorization API: a FHIR-based interface that lets a provider’s systems check whether prior authorization is required, see the documentation the payer needs, submit the request and receive its status and decision.
  • Prior authorization information added to the Patient Access API, plus new Provider Access and Payer-to-Payer APIs.

Some compliance dates vary by payer type, such as Medicaid and CHIP programs, so check the rule for your exact deadlines.

Where automation helps

  • Intake and triage: classifying incoming requests by urgency and service so the 72-hour clock is never missed.
  • Packet assembly: gathering the clinical documentation a request needs from attachments and connected systems.
  • Criteria checks: comparing the documentation against the payer’s published criteria and showing which criteria are met, missing or unclear.
  • Routing: sending complete, clear-cut requests to the right reviewer queue and asking for missing information early.
  • Drafting: preparing determination letters, including the specific denial reason the rule requires, for a reviewer to confirm.

Where licensed reviewers decide

Automation gathers, checks and routes. Determinations stay with qualified people. For Medicare Advantage, an adverse decision based on medical necessity must be reviewed by a physician or other appropriate health care professional with the right expertise (42 CFR 422.566(d)). CMS has also said that algorithms and AI may assist coverage decisions, but each decision must reflect the individual patient’s circumstances.

Measuring turnaround and override rates

  • Turnaround time by urgency and service type, and the share of decisions made within 72 hours or 7 days.
  • Pend rate: how often requests stall for missing information.
  • Override rate: how often reviewers change what automation prepared. A rising rate is the signal to retune.
  • Appeal overturn rate: how often denials are reversed on appeal.

Several of these line up with the metrics impacted payers must publish, so measuring them well serves compliance and operations at the same time.

Frequently asked questions

When do the CMS-0057-F decision timeframes start?
January 1, 2026. Impacted payers must decide expedited requests within 72 hours and standard requests within 7 calendar days.
Does CMS-0057-F apply to prescription drugs?
No. The rule’s prior authorization provisions, including the decision timeframes and the Prior Authorization API, exclude drugs.
Do QHP issuers on the exchanges have to meet the 72-hour and 7-day timeframes?
No. QHP issuers on the federally facilitated exchanges are excluded from the decision timeframes, but other provisions, such as metrics reporting, apply to them.
What standard does the Prior Authorization API use?
HL7 FHIR. CMS recommends the HL7 Da Vinci implementation guides for coverage requirements discovery, documentation templates and rules, and prior authorization support.

Sources

General information, not legal or medical advice.

Next step

Bring us the data problem your compliance team worries about most.

We'll map where protected health information flows today, and how to model, automate and secure it.

What the first call gives you

  1. 1A map of where PHI flows today
  2. 2One workflow worth starting with
  3. 3The controls that workflow needs

A short scoping call, then a written proposal. Please don't send patient information.