Clinical Terminal
Opinion

Your denials AI is real. CMS just can't see it.

Every denials startup leads with the same number: denial rate. It is the right number to manage, and it is also a number that is not in public CMS hospital data. Hospitals do not report denial rates to CMS, so no public dataset will confirm a claim like "we cut denials 30%."

By Jordan Leahy Nov 9, 2026

Your denials AI is real. CMS just can't see it.

Clinical Terminal mapped every capability in the denials management market against the CMS measures hospitals actually report, using a draft capability map of 1,071 healthcare capabilities and stored CMS hospital data. The result is plain: of the ten denials capabilities, none has a strong link to a CMS number, seven have a weak one and two have none at all.

The one public number denials work reaches is net days in accounts receivable, and it reaches it weakly. Six capabilities connect to it: pre-submission denial prediction, denial capture and categorization, automated correction and resubmission, appeal evidence retrieval, appeal letter generation and appeal tracking. In every case the link is a proxy, not a direct one. Fewer denials and faster rework mean faster payment, which shortens A/R. But A/R also moves with payer mix, billing staff, coding lag and a dozen other things, so a denials tool's effect is diluted, and any change takes one to two years to show up in cost reports.

Clinical appeals work differently. Winning DRG-downgrade and level-of-care appeals protects the documented acuity a hospital was paid for. It does not raise it, and the effect on CMS's case mix numbers is faint.

Two capabilities have no CMS outcome at all. Denial letter intake saves labour, and root-cause analytics produces insight; neither changes a reported number by itself.

That shapes what buyers will ask for. A CFO will not find proof of a denials product in CMS data. They will ask for the vendor's numbers, measured at their hospital: the initial denial rate before and after, first-pass yield, the overturn rate on appeals, days to resolve a denial, and cash collected that would otherwise have been written off. If a product cannot produce those cleanly from the customer's own data, the pitch has nothing underneath it.

CMS-visible results do exist in the revenue cycle, just not in denials. Five capabilities have a strong link to days in A/R: payer A/R follow-up, unbilled (DNFB) management, legacy and backlog A/R cleanup, legacy A/R wind-down and full-service RCM outsourcing. That is context, not a claim about any product. For a founder who wants a result a hospital can eventually see in its own cost report, that is where denials work connects to it.

The takeaway for founders is threefold. Sell the operational metric you can prove: denial rate, overturns and cash recovered. Use days in A/R as the CFO's frame, but call it what it is: a proxy, one to two years out. And build the measurement into the product, because in this market the vendor's own data is the evidence.

This analysis comes from draft research mapping 1,071 healthcare capabilities to stored CMS hospital measures, and the map is still being reviewed. Days in A/R here means net A/R days, calculated from each hospital's Medicare cost report: accounts receivable less the allowance for uncollectibles, divided by net patient revenue per day.