By Jay Chowdappa, MD, co-founder and CEO, Zynix AI · Updated October 27, 2026
Editor’s note: this article was first published on March 31, 2026, the day the first prior authorization metrics were due, and was updated on October 27, 2026. The key takeaways, key dates, FAQ and timeline reflect CMS guidance as of October 27, 2026.
Key takeaways
CMS-0057-F, the CMS Interoperability and Prior Authorization Final Rule, has two sets of dates. Its operational rules began January 1, 2026: decision deadlines, a specific reason for every denial and annual public metrics, first due March 31, 2026. Its FHIR APIs, including the Prior Authorization API, are generally due January 1, 2027, with exact dates varying by payer type.
- The first public reports, covering calendar year 2025, were due by March 31, 2026, and show approval, denial and post-appeal approval rates plus average and median decision times, excluding drugs.
- Since January 2026, most impacted payers must decide expedited requests within 72 hours and standard requests within seven calendar days, and must give a specific reason for each denial.
- Payers must offer FHIR-based Prior Authorization, Provider Access and Payer-to-Payer APIs beginning January 1, 2027, with exact dates varying by payer type.
- CMS's WISeR model separately adds technology-assisted prior authorization for select Original Medicare services in six states, with licensed clinicians reviewing every non-affirmation and a gold card exemption since July 2026.
- Start where high volume meets high denial rates, and let software carry the paperwork while staff own every request.
The Prior Auth Transparency Data Is Now Public
March 31, 2026 marked a quiet inflection point in healthcare. As of that day, every Medicare Advantage organization, Medicaid managed care plan, and Qualified Health Plan issuer on the federal exchange was required to publicly report their prior authorization metrics for calendar year 2025.
That means approval rates, denial rates, average decision turnaround times, and appeals outcomes are now visible to anyone with a browser. For the first time, the prior auth black box is cracked open.
If you run an ACO, MSO, or health system with Medicare exposure, this isn't a regulatory footnote — it's a strategic signal. Here's why.
What Exactly Is Being Reported?
Under the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), impacted payers must publish aggregated prior authorization metrics on their public websites annually. The first reports — covering calendar year 2025 — were due March 31, 2026, and payers must update them every year.
Required metrics include:
- Prior authorization approval and denial rates
- Average decision turnaround times
- Appeals outcomes (approval/denial after appeal)
- Extended review rates
MA organizations report at the contract level. State Medicaid and CHIP programs report at the state level. Managed care plans report at the plan level.
One notable exclusion: drugs are carved out. Only medical items and services fall under this mandate.
CMS-0057-F key dates
CMS-0057-F splits into operational rules that started on January 1, 2026 and API requirements that generally start on January 1, 2027. CMS says the exact API compliance dates vary by payer type. These are the dates as CMS states them:
| Date | What CMS requires | Who it applies to |
|---|---|---|
| January 17, 2024 | CMS releases the Interoperability and Prior Authorization final rule (CMS-0057-F) | Medicare Advantage 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 |
| January 1, 2026 | Prior authorization decisions within 72 hours for expedited requests and 7 calendar days for standard requests | Impacted payers other than QHP issuers on the federally facilitated exchanges |
| January 1, 2026 | A specific reason for every denied prior authorization, however the request was sent; annual Patient Access API usage metrics reported to CMS | All impacted payers |
| March 31, 2026 | First public prior authorization metrics posted on the payer’s website, covering the previous calendar year; then annually | All impacted payers |
| January 1, 2027 (generally) | Prior Authorization API, Provider Access API and Payer-to-Payer API in place, and prior authorization information added to the Patient Access API | All impacted payers; exact compliance dates vary by payer type |
| CY 2027 performance period | New Electronic Prior Authorization attestation measure (CY 2029 MIPS payment year for clinicians) | MIPS eligible clinicians, eligible hospitals and critical access hospitals |
None of these provisions apply to prior authorization for drugs. For a provider organization, the practical sequence is: use the 2026 metrics to see where friction sits, hold payers to the 2026 decision deadlines, and prepare to send requests electronically when payers’ Prior Authorization APIs go live in 2027.
Why This Matters More Than You Think
On the surface, this is a transparency play. But underneath, it creates three dynamics that directly impact ACO operations:
1. Payer behavior is now benchmarkable
For the first time, you can compare denial rates across payers in your market. If Payer A denies 30% of prior auth requests and Payer B denies 12%, that's not just interesting — it's actionable intelligence for contract negotiations, network decisions, and care routing.
2. Denial patterns become predictable
With public data on which service categories get denied most frequently, your rev cycle and care management teams can build pre-submission denial risk models. You don't need to wait for a denial to react — you can anticipate it.
3. The regulatory momentum is accelerating
This transparency mandate is just the first shoe to drop. By January 2027, impacted payers must implement a FHIR-based Prior Authorization API that accepts and returns structured electronic prior auth requests. The infrastructure burden on payers is about to spike — and the operational ripple effects will hit providers.
The WISeR Wildcard: CMS Is Using AI to Review Your Claims
While everyone is focused on transparency reporting, there's a parallel development that deserves more attention: the Wasteful and Inappropriate Service Reduction (WISeR) Model.
Launched January 1, 2026, WISeR is running in six states — Arizona, New Jersey, Ohio, Oklahoma, Texas, and Washington. It uses AI and machine learning to screen prior authorization requests for select Medicare FFS services.
Here's what makes WISeR significant:
- Functionally mandatory: Claims not submitted for prior auth are automatically routed to prepayment review. So while the model is technically voluntary, skipping it means your claim gets scrutinized anyway.
- AI-first screening: Initial review is algorithmic, with licensed clinicians reviewing all non-payment recommendations. Participants plan to issue prior authorization decisions within 3 calendar days (2 for expedited requests).
- Gold carding since July 2026: CMS and the WISeR participants exempt clinicians with consistent approval histories — essentially rewarding clean submitters by skipping review for at least a year.
The six WISeR participants include Cohere Health, Innovaccer, Humata Health, Genzeon, Virtix Health, and Zyter. If you're an ACO in one of those six states, your claims are already being screened by AI. The question is whether your submission workflows are optimized for that reality.
What ACOs Should Do Before 2027
The organizations that will benefit from this regulatory shift are the ones that treat it as an operational opportunity, not a compliance checkbox. Here's the playbook:
1. Mine the new transparency data
Pull the public prior auth reports from every payer in your network. Build a denial rate dashboard by payer and service category. Use it to prioritize which workflows to automate first — start with the highest-denial, highest-volume service lines.
2. Automate pre-submission denial risk scoring
If many physicians believe AI is increasing payer denials (per the latest AMA survey), the answer isn't to fight AI with paper — it's to fight AI with better AI. Pre-submission risk models that flag high-denial-probability requests before they're sent give your team time to strengthen documentation, attach supporting evidence, or reroute the request.
3. Build for the January 2027 FHIR API mandate
The Prior Authorization API requirement generally takes effect January 1, 2027, with exact compliance dates varying by payer type. Payers will be required to accept electronic prior auth requests via FHIR APIs. ACOs that integrate their EHR and care management workflows with these APIs early will see faster approvals, fewer manual touches, and lower administrative burden.
4. If you're in a WISeR state, optimize now
Your claims are being AI-screened today. Clean clinical documentation, accurate coding, and complete submissions aren't best practices anymore — they're requirements for getting paid on time. Ambient documentation tools like ZynScribe, which draft visit notes for the physician to review and approve, help make documentation complete at the point of care and are no longer optional.
The Bigger Picture: Prior Auth Is a Proxy for the AI Execution Gap
Here's what most analysis of the transparency rule misses: prior authorization is a symptom, not the disease.
The real problem is that most ACOs still run care management, documentation, and revenue cycle workflows on manual processes augmented by dashboards. They can see the problem — they just can't execute the fix at scale.
At Zynix AI, we built the Zynix platform specifically for this execution gap. On prior authorization, we don't just flag risks — we take on the paperwork: pulling the right clinical documentation into the request, tracking the submission, and routing the payer's response to the right person, while your staff own every request. The goal is to move care management and revenue cycle teams from reacting to denials toward submitting complete requests the first time.
The transparency rule makes the problem visible. AI agents make it solvable.
What Comes Next
The prior auth landscape is moving faster than most ACO leaders realize:
- March 31, 2026: Payers had to publish PA metrics publicly, and must update them every year
- July 2026: WISeR exemption (gold carding) program began
- January 1, 2027 (generally): FHIR-based Prior Authorization API mandate takes effect, alongside the Provider Access and Payer-to-Payer APIs; exact dates vary by payer type
- CY 2027: clinicians and hospitals begin attesting to the new Electronic Prior Authorization measure
- 2027–2031: WISeR continues through December 31, 2031; the LEAD model launches January 1, 2027 with 10-year ACO commitments
The ACOs that automate prior auth workflows now won't just reduce denials — they'll build a structural operational advantage that compounds over the next five years.
The data is public. The AI is already screening your claims. The question is whether your workflows are ready.
Frequently asked questions
What prior authorization metrics must payers publish under CMS-0057-F?
Impacted payers must post a list of medical items and services that need prior authorization, excluding drugs, and, for standard and expedited requests, the percentage approved, denied and approved after appeal, plus average and median decision times. They also report how often an extended review ended in approval. Medicare Advantage organizations report by contract, state Medicaid and CHIP fee-for-service programs by state, managed care plans by plan and federal exchange issuers by issuer.
What are the key CMS-0057-F dates?
CMS finalized the rule on January 17, 2024. Operational rules began January 1, 2026: payers other than federal exchange plans must decide expedited requests within 72 hours and standard requests within 7 calendar days, and every payer must give a specific denial reason. Public prior authorization metrics were first due March 31, 2026, then yearly. The Prior Authorization, Provider Access and Payer-to-Payer APIs are generally due January 1, 2027, with dates varying by payer type.
How can an ACO use payer prior authorization data?
Compare payers on denial rates, approvals after appeal and decision times for the services your attributed patients use most. Rank service lines by volume and denial rate to choose where to fix documentation or automate paperwork first, and bring the comparisons into payer contract and network discussions. Prior authorization competes for the same staff time as an ACO's TCM, wellness visit and gap closure work, so track the metrics each year.
Does the WISeR model affect ACO patients?
It can. WISeR applies to providers in Arizona, New Jersey, Ohio, Oklahoma, Texas and Washington who furnish selected services, such as skin and tissue substitutes or electrical nerve stimulator implants, to Original Medicare patients, and Shared Savings Program ACOs serve Original Medicare patients. It does not apply to Medicare Advantage. Providers choose prior authorization or pre-payment review, and since July 2026 consistently affirmed clinicians can earn an exemption.
How can AI automate prior authorization under CMS-0057-F, and what should staff keep?
Automate the paperwork: assembling documentation against each payer's requirements, which payers' Prior Authorization APIs must expose from 2027, tracking each request against its decision deadline and routing payer responses to the right person. Keep people in charge of each request and of appeal decisions, and leave peer-to-peer conversations to clinicians. Zynix works this way, handling paperwork assembly, submission tracking and routing of payer responses through connections to the EHRs your practices already run, while your staff own every request.
Related reading
- CMS WISeR Is Live in 6 States: What the AI Prior Auth Pilot Means for Your Revenue Cycle — and How to Reach Gold Card Status
- Prior Authorization Delays: What They Actually Cost And How to Fix Them
- How ACOs Actually Make Money: Shared Savings Mechanics and Where AI Moves the Needle
Source notes
CMS: CMS Interoperability and Prior Authorization Final Rule CMS-0057-F (fact sheet). https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-prior-authorization-final-rule-cms-0057-f
CMS: Prior Authorization Metrics Reporting, Overview and Template (PDF). https://www.cms.gov/prior-authorization-metrics-reporting-overview-template
CMS: WISeR (Wasteful and Inappropriate Service Reduction) Model. https://www.cms.gov/priorities/innovation/innovation-models/wiser
American Medical Association: AMA prior authorization physician survey (2025 edition, PDF). https://www.ama-assn.org/system/files/prior-authorization-survey.pdf
CMS: LEAD Model. https://www.cms.gov/priorities/innovation/innovation-models/lead
CMS: WISeR Model Provider and Supplier Operational Guide, version 7.0 (July 24, 2026). https://www.cms.gov/priorities/innovation/files/wiser-provider-supplier-guide.pdf
CMS: 2024 CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), rule overview page. https://www.cms.gov/priorities/burden-reduction/overview/interoperability/policies-regulations/cms-interoperability-prior-authorization-final-rule-cms-0057-f
About the author
Jay Chowdappa, MD is co-founder and CEO of Zynix AI. He is a physician, and ACOs led by him generated $300M+ in shared savings before he started Zynix AI to help care teams follow through on what their data already shows.