Where the Power to Say ‘No’ Gets Installed: From Portals to Clinics
The scandal here isn’t that an algorithm might get a medical call wrong. It’s that “deny” is being treated like a feature you can deploy at scale—without deploying an equally real, equally fast way for the people harmed by that denial to stop it.
Ars Technica reports that the Trump administration launched a Medicare pilot in January that introduces prior authorization—pre-approval—to services that, in traditional Medicare, didn’t require it before, and that the program uses AI and machine learning as part of how approvals and denials happen Ars Technica. In the months after rollout, Ars writes, providers described technical failures, long waits, confusing denials, and patients stuck in pain while decisions lingered. Federal documents obtained by the Electronic Frontier Foundation through litigation—again as relayed by Ars—include provider feedback describing weeks-long delays and an inability to reach a human being.
Those are the reported facts. Here’s my point: this is governance-by-interface.
Prior authorization isn’t new in American healthcare. What’s new—and politically potent—is shifting a “care happens unless a human stops it” system into “care doesn’t happen unless you clear the gate,” and then making the gate feel procedural, neutral, and therefore unarguable. You don’t debate it as policy. You experience it as a workflow.
The WISeR model (Wasteful and Inappropriate Service Reduction) is explicitly framed as protecting taxpayers by reducing fraud, waste, and abuse, and it has been rolled out in six states with plans to run through 2031, according to the documents described by Ars Technica. It currently applies to roughly a dozen services—pain interventions like epidural steroid injections and nerve stimulation are among them—so the kinds of patients most exposed aren’t abstract. They are often people in immediate discomfort, trying to get relief.
But the detail in Ars that should reframe how we think about “AI in healthcare” is the incentive design.
In a Senate hearing, Sen. Patty Murray pressed the administration’s HHS deputy secretary nominee on whether contractors make more money when they deny care; Ars reports CMS planning documents indicate that WISeR participants are compensated through a share of “averted expenditures”—with guidance describing CMS paying vendors 25 percent of a benchmarked cost when a request is denied. Ars also reports the CMS Office of the Actuary warning that participants will have an incentive to deny as many claims as possible.
You can believe—sincerely—that you’re fighting waste and fraud, and still create a machine that is rationally paid to say “no.” In other words: even if the model is “accurate,” the surrounding system is designed to prefer denial, then dare patients and clinicians to fight their way back to yes.
And that fight happens in the most modern and least accountable arena we have: the interface. A denial is not just a decision; it’s a compression. It takes a patient’s messy reality—pain, history, risk tolerance, the physician’s judgment, the calendar—and collapses it into codes, rules, queues, and deadlines. Ars reports WISeR aims for decisions within 72 hours, but providers reported waits stretching to weeks and even months, including at least one request pending after 83 days. When time is part of the clinical outcome, delay is not a neutral inconvenience. Delay is a form of denial that doesn’t have to call itself that.
The vendors’ struggles matter less to me than what they reveal about how fragile this kind of governance is. Ars reports one vendor asked to delay rollout and temporarily “auto-approved” everything to avoid backlogs; another had months of discrepancies tied to misunderstanding Medicare Part A vs. Part B; and one vendor’s weekly report showed more denials than approvals during a period Ars describes. If you’re an elderly patient trying to understand why your care is stalled, none of that reads as “innovation.” It reads as being trapped inside someone else’s half-built system.
We talk about AI like it’s mainly a question of capability: Can the model classify? Can it detect fraud? Can it match rules? In WISeR, the more dangerous question is constitutional: who holds the handle on refusal?
Ars reports providers describing “radio silence” when they sought help, and describes feedback complaining there was no way to get a human on the line. That’s the thing no one should accept as a growing pain. If you cannot reach a responsible human quickly, you do not have a healthcare process—you have a labyrinth.
The program’s defenders, as Ars reports, point to checks: corrective action plans for missed deadlines; quality scoring meant to discourage inappropriate denials; the claim that vendors use established CMS coverage determinations rather than inventing their own rules. But Ars also reports that the payment adjustment for poor quality scores appears relatively modest compared to the core incentive to deny, and that few denials are appealed in similar contexts even though many appeals succeed. That combination—strong incentive to deny, weak incentive to be right, and low appeal throughput—creates a predictable outcome: the system can be “compliant” while patients suffer.
If this is an experiment, then stop asking the public to evaluate it from slogans (“reduce waste”) or vibes (“AI will streamline care”). Publish the scoreboard where the harm lives: time-to-decision, time-to-procedure, denial rates by vendor and service, appeal rates, overturn rates, and the fraction of cases where a patient or clinician reached a human being within a clinically meaningful window.
But I’m more interested in something simpler than dashboards.
Where is the patient’s “no” installed?
Not “you may appeal” in fine print after the fact. Not “resubmit” after weeks. Not a peer-to-peer process that only a clinic with administrative slack can navigate. A real interrupt: a rapid, accountable human override that can stop the machine from turning a delay into damage.
Because once the interface becomes the constitution—once care depends on what the portal accepts and what the workflow allows—rights start to look like queues. And queues are easy to ignore, especially when the people waiting are old, in pain, and out of sight.
No comments yet.