The Rule Worked. Denials Still Went Up.

Last week I wrote about the six months of runway before electronic prior auth becomes mandatory. This week the data showed up early, and it is not subtle. Denial rates are up 31% year over year. Not projected. Already happened, in the first half of the very rule meant to fix this.

The number nobody put on a slide

CMS-0057-F went live 1 January. Faster decisions, cleaner reason codes, an API on the way. Six months in, denials climbed — not dropped.

That is not the rule failing. That is the rule working exactly as designed, just not for the side that expected relief. Payers automated their “no” faster than providers automated their “yes, and here is the proof.”

Drugs are next, and the comment period just closed

While providers were absorbing that denial spike, CMS quietly closed the public comment window on 15 June on a new proposed rule extending the same electronic prior-auth machinery to prescription drugs — standardised turnaround times, FHIR for the medical benefit, NCPDP for the pharmacy benefit, one-day decisions on urgent drug requests.

Read that timeline again. Non-drug items and services already live. Drugs next in the queue. The scope of this framework is expanding faster than most billing teams are updating their workflows for the part already in effect.

The quiet enforcement layer most practices have not clocked

Six states — New Jersey, Ohio, Oklahoma, Texas, Arizona and Washington — are now running under CMS’s WISeR model, where targeted services require prior auth or the claim gets flagged for pre-payment medical review. That is not a slower “no”. That is a hold on the money before the claim is even adjudicated.

If your practice operates in one of those states and you have not checked whether your top billed services are on the targeted list this quarter, that is not a someday task any more.

What the 31% is actually telling you

A denial rate climbing inside a rule built to speed things up means the bottleneck moved. It did not disappear. It shifted from “how long until we hear back” to “how do we prove medical necessity in a format the payer’s engine will accept the first time.”

Practices treating this as a coding problem are solving last year’s issue. The ones closing the gap right now are doing three things:

• Logging denial reason codes by payer and by service line, every month, not just at year-end
• Rebuilding intake documentation to match what the FHIR-based reviewers actually scan for, not what the old fax cover sheet used to say
• Watching the WISeR states specifically, because pre-payment review changes your cash flow timeline in a way a slower decision never did

None of that requires the January 2027 API to exist yet. All of it determines whether that API becomes a tool or another channel you are losing through.

The 2030 view

The industry keeps talking about this as an interoperability story. It is a documentation story wearing an interoperability rule as a costume.

The API does not decide anything. It just moves whatever you fed it, faster, to a payer system built to find the reason to say no. Six months from now, everyone will have the pipe. The practices ahead will be the ones whose data was clean before anyone asked for it electronically.