Rule at a glance
- Rule
- CMS-0057-F
- Status
- Final rule (published February 8, 2024)
- Affects
- Medicare Advantage organizations
- State Medicaid and CHIP fee-for-service agencies
- Medicaid and CHIP managed care plans
- Qualified health plan issuers on Federally-Facilitated Exchanges
- Key dates
- January 1, 2026: decision time frames of 72 hours (expedited) and 7 calendar days (standard), where they apply
- January 1, 2027: API requirements, with the exact date varying by payer type
- The rule sets no single deadline: dates and obligations differ by program.
- For most payers the API compliance date is January 1, 2027; decision clocks of 72 hours and 7 calendar days took effect January 1, 2026 where they apply.
- Readiness should be scored per API and per shared dependency, on one five-level scale.
1.1 Program applicability, regulatory citations and compliance dates
CMS-0057-F (89 FR 8758, Feb. 8, 2024) does not impose one uniform deadline or rule set across all market participants. Confirm exact legal applicability by program, contract/rating cycle, and approved federal/state exceptions before locking remediation schedules.
Table 1. Applicability by regulated cohort
| Regulated cohort / program | Governing API and operational citations | API compliance date | Decision clocks, reporting and key scope boundaries |
|---|---|---|---|
| Medicare Advantage (MA) Organizations | Patient Access: 42 CFR § 422.119 Provider Access: 42 CFR § 422.121(a) Payer-to-Payer: 42 CFR § 422.121(b) Prior Auth API & Denials/Metrics: 42 CFR § 422.122(a)–(c) Decision Clocks: 42 CFR §§ 422.568(b)(1)(ii), 422.572 |
January 1, 2027 | 72 hours (expedited) / 7 calendar days (standard) effective Jan 1, 2026; specific denial reason (§ 422.122(a)); annual public PA metrics by March 31 (§ 422.122(c)); annual Patient Access usage reporting to CMS (§ 422.119(f)). Excludes drugs. |
| State Medicaid & CHIP FFS Agencies | Medicaid FFS: 42 CFR §§ 431.60, 431.61(a)–(b), 431.80, 440.230(e) Separate CHIP FFS: 42 CFR §§ 457.730, 457.731, 457.732, 457.495(d) (Medicaid Expansion CHIP follows Medicaid rules per § 457.700(c)) |
January 1, 2027 (subject to CMS-approved state extension or exemption processes) | 72h expedited / 7 calendar days standard clocks effective Jan 1, 2026. Verify in writing whether the state agency holds a CMS-approved extension or exemption for Provider Access, Payer-to-Payer, or Prior Auth APIs. Excludes drugs. |
| Medicaid Managed Care (MCO, PIHP, PAHP) & CHIP Managed Care | Medicaid MCO: 42 CFR §§ 438.242(b)(5)–(7), 438.210(d), 438.210(f) CHIP MCO: 42 CFR § 457.1233(d) |
By the rating period beginning on or after January 1, 2027 | Verify each state contract's exact rating-period start date (e.g., Jan 1 vs. July 1 vs. Oct 1, 2027) and any stricter state turnaround mandates. Excludes drugs. |
| QHP Issuers on Federally-Facilitated Exchanges (FFEs) | Patient Access: 45 CFR § 156.221 Provider / P2P: 45 CFR § 156.222(a)–(b) Prior Auth: 45 CFR § 156.223 |
Plan years beginning on or after January 1, 2027 (subject to FFE QHP exception authority, e.g., § 156.221(h) / § 156.223(d)) | Not subject to CMS-0057-F's 72-hour / 7-day decision-clock change (existing federal/ACA turnaround rules govern unless CMS-0062-P is finalized). Specific denial reasons and annual PA metrics still apply. Excludes drugs. |
| Eligible Hospitals & CAHs (Promoting Interoperability) | FY 2027 IPPS / LTCH PPS Final Rule (CMS-1849-F, 91 FR 49570, Aug. 4, 2026) | Optional bonus in CY 2027; Mandatory beginning CY 2028 | Providers do not host CMS-0057-F payer APIs. Hospitals prepare EHR workflows to consume payer Prior Auth APIs for Promoting Interoperability ePA reporting. |
| MIPS-Eligible Clinicians (Quality Payment Program) | CY 2027 PFS Final Rule (CMS-1848-F, Nov. 2026) | Optional bonus in CY 2027; Mandatory per QPP schedule (CY 2028) | Clinicians have no Jan 1, 2027 API hosting mandate; practices evaluate certified EHR readiness (45 CFR § 170.315(g)(31)–(33)) and payer endpoint availability. |
Note · Historical market context
Bounded snapshots; verify locally. Earlier industry snapshots, such as WEDI's February 2026 survey (n = 86 total respondents across payers, clearinghouses, vendors, and ~4 providers) and Artificer Health's April 2026 scan of n = 48 public payer FHIR endpoints, highlighted substantial variation in implementation progress during H1 2026. Because sample sizes were small, public endpoint scans miss private partner gateways, and months have elapsed, treat external figures solely as background context and assess your organization's actual API-by-API readiness directly.
1.2 Unified maturity scale (L0–L4) and executive readiness dashboard
Organization-wide status labels obscure single-point compliance failures. Assess each API and shared dependency independently using one consistent five-level definition across all teams:
- L0. Not implemented. No active build or provisioned environment covering the required regulatory scope.
- L1. Built and smoke-tested. Core endpoints and schemas exist in dev/staging; synthetic connectivity and basic syntax checks only.
- L2. Conformant and content-validated within defined scope (requires both L2a and L2b).
- L2a, technical conformance: passes automated standard/IG validation suites (e.g., ONC Inferno / Touchstone) for claimed profiles, OAuth/SMART flows, and discovery metadata.
- L2b, data and clinical content validation: audited against production-representative claims, USCDI, attribution, permission/opt-out, medical policy, and specific denial-reason source records within explicitly documented scope boundaries.
- L3. Representative external partner journeys tested. Completed end-to-end authentication, request/response, permission/attribution filtering, and negative/error-handling scenarios with external EHR, consumer app, clearinghouse, or peer-payer counterparties.
- L4. Operationally verified (specify environment explicitly). SLA clocks, exception queues, audit logs, and support runbooks verified, explicitly distinguishing L4-PreProd (parallel shadow run in staging/pre-production) from L4-Prod (live production verification).
API and shared-dependency executive scorecard
Table 2. Executive scorecard
| Mandate / shared dependency | Current level | Primary technical or legal gap | Launch disposition target | Accountable executive |
|---|---|---|---|---|
| 1. Patient Access API (PA additions) 422.119(b)(1)(iv) & parallels: non-drug PA status, dates, approved items, specific denial reason, structured provider docs; 3-part timing verified |
L__ | |||
| 2. Provider Access API 422.121(a) & parallels: claims/encounters excl. remittances/cost-sharing, USCDI, non-drug PA data from Jan 1, 2016 within 1 business day; attribution & enrollee opt-out |
L__ | |||
| 3. Payer-to-Payer API 422.121(b) & parallels: 5-yr lookback excl. remittances, cost-sharing, drugs & denied PAs; enrollee opt-in; 1-wk request / 1-day response / quarterly concurrent |
L__ | |||
| 4. Prior Authorization API 422.122(b) & parallels: covered non-drug items/services requiring PA, documentation rules, PA request/response, specific denial reasons |
L__ | |||
| Dep A: Medical policy and documentation content Structured PA service list & documentation rules across applicable covered medical items/services |
L__ | |||
| Dep B: Delegated UM / specialty benefit managers Radiology, cardiology, oncology, musculoskeletal, behavioral health TPAs |
L__ | |||
| Dep C: Identity, attribution and enrollee choice controls Authentication/Identity vs. Provider Attribution vs. Enrollee Opt-Out [Provider Access] vs. Enrollee Opt-In Permission [Payer-to-Payer] vs. 42 CFR Part 2 / state-sensitive filtering |
L__ | |||
| Dep D: Operational clocks, queues and public reporting 72h/7d clocks where applicable, specific denial mapping, March 31 PA metrics & Patient Access usage reporting |
L__ |