Last reviewed: May 2026
CMS-0057 compliance for ambulatory surgery centers
The CMS Interoperability and Prior Authorization final rule (CMS-0057-F) reshapes how covered payers handle prior authorization, with the core API and decision-timeframe requirements taking effect on January 1, 2027. ASCs are not directly regulated by the rule, but the way orthopedic, spine, and pain management centers submit and track authorizations is about to change. This page summarizes what the rule says, what is verified from primary sources, and what your scheduling and authorization teams should prepare for now.
What is CMS-0057?
CMS-0057-F is the Centers for Medicare and Medicaid Services' final rule titled “Medicare and Medicaid Programs; Patient Protection and Affordable Care Act; Advancing Interoperability and Improving Prior Authorization Processes.” CMS released the rule on January 17, 2024, it was published in the Federal Register on February 8, 2024, and the regulations took effect April 8, 2024. The rule sets new operational and technical requirements for a defined set of payers, with most substantive obligations phased in across 2026 and 2027.
The rule has two interlocking goals. The first is to standardize how patient data, claims history, and prior authorization information flow between payers, providers, and patients using HL7 Fast Healthcare Interoperability Resources (FHIR) application programming interfaces. The second is to compress the time between when a provider submits a prior authorization request and when a payer responds, and to require payers to give a specific reason when a request is denied. Together, these provisions aim to reduce administrative drag on clinical operations and make prior authorization status visible in the systems clinicians already use.
Key dates and requirements
- Final rule released by CMS: January 17, 2024
- Federal Register publication: February 8, 2024
- Effective date of the regulations: April 8, 2024
- Decision timeframe and denial-reason requirements (non-QHP impacted payers): January 1, 2026
- API requirements — Medicare Advantage + state Medicaid/CHIP FFS: January 1, 2027
- API requirements — Medicaid/CHIP managed care: rating period beginning on or after January 1, 2027
- API requirements — QHP issuers on FFEs: plan years beginning on or after January 1, 2027
Decision timeframes
For prior authorization requests on medical items and services, the rule requires impacted payers (excluding QHP issuers on the FFEs) to send decisions within 72 hours for expedited, urgent requests and within seven calendar days for standard, non-urgent requests. These timeframes apply regardless of the channel used to submit or return the decision.
Payer types covered
- Medicare Advantage organizations
- State Medicaid fee-for-service programs
- State Children's Health Insurance Program (CHIP) fee-for-service programs
- Medicaid managed care plans
- CHIP managed care entities
- Qualified Health Plan issuers on the Federally Facilitated Exchanges
Payer types not covered
The rule does not regulate employer self-insured plans governed by ERISA, workers' compensation carriers, automobile and other casualty insurers, or fully insured commercial group or individual plans offered outside the Federally Facilitated Exchanges.
What this means for ASCs
Ambulatory surgery centers submit prior authorizations — they do not run payer adjudication systems — so CMS-0057 reaches you indirectly through the payers you bill. The practical effects on orthopedic, spine, and pain management ASCs cluster around three changes.
Decisions become more predictable in time. Once impacted payers are operating under the 72-hour expedited and seven-calendar-day standard windows, scheduling teams can plan from a defined ceiling rather than an open-ended wait. For elective spine, total joint, and interventional pain cases that already sit in a tight pre-op window, a known outer bound on payer turnaround makes block utilization and surgeon scheduling easier to forecast. Denials carrying a specific reason also reduce the back-and-forth of figuring out what a payer actually objected to before drafting a peer-to-peer or a corrected submission.
Status visibility moves out of phone queues. As payers stand up the Prior Authorization API and Provider Access API on FHIR, status and supporting documentation requirements become readable in standardized formats. In practice, ASCs working with vendors who consume these APIs will spend less time on hold confirming whether a prior auth is pending, approved, or denied, and more time on the cases where clinical documentation needs to be supplemented.
FHIR-based exchange replaces fax and portal-only submission for covered payers. FHIR is a healthcare data exchange standard from HL7 that defines how clinical and administrative information is structured and transmitted over web APIs. Under CMS-0057, impacted payers must publish a Prior Authorization API that returns the list of items and services requiring prior authorization, the documentation needed, and the ability to submit a request and receive a decision. ASCs do not need to build FHIR infrastructure themselves, but their authorization software, EHR, or practice management system needs to be able to consume these APIs as payers roll them out.
Medicaid layers state rules on top of the federal floor. CMS-0057 sets the federal baseline for state Medicaid and CHIP programs and their managed care entities, but individual states may impose additional prior authorization requirements, documentation rules, or earlier internal deadlines. Multi-state ASC operators should map state-specific Medicaid policy alongside the federal rule rather than treating CMS-0057 as the only source of obligation.
How Approva helps
- Approva treats every authorization as a structured case with source documents, codes, and clinical evidence in one place, so the artifact you submit to a payer matches the documentation the payer will ultimately request.
- Approva's workflow positions ASCs to integrate with payer FHIR APIs as they go live in 2027, without forcing your team to wait for that transition to fix today's authorization queue.
- Status tracking, escalation rules, and human reviewer assignments are designed for the new decision timeframes, so urgent and standard cases are routed against the right clock from intake.
- Denial reasons returned by payers are captured against the original case, making appeals, peer-to-peer prep, and trend analysis a normal part of the workflow rather than a separate spreadsheet exercise.
Frequently asked questions
What is CMS-0057?
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.
When does CMS-0057 take effect?
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.
Which payers must comply with CMS-0057?
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.
Are ambulatory surgery centers directly regulated by CMS-0057?
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.
What are the prior authorization decision timeframe requirements under CMS-0057?
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.
Does CMS-0057 apply to commercial insurance or workers’ compensation?
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.
How does CMS-0057 affect prior authorization workflows for ASCs?
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.
How does Approva help ASCs navigate CMS-0057?
Approva structures every prior authorization as a case with codes, source documents, and clinical evidence in one record, and tracks each case against the decision timeframes that impacted payers must meet. The workflow is built to integrate with payer FHIR APIs as they roll out under CMS-0057, while remaining usable today against payer portals, fax, and phone. Specific denial reasons returned by payers are captured against the original case for appeals and peer-to-peer preparation, and human reviewers are named on the case record so confidence in any automated assistance is always tied back to an accountable person.
If your orthopedic, spine, or pain management ASC wants its authorization workflow ready for the CMS-0057 timeframes and the FHIR API rollout, request a demo and we will walk through your current process and where Approva fits.
Request a demoThis content is for informational purposes only and does not constitute legal or regulatory advice. Consult your compliance counsel for authoritative guidance on your specific obligations.
Sources
- CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) overview — CMS landing page with summary, applicability, and compliance dates.
- CMS press release: CMS Finalizes Rule to Expand Access to Health Information and Improve the Prior Authorization Process — January 17, 2024, confirming release of CMS-0057-F, decision timeframes, and impacted payer categories.
- CMS-0057-F fact sheet (PDF) — Official fact sheet detailing the four APIs, decision timeframes, and 2026/2027 compliance dates.
- Federal Register: Advancing Interoperability and Improving Prior Authorization Processes — Federal Register publication, February 8, 2024, document 2024-00895, effective April 8, 2024.
- CMS FAQ: Prior Authorization API — Guidance on Prior Authorization API requirements and FHIR implementation.
- CMS FAQ: Payer-to-Payer API — Guidance on Payer-to-Payer API requirements under CMS-0057-F.