Prepare your data, case files and oversight for 2027 program audits.

Download Whitepaper Download Whitepaper

CMS-0057-F: 2027 Prior Authorization and Interoperability Requirements for Health Plans

Inovaare_CMS-0057-F Final Rule: How Health Plans Can Prepare for Prior Authorization Reform

The clock is running on CMS-0057-F, and for health plans, 2027 is no longer a distant compliance milestone. With the rule’s operational requirements already in effect since 2026 and major interoperability and API compliance deadlines approaching in 2027, the focus has shifted from understanding the regulation to demonstrating readiness. For Medicare Advantage organizations, Medicaid and CHIP programs, and impacted Marketplace health plans, this means more than deploying FHIR APIs. It means connecting prior authorization workflows, clinical data, decision processes, and reporting systems so information moves accurately, securely, and consistently across the care ecosystem. The real question for health plan leaders is no longer “What does CMS-0057-F require?” but “Can our systems, processes, and data withstand the operational and compliance demands of 2027?”

What is CMS-0057-F

CMS-0057-F requires defined payer categories to improve non-drug prior authorization processes and exchange specified health information through FHIR-based APIs. Operational requirements generally took effect in 2026, while major API deadlines begin in 2027 on payer-specific schedules. As 2026 closes in, the most practical leadership question is whether 2026 process and public-reporting evidence can be demonstrated, and whether the 2027 APIs are ready for secure, tested production operation. CMS-0062-P proposes additional drug prior authorization and interoperability requirements; certain ONC health IT standards from that proposal were separately finalized in August 2026.

“CMS-0057-F is not just an API implementation deadline. It is a test of how well health plans can connect their data, systems, and operational processes to support timely decisions, transparency, and accountability. The priority should be building a flexible, interoperable technology foundation that supports compliance today while remaining adaptable to tomorrow’s regulatory requirements.”

Brenda Wade
Chief Compliance Officer, Inovaare

CMS-0057-F deadlines at a glance

CMS-0057-F deadlines at a glance
RequirementCompliance timingWhat payers must verify
Prior authorization decisions and denial reasons2026 operational deadlines: January 1, 2026 for MA and Medicaid/CHIP FFS; relevant rating periods starting on or after January 1, 2026 for Medicaid/CHIP managed care; FFE QHP denial reasons from applicable 2026 plan years.Non-drug decision clocks and specific denial notices; the new 72-hour/7-day clocks do not apply to FFE QHP issuers under CMS-0057-F.
Public prior authorization metricsFirst public posting by March 31, 2026 for CY 2025; annually by March 31 for the prior year.Publish non-drug metrics on the correct website and reporting unit (MA contract, FFS state, managed care plan, FFE QHP issuer).
Patient Access API usage metricsFirst CY 2025 data reported in 2026, generally by March 31, 2026; Medicaid managed care data may follow state MCPAR submission pathways.Report both unique patients with app transfers and unique patients whose data transferred more than once; reconcile state reporting instructions.
Expanded Patient Access APIJanuary 1, 2027 (MA and Medicaid/CHIP FFS); relevant 2027 rating periods (Medicaid/CHIP managed care); relevant 2027 plan years (individual-market FFE QHP issuers).Add required non-drug PA information; update information within one business day of receipt or status change and observe applicable availability windows.
Provider Access APISame payer-specific 2027 API schedule.Confirm provider attribution/treatment relationship, patient opt-out, lawful exchange, response timeliness, and USCDI/claims/PA data scope.
Payer-to-Payer APISame payer-specific 2027 API schedule.Patient opt-in and attestation; former and concurrent payer workflows, five-year lookback, and exclusion of denied prior authorizations from required PA exchange.
Prior Authorization APISame payer-specific 2027 API schedule.Non-drug services, requirements discovery, documentation, requests and responses. The API does not mandate real-time adjudication.

For these 2027 API policies, Medicare Advantage organizations and state Medicaid/CHIP fee-for-service (FFS) programs generally must comply by January 1, 2027. Medicaid managed care plans and CHIP managed care entities must comply for rating periods beginning on or after January 1, 2027. Individual-market qualified health plan (QHP) issuers on Federally-facilitated Exchanges (FFEs) must comply for plan years beginning on or after January 1, 2027. These distinctions are material: a rating-period start date is not necessarily January 1.

