PCOOB Weekly
 |  Vol. 2, Issue 27

When CMS Can See Every Denial

The June 2026 MCPAR prior authorization reporting requirement created the first standardized federal data set on Medicaid MCO denial rates. Most plans built their authorization workflows for a world where that visibility did not exist.

4
MCPAR PA data fields now standardized
7 days
CMS-0057-F standard PA timeliness requirement (Jan 2026)
53
MFCUs under active federal review (CRUSH initiative)
Jun 2026
First MCPAR cycle with plan-level PA data submitted to CMS
01

A new federal visibility layer, not a new reporting form

The first wave of standardized Medicaid prior authorization data is now flowing to CMS. Most health plan leaders have not fully processed what that means.

Beginning with the reporting cycle submitted in June 2026, the Medicaid Managed Care Program Annual Report (MCPAR) requires states to submit plan-level prior authorization data in standardized fields: total number of PA requests, denial rates, approval rates, the percentage of standard requests approved after appeal, and average and median decision timelines. For the first time, CMS holds a comparable data set across every Medicaid managed care organization in every reporting state.

This is not a minor administrative expansion. Prior to this cycle, Medicaid prior authorization data existed at the state level in fragmented forms. Some states collected denial rates. Some did not. Timeliness data was reported in varying formats, on varying cadences, under varying definitions. CMS had no standardized basis for comparison across plans or states.

The MCPAR revision changes that architecture permanently. CMS also told GAO in November 2025 that it was building an internal appeals and grievance dashboard to use this data for oversight, with planned implementation by June 2026 — precisely when the first MCPAR cycle went live. The timing is not coincidental.

“For the first time, CMS holds a comparable data set across every Medicaid managed care organization in every reporting state. Not summaries. Not state-level aggregates. Plan-by-plan numbers.”
12.5%

Medicaid MCO prior authorization denial rate, compared with 5.7% in Medicare Advantage — as documented in a 2023 OIG evaluation

Source: HHS Office of Inspector General — Prior Authorization Denials in Medicaid MCOs

OVERPAYMENT

The OIG baseline that makes the MCPAR data meaningful

12.5%
MCO denial rate
Medicaid MCO overall prior authorization denial rate — more than double the MA rate of 5.7% at the time of the OIG evaluation
89%
Do not appeal
Of Medicaid enrollees who receive an MCO prior authorization denial, 89 percent never file an appeal — leaving most denials unchallenged
~33%
Appeal success rate
Of the 11% who do appeal, only about one-third succeed — compared to an 82% overturn rate in Medicare Advantage

The OIG numbers were drawn from sampled data under inconsistent methodologies. They told a story about the Medicaid MCO population in aggregate. They did not produce plan-by-plan comparisons. The MCPAR data produces exactly that.

When CMS and state Medicaid agencies can see that one plan in a market denies at 8 percent while another denies at 19 percent, the compliance implications are immediate. High denial rates do not by themselves indicate wrongdoing. But they generate questions that plans should already be able to answer clearly and quickly.

The 7-day timeliness standard adds a second dimension. CMS-0057-F, effective January 2026, requires standard prior authorization decisions within 7 calendar days for plans subject to the rule. The MCPAR now captures average and median decision times.

Plans that have not validated their PA workflow timelines at the process level — not just at the policy level — will see the compliance gap in the data before they see it in a formal inquiry. Queue management, staffing, system routing, and FDR turnaround requirements all affect the actual median timeline. A 7-day policy and a 10-day median workflow are two different things.

The rollup risk most compliance programs have not addressed

Many Medicaid managed care organizations delegate prior authorization functions to specialty vendors, behavioral health managed care organizations, or pharmacy benefit managers. The arrangement is common and operationally rational. The compliance implication of MCPAR, however, runs in a direction most FDR oversight programs have not yet mapped.

The MCPAR submission is a plan-level report. States submit data on behalf of each plan they contract with, drawing from data the plan provides. If FDR-delegated PA data does not flow accurately into the state-submitted MCPAR data — because the FDR uses a different system, because the data pipeline was never formally designed, or because no one validated that the FDR’s PA volume was counted in the plan’s total — the plan’s submitted numbers may undercount total PA volume, misstate denial rates, or omit entire categories of PA decisions.

