CMS-0057 compliance for ambulatory surgery centers

CMS-0057, formally the CMS Interoperability and Prior Authorization final rule (CMS-0057-F), is a federal rule from the Centers for Medicare and Medicaid Services that requires certain payers to implement FHIR-based application programming interfaces for patient access, provider access, payer-to-payer data exchange, and prior authorization. The rule also sets new prior authorization decision timeframes and requires payers to provide a specific reason for denials. CMS released the rule on January 17, 2024, and it was published in the Federal Register on February 8, 2024.

The CMS-0057-F regulations became effective on April 8, 2024, but compliance obligations are phased. Impacted payers other than QHP issuers on the FFEs must meet the prior authorization decision timeframe and denial-reason requirements as of January 1, 2026. The API development and enhancement requirements take effect on January 1, 2027 for Medicare Advantage organizations and state Medicaid and CHIP fee-for-service programs; for the rating period beginning on or after January 1, 2027 for Medicaid managed care plans and CHIP managed care entities; and for plan years beginning on or after January 1, 2027 for QHP issuers on the FFEs.

CMS-0057 applies to Medicare Advantage organizations, state Medicaid fee-for-service programs, state CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan issuers on the Federally Facilitated Exchanges. CMS refers to these collectively as impacted payers. The rule does not apply to ERISA self-insured employer plans, workers’ compensation, auto and casualty carriers, or commercial group or individual plans sold outside the Federally Facilitated Exchanges.

No. CMS-0057 places obligations on covered payers, not on ambulatory surgery centers. ASCs experience the rule indirectly because the payers they bill must respond to prior authorization requests within defined timeframes, provide a specific denial reason, and expose prior authorization status and documentation requirements through FHIR APIs. ASC operations change with the payers’ implementation, but ASCs themselves are not required to build CMS-0057 infrastructure to be compliant.

For prior authorization requests on medical items and services, impacted payers other than QHP issuers on the FFEs must send a decision within 72 hours for expedited, urgent requests and within seven calendar days for standard, non-urgent requests. These timeframes apply regardless of whether the decision is communicated by portal, fax, email, mail, phone, or API. When a request is denied, the payer must provide a specific reason for the denial.

CMS-0057 does not apply to employer self-insured plans regulated under ERISA, workers’ compensation carriers, automobile and other casualty insurance, or fully insured commercial group or individual plans sold outside the Federally Facilitated Exchanges. For an ASC, that means cases tied to those payer categories are out of scope of the federal rule, even when the procedure, documentation, and submission steps look identical to a covered case.

CMS-0057 changes the operating environment for ASC authorization teams in three ways. Decisions from impacted payers fall within bounded timeframes, which makes elective scheduling easier to forecast. Denials carry a specific reason, which reduces the time spent reconstructing why a request was rejected. Prior authorization status, documentation requirements, and the list of items and services subject to authorization become available through FHIR APIs that authorization software, EHRs, and practice management systems can consume directly, reducing reliance on phone queues and payer portals over time. State Medicaid programs may impose additional requirements on top of the federal baseline.

Approva treats every prior authorization as a structured case with codes, source documents, and clinical evidence in one record, and tracks each case against the decision timeframes impacted payers must meet. The matrix on this page shows the operational axes — decision turnaround, denial reason, status visibility, packet contents, and payer accountability — and the position Approva occupies today across each. Approva is built to consume CMS-0057 FHIR APIs as payers roll them out, while remaining usable now against payer portals, fax, and phone.