Who is subject to CMS-0057-F?

The rule covers Medicare Advantage organizations; state Medicaid and CHIP fee-for-service programs; Medicaid managed care plans; CHIP managed care entities; and individual-market qualified health plan issuers on the Federally-facilitated Exchanges. It does not automatically cover every off-Exchange commercial plan or every employer product. Adding small-group FF-SHOP issuers to impacted-payer scope is proposed in CMS-0062-P; do not present that expansion as finalized.

What changed in 2026? Operational prior authorization obligations

  • Faster Prior Authorization Decisions:
    For covered non-drug medical items and services, applicable payers must issue decisions as expeditiously as the patient’s condition requires, generally within 7 calendar days for standard requests and 72 hours for expedited requests.
  • Payer-Specific Effective Dates:
    Medicare Advantage organizations and state Medicaid/CHIP fee-for-service programs generally became subject to the new requirements on January 1, 2026. Medicaid and CHIP managed care entities must comply for rating periods beginning on or after that date. The shortened decision timeframes do not apply to FFE QHP issuers under CMS-0057-F.
  • Clear Decision Clock Rules:
    The clock starts when the payer receives an actual prior authorization request, regardless of the submission channel. Preliminary coverage inquiries do not trigger the clock, and timelines are measured in calendar time, not business days.
  • Limited Extensions, Not Automatic Pauses:
    Certain programs permit extensions, generally up to 14 additional calendar days, under specified conditions. Requesting missing documentation does not automatically pause, reset, or extend the decision deadline.
  • Specific Reasons for Denial:
    Impacted payers must provide a specific reason when denying a covered non-drug prior authorization request, regardless of how the request was submitted. This requirement also applies to individual-market FFE QHP issuers for applicable 2026 plan years, even though their decision timeframes were not shortened.
What this means for health plans

Compliance requires more than faster reviews. Payers need reliable request tracking, deadline monitoring, consistent denial documentation, and auditable workflows across submission channels. These operational capabilities also provide a foundation for the interoperability requirements taking effect in 2027.

What must health plans publish about prior authorization?

Under CMS-0057-F, prior authorization performance is no longer solely an internal operational measure. Beginning in 2026, impacted payers must publicly disclose specified prior authorization metrics on their websites, making approval rates, denial rates, appeals outcomes, and decision timelines more transparent to members, providers, and other stakeholders.

Key public reporting requirements include:

  • Annual Reporting Deadline: Impacted payers must publish prior authorization metrics by March 31 each year, covering the previous calendar year. The first publication was due March 31, 2026, using 2025 data. The next reporting deadline is March 31, 2027, covering 2026 performance.
  • Prior Authorization Requirements: Publish a list of medical items and services that require prior authorization. Drug prior authorizations are excluded from these CMS-0057-F reporting requirements.
  • Approval and Denial Rates: Report the percentage of standard and expedited prior authorization requests approved and denied, aggregated across applicable medical items and services.
  • Appeals and Overturned Denials: Disclose the percentage of standard prior authorization requests approved after appeal, providing visibility into decisions that were initially denied but subsequently overturned. CMS requires applicable appeals outcomes to be reflected in the overall approval and denial metrics.
  • Extensions and Approval Outcomes: Report the percentage of prior authorization requests for which the review timeframe was extended and the request was subsequently approved.
  • Decision Turnaround Times: Publish the average and median time between request submission and determination, separately for standard and expedited prior authorizations. These metrics provide insight into actual processing performance.
  • Payer-Specific Reporting Levels: Medicare Advantage organizations report at the contract level; state Medicaid and CHIP fee-for-service programs at the state level; Medicaid and CHIP managed care entities at the plan level; and federally facilitated Exchange QHP issuers at the issuer level.
What this means for health plans

