Checklist: payers getting ready for the CMS-0057-F API and prior authorization dates

Twelve steps for Medicare Advantage organizations, Medicaid and CHIP programs and plans, and Exchange QHP issuers: the prior authorization rules in force since 2026, the March 31 reports, and the four APIs due in 2027.

Which payers and which dates

The CMS Interoperability and Prior Authorization final rule (CMS-0057-F) was published on February 8, 2024 and took effect on April 8, 2024 [1]. It applies to “impacted payers”: Medicare Advantage (MA) organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on the Federally-facilitated Exchanges [1]. It runs on two sets of dates. Prior authorization process changes started in 2026: by January 1, 2026 for MA organizations and state fee-for-service programs, by the rating period beginning on or after that date for managed care, and for plan years beginning on or after that date for QHP issuers. The API requirements follow the same pattern a year later, in 2027 [1]. CMS’s own page on the rule says the same [10].

How the steps are built

We cite the MA sections in 42 CFR part 422 as the worked reference; the rule adds parallel sections for the other payer types, such as 42 CFR 431.80, 438.210 and 457.495 and 45 CFR 156.223 [7] [8] [9]. Each step says where a duty comes from, and marks suggestions as such. The owner under each step is a typical assignment, not one the rule names. As checked on November 14, 2026, a further CMS proposal from April 14, 2026 on prior authorization for drugs and required implementation guides is not final [11] [12]; the last step covers it. Not legal advice.

The checklist

Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.

  1. Regulatory compliance

    The rule ties dates to payer type: calendar dates for MA organizations and state fee-for-service programs, rating periods for Medicaid and CHIP managed care, and plan years for QHP issuers on the Exchanges [1].

  2. Utilization management leadership

    Required since January 1, 2026 for MA organizations by section 422.122(a), which excludes drugs [2]; the QHP and state equivalents carry the same 2026 start, for example 45 CFR 156.223 and 42 CFR 431.80 [9] [1].

  3. Utilization management operations

    For MA, section 422.568(b)(1)(ii) sets 7 calendar days for standard decisions on items and services under section 422.122 from January 1, 2026, and section 422.572(a)(1) sets 72 hours for expedited decisions [5] [6]. Medicaid managed care contracts must set the same limits for rating periods starting on or after January 1, 2026 (section 438.210(d)), and CHIP state plans from January 1, 2026 unless they follow existing state law on prior authorization (section 457.495(d)(2)) [7] [8]. These sections allow extensions of up to 14 days in set cases. QHP issuers on the Exchanges were not given these timeframes [1].

  4. Utilization management analytics and web team

    Section 422.122(c) requires MA organizations to post, by March 31 each year from 2026, the list of items and services needing prior authorization and the listed approval, denial, appeal, extension and timing measures for the previous calendar year [2]. Using CMS’s Prior Authorization Metrics Report template is our suggestion [10].

  5. Interoperability program office

    Section 422.119(f) requires MA organizations, beginning in 2026, to report aggregated, de-identified Patient Access API usage metrics for the previous calendar year by March 31 [4].

  6. API engineering

    The rule requires impacted payers to include information about certain prior authorizations in the Patient Access API from the 2027 compliance dates [1].

  7. API engineering with provider network management

    Section 422.121(a) requires, from January 1, 2027, an API giving in-network providers member data with dates of service from January 1, 2016, excluding remittances and cost-sharing, within 1 business day of a request; an attribution process; an opt-out available before data first flows; and member and provider resources written in clear, non-technical terms [3].

  8. API engineering with enrollment operations

    Section 422.121(b) requires, from January 1, 2027, an opt-in process offered to new members no later than 1 week after the coverage start date or after CMS accepts the enrollment, whichever is later, identification of previous and concurrent payers, and exchange of data with dates of service within 5 years before the request [3]. Section 422.121(b)(6) also requires requests to concurrent payers at least quarterly while the member is enrolled with both [3].

  9. API engineering with utilization management

    Section 422.122(b) requires this API from January 1, 2027, excluding drugs, conformant with the FHIR standards it cites in 45 CFR 170.215 [2]. The rule names HL7 FHIR Release 4.0.1 as the base standard [1].

  10. EDI and architecture leads, with counsel

    CMS reports that on February 28, 2024 its National Standards Group announced it will not take HIPAA Administrative Simplification enforcement action against covered entities that choose not to use X12 278 in a FHIR-based prior authorization process under this rule [10]. This is enforcement discretion, not a rule change.

  11. Architecture lead

    Good practice under the current rule, which strongly recommends implementation guides beyond the required standards [1]. The April 2026 proposal would require conformance to these three guides with an October 1, 2027 compliance date [11], and ONC finalized updated versions of them in the FY 2027 IPPS final rule [12].

  12. Regulatory affairs and pharmacy benefit leadership

    Proposed only, as checked on November 14, 2026. The proposal would require electronic prior authorization for all drugs through the Prior Authorization API and NCPDP standards from October 1, 2027, and would require impacted payers to report their API endpoints to CMS; comments closed June 15, 2026 [11]. The FY 2027 IPPS final rule finalized only ONC’s standards updates from that proposal and says comments on its other proposals are still being reviewed and considered [12]. State fee-for-service programs and QHP issuers can also request an extension, exemption or exception under the 2024 rule [1].

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

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