When CMS or a state oversight team reviews the MCPAR data, the plan’s submission is the record. The vendor’s system architecture is not a mitigating explanation after the fact. The accountability flows to the plan.

Behavioral health is where this risk concentrates. The June 2026 MCPAR cycle arrives shortly after the April 30, 2026 UM Annual Data Submission, which for Medicare Advantage plans required disclosure of internal coverage criteria — including FDR criteria. The OIG previously found that one in five behavioral health prior authorization requests in a reviewed MA sample was denied or modified. Plans that operate under behavioral health carve-outs should verify explicitly whether their MBHO’s PA decisions are captured in the MCPAR PA count.

Key exposure
MCPAR is a plan-level submission. FDR data quality problems produce plan-level reporting problems. CMS sees the plan number, not the vendor’s system architecture.
Behavioral health risk
Plans with behavioral health carve-outs to MBHOs must verify whether MBHO PA decisions are included in the MCPAR submission. Omission understates total denial volume.
FDR oversight gap
Most FDR oversight programs monitor clinical quality and contractual compliance. MCPAR data accuracy — including PA rollup from FDRs — is a new monitoring criterion that most programs have not yet built for.
Timeline
The next MCPAR cycle recurs annually. Plans that identify FDR rollup gaps now have a defined window to correct them before the next submission.
“The MCPAR data lands inside a federal oversight environment that is not passive. The data is actionable — not just informational.”

The MCPAR prior authorization data does not exist in a neutral oversight environment. CMS is running the CRUSH initiative — Comprehensive Regulations to Uncover Suspicious Healthcare — with enforcement actions that include the largest Medicaid funding deferral in agency history ($1.3 billion from California), letters to all 50 state Medicaid programs on program integrity, and a formal review of every Medicaid Fraud Control Unit before its next annual recertification.

In June 2026, HHS denied Hawaii’s MFCU annual recertification — discontinuing federal funding — citing zero fraud convictions from 2022 through 2025. The decertification is the first concrete enforcement action under the MFCU review process, and a clear signal that federal oversight of the Medicaid program integrity infrastructure is active and consequences are real.

For MCOs, this context matters because the states they contract with are under their own pressure to demonstrate program integrity rigor. A state facing CMS scrutiny over Medicaid spending has every incentive to surface MCO compliance gaps rather than absorb them. The MCPAR PA data gives states a direct tool for doing exactly that.

November 2025
CMS tells GAO it is building an internal appeals and grievance dashboard for oversight, planned for June 2026
January 2026
CMS-0057-F 7-day standard PA timeliness requirement takes effect for covered payers
May 2026
CMS announces MFCU review of all 53 state/territory Medicaid Fraud Control Units before next recertification
June 4, 2026
HHS denies Hawaii MFCU recertification; first enforcement action under expanded MFCU review process
June 2026
First MCPAR cycle with plan-level PA data requirements goes live; states submit standardized denial rates, appeal rates, and timeliness data
08
What this demands from leadership

The compliance gap is visible before anyone asks about it

Most Medicaid MCO compliance programs track prior authorization denial rates for clinical quality review purposes. They track appeal rates for member access monitoring. What most leadership teams do not have is a cross-functional view of what their plan-level denial rate looks like relative to MCPAR methodology, what their approval-after-appeal rate suggests about initial denial defensibility, and what a federal comparative data analysis of their market would reveal.

The MCPAR data makes that comparison possible — for CMS, for state Medicaid agencies, and eventually for OIG. Plans that have not already conducted that analysis internally are behind.

The compliance program cannot own this question alone. A plan-level denial rate that sits above market peers implicates clinical policy (are criteria defensible?), operations (is volume being counted correctly?), technology (does the data pipeline capture all PA requests?), and FDR oversight (is delegated PA volume included?). This is a cross-functional governance question, not a reporting one.

Oversight capacity tends to find what plans have not already found themselves. The MCPAR data is now flowing. The CMS dashboard is now operational. The MFCU review process is now active. Plans that wait for enforcement to surface their PA governance gaps are making a governance decision — even if it does not feel like one.

Until next week, stay briefed.

Why this matters

Five cross-functional implications for health plan leadership