Public reporting creates a new level of visibility into prior authorization performance. Health plans need consistent data capture, reliable metric calculations, accurate appeals reconciliation, and auditable reporting processes. Beyond meeting disclosure requirements, these metrics can help identify operational bottlenecks, improve decision consistency, and support continuous performance improvement.

The bigger implication

Prior authorization performance is becoming publicly measurable. For payer executives, the challenge is not simply publishing compliant metrics, but understanding what those metrics reveal about operational effectiveness and where improvements are needed.

Note: CMS-0057-F does not require public reporting of total request volumes or individual denial reasons as standalone metrics. Those should not be added to the mandatory disclosure list. The reporting requirements above reflect the final rule, not proposed changes in CMS-0062-P. Sources: CMS Prior Authorization FAQs and 42 CFR § 422.122(c)

Four API requirements for 2027

CMS-0057-F introduces four critical interoperability requirements that change how health plans exchange prior authorization, clinical, and administrative data. Beginning in 2027, impacted payers must implement or enhance the Patient Access API, Provider Access API, Payer-to-Payer API, and Prior Authorization API, according to payer-specific compliance dates. Each serves a distinct purpose, but together they require connected data systems, standardized FHIR-based exchange, appropriate security and consent controls, and reliable operational workflows. For health plans, the challenge is not simply making these APIs available. It is ensuring they work across existing systems, support accurate data exchange, and meet the rule’s technical and operational requirements.

Explore the four API requirements, their compliance deadlines, key implementation considerations, and the readiness checkpoints health plans should address before enforcement.

2027 readiness: What payer executives should test now

  • Validate scope by line of business and legal entity. Map MA, Medicaid FFS, CHIP FFS, managed care rating periods and FFE QHP plan years individually.
  • Reconcile 2025 baseline metrics and 2026 public reporting. Verify posted values, denominator definitions, appeal treatment and documented corrections.
  • Test the full prior authorization clock from request receipt to decision notification, including weekends, additional-information requests, permitted extensions and delegated cases.
  • Run API contract tests with provider and payer partners. Verify FHIR implementation, access control, member consent or opt-out as applicable, audit logs, data quality and error handling.
  • Map prior authorization records to source systems. Confirm clinical documentation, authorization status, denial reasons, dates and covered services can be retrieved accurately.
  • Assess delegated entities and technology vendors. Assign evidence owners, validate service commitments and build exception escalation routes.
  • Prepare evidence for audits and operational oversight: access logs, decision histories, reporting calculations, testing results, issues and remediation records.

What about CMS-0062-P and drug prior authorizations?

While CMS-0057-F focuses on prior authorization for non-drug medical items and services, CMS is proposing to extend many of these interoperability and operational requirements to prescription drugs through CMS-0062-P, the Interoperability Standards and Prior Authorization for Drugs Proposed Rule, released on April 10, 2026.

The proposal signals a potential expansion of electronic prior authorization requirements, bringing medical and pharmacy authorization processes into a more connected, standardized framework.

Key proposed changes include:

  • Electronic Prior Authorization for Drugs: Extend electronic prior authorization capabilities to drugs covered under the medical benefit, using FHIR-based APIs. CMS proposes an October 1, 2027 implementation date.
  • Pharmacy Benefit Interoperability: Require applicable Medicaid, CHIP, and federally facilitated Exchange payers to support specified National Council for Prescription Drug Programs (NCPDP) standards, including SCRIPT, Formulary & Benefit, and Real-Time Prescription Benefit, beginning October 1, 2027.
  • Faster Drug Authorization Decisions: Introduce or align drug prior authorization decision timeframes across applicable payer programs, subject to program-specific rules and exceptions.
  • Expanded Payer Applicability: Bring small-group Qualified Health Plan issuers on the Federally-facilitated Small Business Health Options Program (FF-SHOP) into the scope of specified interoperability requirements.
  • Enhanced API Standards and Transparency: Propose additional requirements for interoperability API implementation, technical documentation, endpoint reporting, usage metrics, and standardized data exchange.
  • FHIR-Based Administrative Transactions: Propose adopting FHIR standards and implementation guides for certain HIPAA prior authorization-related transactions, including supporting clinical documentation.
