CMS reaches its first public prior-authorization metrics deadline
The March 31 reporting milestone creates a new, imperfect public evidence layer for examining payer authorization volume, outcomes, and decision timeframes.
Editorial figure by Prior Auth Monitor. Source context: Centers for Medicare & Medicaid Services.
A new source, not a finished benchmark
Public reporting gives buyers, providers, researchers, and members a stronger starting point than isolated anecdotes. It can reveal authorization volumes, approval and denial patterns, appeal outcomes, and decision timing within the reporting structure CMS established. The first analytical task, however, is normalization rather than ranking.
Plan type, contract, covered population, service mix, and reporting unit can materially change the numbers. Files published by UnitedHealthcare, Humana, Aetna, and Cigna demonstrate that the market now has more first-party data, but they should not be combined without reading the scope and notes attached to each disclosure.
The questions a credible benchmark must answer
Every metric record should identify the legal entity or plan, line of business, measurement year, denominator, excluded requests, urgent versus standard treatment, and whether a determination followed an initial request or an appeal. Averages should not be treated as distributions, and an approval percentage does not establish that the underlying request was clinically appropriate or administratively efficient.
Prior Auth Monitor will preserve payer disclosures as sourced records and label comparability limitations. The objective is to make evidence easier to inspect—not to convert unlike populations into a simplistic score.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Prior Auth Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.