The CMS Interoperability and Prior Authorization rule (CMS-0057-F), explained

CMS-0057-F gave Medicare Advantage, Medicaid, CHIP and Exchange plans prior authorization deadlines and public metrics from 2026, and four FHIR APIs to build by 2027. Later rules in 2026 eased the provider measure and proposed adding drugs.

Who the rule covers

CMS published the Interoperability and Prior Authorization final rule (CMS-0057-F, 89 FR 8758) on February 8, 2024, effective April 8, 2024. It applies to what it calls impacted payers: 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 on the Federally-facilitated Exchanges. It also adds an Electronic Prior Authorization measure for hospitals and clinicians in Medicare’s Promoting Interoperability programs [1].

The rule does two separate things on two separate timetables. It changes how payers run prior authorization, with dates in 2026, and it requires payers to build or extend four FHIR application programming interfaces, with dates in 2027 [1]. Its prior authorization requirements cover items and services and do not apply to drugs of any type [1].

How each payer type reads a date

Most compliance dates in the rule are expressed three ways. Medicare Advantage organizations and state Medicaid and CHIP fee-for-service programs comply by January 1 of the year. Medicaid managed care plans and CHIP managed care entities comply by the rating period beginning on or after January 1 of that year. Exchange QHP issuers comply for plan years beginning on or after January 1 of that year [1].

Prior authorization process changes from 2026

From the 2026 dates, payers must send providers a notice when they make a prior authorization decision, and a denial must include a specific reason, whatever channel the request arrived through [1] [2].

Payers other than Exchange QHP issuers must also decide within set timeframes: 72 hours for expedited requests, unless state law sets a shorter minimum, and 7 calendar days for standard requests, with a possible extension of up to 14 days in certain circumstances [1].

All impacted payers must post prior authorization metrics on their websites once a year. For a Medicare Advantage organization, the regulation says that beginning in 2026 it reports the previous calendar year’s data at contract level by March 31 [2]. The data include:

  • a list of all items and services that require prior authorization;
  • the percentages of standard and of expedited requests approved and denied;
  • the percentage of standard requests approved after appeal, and of requests approved after the review timeframe was extended;
  • the average and median time from submission to decision, for standard and for expedited requests [2].

Separately, starting January 1, 2026, payers report to CMS each year certain metrics on patient data requests made through the Patient Access API [1].

The four APIs due in 2027

The API requirements build on the Patient Access API that the 2020 Interoperability and Patient Access final rule already required, and use HL7 FHIR Release 4.0.1 with the implementation specifications CMS identifies for each API [1].

  • Patient Access API: extended to include information about certain prior authorizations [1].
  • Provider Access API: new. Providers with a contractual relationship with the payer and a treatment relationship with the patient can retrieve adjudicated claims and encounter data (without provider remittances and patient cost-sharing), the data classes in the United States Core Data for Interoperability, and prior authorization information. Patients can opt out, and payers must share educational resources [1].
  • Payer-to-Payer API: new. With the patient’s permission, a new payer requests data from the previous payer no later than one week after coverage starts or at the patient’s request, and integrates what it receives. The exchange covers five years of data, and concurrent payers exchange data at least quarterly [1].
  • Prior Authorization API: new. It tells a provider whether an item or service needs prior authorization and what documentation the payer requires, supports a HIPAA-compliant request and response, and returns the decision, with a specific reason for any denial [1] [2].

On February 28, 2024, CMS’s National Standards Group announced enforcement discretion: it will not take HIPAA Administrative Simplification enforcement action against covered entities that choose not to use the X12 278 standard as part of an electronic FHIR prior authorization process [3].

What providers report

The rule added an Electronic Prior Authorization measure, a yes or no attestation, starting with the CY 2027 reporting period for eligible hospitals and critical access hospitals and the CY 2027 performance period for MIPS clinicians [1]. Two 2026 payment rules changed that start. The FY 2027 hospital inpatient rule made the measure optional for hospitals in CY 2027, worth 10 bonus points, and required a “Yes” attestation or an exclusion from the CY 2028 reporting period, with the measure unscored [4]. The CY 2027 physician fee schedule rule, published November 9, 2026, made the measure optional and worth 10 bonus points for MIPS clinicians in the CY 2027 performance period [5].

A later proposal that would add drugs and standards

On April 14, 2026, CMS published a proposed rule (91 FR 19890) that would extend many of these prior authorization requirements to drugs, bring small group QHP issuers on the federally-facilitated SHOP Exchanges in as impacted payers, require payers to report their API endpoints to CMS, and turn implementation guides that CMS-0057-F only recommends into requirements [6]. For the Prior Authorization API it proposed requiring the HL7 Da Vinci Coverage Requirements Discovery, Documentation Templates and Rules, and Prior Authorization Support guides, with an October 1, 2027 date to conform; the proposal states it would not change the 2027 dates for building the APIs [6].

The August 4, 2026 hospital rule finalized ONC’s updated versions of those guides for health IT certification [4]. As checked on November 14, 2026, we found no final rule adopting the payer proposals: the Federal Register lists only the proposal and a correction to the hospital rule under the proposal’s regulation identifier [7].

Dates to plan around

  • 2026 dates: decision timeframes, specific denial reasons and provider notices; Patient Access API metrics to CMS each year [1].
  • By March 31 each year, beginning in 2026 (the Medicare Advantage text): prior authorization metrics for the previous calendar year posted on the payer’s website [2].
  • 2027 dates: Patient Access API with prior authorization data, Provider Access API, Payer-to-Payer API and Prior Authorization API [1].
  • CY 2027: optional Electronic Prior Authorization measure for hospitals and MIPS clinicians [4] [5].
  • CY 2028: hospitals attest “Yes” or claim an exclusion [4].

The steps a payer can take, in order, are in the companion CMS-0057-F checklist. Moraph’s teams help organizations with work like this; see our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • CMS-0057-F
  • prior authorization
  • FHIR
  • Patient Access API
  • Provider Access API
  • Payer-to-Payer API
  • Medicare Advantage
  • Medicaid