📊
Compliance
Denial rates and appeal rates are now observable by CMS and states at the plan level. Plans with outlier patterns will be visible before they receive a formal inquiry.
⚙️
Operations
The 7-day timeliness standard under CMS-0057-F is now captured in MCPAR median data. A policy standard and an actual workflow are two different things — only one shows up in the data.
🔗
FDR oversight
MCPAR is a plan-level submission. Delegated PA volume from BH vendors, specialty carve-outs, and PBMs must roll up accurately. FDR data quality problems become plan-level reporting problems.
💻
Technology
Data pipelines that were built for internal quality review were not necessarily built to capture total PA volume across all FDR systems to MCPAR specifications. Infrastructure validation is needed.
💰
Finance
Enforcement exposure from PA governance gaps — triggered by comparative MCPAR data — carries financial risk beyond the compliance program. Cross-functional awareness at the finance level is appropriate now, not after a finding.
🏛️
Program integrity
CMS’s CRUSH initiative and MFCU review process create a federal oversight posture where MCPAR data is actionable — states under pressure have every incentive to surface MCO compliance gaps rather than absorb them.
Questions

Eight questions plan leadership should ask now

Q1
What is our plan-level PA denial rate, calculated using MCPAR methodology, and how does it compare to prior years?
Q2
What is our approval-after-appeal rate, and what does it reveal about the clinical defensibility of our initial denial distribution?
Q3
Is all PA volume from FDR-delegated functions — BH vendors, specialty carve-outs, PBMs — captured and included in our MCPAR submission?
Q4
Are our PA decision timelines validated at the workflow level against the 7-calendar-day CMS-0057-F standard, not just at the policy level?
Q5
Did our compliance program review the accuracy of this year’s MCPAR PA submission before it was filed by the state on our behalf?
Q6
Do we have a peer benchmarking view of PA denial rates in our markets, and is our leadership team aware of where we stand relative to peers?
Q7
What is our response plan if CMS, a state Medicaid agency, or OIG issues an inquiry based on MCPAR denial rate comparisons?
Q8
Has our FDR oversight program been updated to include MCPAR data accuracy — including PA rollup from all delegated vendors — as an explicit monitoring criterion?
Frequently Asked Questions

Common questions about this edition

What is the MCPAR prior authorization reporting requirement?

Beginning with the reporting cycle submitted in June 2026, the Medicaid Managed Care Program Annual Report (MCPAR) requires states to submit plan-level prior authorization data in standardized fields, including total PA requests, denial and approval rates, appeal-approval rates, and decision timelines. This is the first time CMS has held comparable, plan-by-plan prior authorization data across every Medicaid managed care organization in every reporting state.

What was the Medicaid MCO prior authorization denial rate before MCPAR standardization?

A 2023 OIG evaluation found Medicaid MCOs had an overall prior authorization denial rate of 12.5 percent, compared with 5.7 percent for Medicare Advantage at the time. Of denied Medicaid enrollees, 89 percent did not appeal, and only about one-third of those who did appeal succeeded, compared with an 82 percent overturn rate in Medicare Advantage.

What is the 7-day prior authorization timeliness standard?

CMS-0057-F, effective January 2026, requires standard prior authorization decisions within 7 calendar days for plans subject to the rule. The MCPAR now captures average and median decision times, so plans that have not validated their actual workflow timelines against this standard will see the gap in the federal data before they see it in a CMS inquiry.

Why does FDR-delegated prior authorization data create compliance risk under MCPAR?

Many Medicaid MCOs delegate prior authorization functions to specialty vendors, behavioral health MCOs, or pharmacy benefit managers. Because the MCPAR submission is a plan-level report, any gap in how delegated PA data flows into that submission can undercount total PA volume or misstate denial rates. The plan’s submission is the record CMS reviews, regardless of the vendor’s own system architecture.

Namrata Giri
Independent payer intelligence & strategy analyst

PCOOB Weekly is an independent newsletter covering payer compliance, governance, risk, and operations for U.S. health plan leaders. Every edition is built from primary federal and regulatory sources, written to inform, not to sell.

Connect on LinkedIn

Discover more from PCOOB Weekly

Subscribe now to keep reading and get access to the full archive.

Continue reading