Important Regulatory Distinction

As of November 2026, CMS-0062-P remains a proposed rule. Its proposed requirements and implementation dates are not yet binding. However, HHS finalized certain updated health IT standards originally proposed under CMS-0062-P through the FY 2027 Inpatient Prospective Payment System final rule (CMS-1849-F), effective October 1, 2026. That standards adoption does not mean the broader drug prior authorization proposals have been finalized.

The bigger implication

CMS-0057-F establishes the current interoperability baseline. CMS-0062-P signals where federal prior authorization policy may move next. Health plans that design for adaptability, rather than a single compliance deadline, will be better positioned to respond as these requirements evolve.

What this means for health plans

Payers should prioritize compliance with the finalized CMS-0057-F requirements while assessing how their existing architecture could accommodate future drug prior authorization obligations. An API-first, configurable technology foundation can help reduce the need for separate medical and pharmacy authorization infrastructures, support evolving interoperability standards, and minimize future integration complexity.

A practical approach to enterprise-wide CMS-0057-F oversight

Compliance leaders need a clear view across utilization management, interoperability, reporting, privacy, delegated operations and audit. A useful operating model links each regulatory requirement to its accountable owner, supporting system, data source, test evidence, exceptions and corrective actions. This is a recommended governance approach rather than a separate CMS-prescribed platform requirement.

An integrated workflow can help health plans see whether decisions meet timeframes, where provider documentation is incomplete, how delegated entities perform and whether public reports reconcile to operational data. Clinical decisions should remain subject to appropriate professional oversight. Automation should surface missing documentation and route work to authorized reviewers, not be described as automatically validating medical necessity.

How Inovaare can support payer readiness

Meeting CMS-0057-F requirements involves more than implementing APIs. Health plans need an underlying technology foundation that connects systems, supports reliable data exchange, adapts to evolving regulatory requirements, and maintains operational visibility and accountability. Inovaare’s healthcare-focused, API-first platform provides a flexible foundation for health plans to strengthen interoperability, streamline operations, and build sustainable compliance processes.

CMS-0057-F is an important milestone, but interoperability and regulatory modernization will continue beyond 2027. Health plans need technology investments that can accommodate changing standards, emerging requirements, and evolving operational needs without repeated system overhauls.

Inovaare’s configurable, integration-ready platform provides a foundation for this adaptability, helping health plans move toward more connected, transparent, and sustainable healthcare operations.

single pillar but in the connections between them. And those connections are precisely where continuous readiness either becomes real — or stays theoretical.


Frequently Asked Questions

Continuous audit readiness means maintaining compliance infrastructure as a permanent operational state rather than a pre-audit preparation mode. Specifically, it means the compliance function always knows where its gaps are, can measure whether they are improving, and can respond to an audit without changing its operating mode. When a CMS letter arrives, the organization is already operating at audit-ready quality.

No. The rule requires a compliant Prior Authorization API and applicable decision timeframes, but does not require that every clinical decision be made in real time.

CMS-0057-F’s new prior authorization process and API mandates address non-drug items and services. This does not eliminate separate existing Part B, Part D, Medicaid or other drug coverage requirements. CMS-0062-P proposes additional drug policies, not a finalized expansion of CMS-0057-F drug obligations. Selected ONC standards from the proposal were finalized separately in August 2026.

No. It applies to the defined impacted payer categories under CMS-0057-F. The rule does not impose it on every commercial product. Public reporting must follow the applicable MA contract, state FFS, managed care plan or individual-market FFE QHP issuer unit.

Yes. CMS-0057-F requires affirmative patient opt-in for payer-to-payer exchange, including previous/concurrent payer scenarios; the Provider Access API instead includes a patient opt-out mechanism.

Sources

How audit-ready is your health plan?

Request a complimentary compliance readiness assessment. Our team will evaluate your audit preparedness, operational efficiency, and compliance infrastructure — and deliver a scored readiness brief within 24 hours.

No PHI or plan data required. HIPAA-compliant process.
Trusted by 40+ health plans · HIPAA Compliant · HITRUST Certified
Scroll to Top