Black Book’s 2027 Categories Split Out Autonomous Coding

·

Black Book’s 2027 Categories Split Out Autonomous Coding

On October 2, 2026, Black Book Research published an expanded category framework for
what it calls the “mid-revenue cycle” — the stretch of the billing workflow between a
patient encounter and a clean claim. The announcement, timed just ahead of AHIMA26
(October 4-6, San Antonio), does something research firms rarely bother with: it stops
treating “coding software” as one product category and splits it into pieces that map
much more closely to how coding and compliance teams actually buy and manage these
tools.

The research draws on Q3 2026 feedback from 1,787 coding, health information
management, clinical documentation integrity, revenue integrity, and revenue-cycle
professionals — a large enough base that the category boundaries are worth taking
seriously, even for teams that ignore vendor rankings on principle.

Four Segments, Nineteen Categories

Rather than one bucket for “RCM software,” Black Book now organizes the market into
four segments, each broken into its own set of categories:

  • Provider Technology (7 categories) — including autonomous
    professional coding, AI-enabled CDI, pre-bill clinical validation, and denial
    prevention as separate lines, not features of a single platform.
  • Payer Operations (4 categories) — covering payment integrity,
    risk adjustment, and data exchange tools used on the payer side of the same claims.
  • Outsourced Operations (5 categories) — managed coding and denial
    recovery services, distinguished from the software vendors in the other segments.
  • Consulting and Governance (3 categories) — transformation work,
    AI governance, and vendor strategy advisory.

Autonomous Coding Gets Its Own Lane

The provider-technology split is the one coding teams should read most closely.
Autonomous professional coding is now tracked separately from AI-enabled CDI and from
pre-bill clinical validation — three functions that marketing copy routinely blends
together under “AI coding platform.” Black Book’s category leaders in this segment
include Dolbey, IKS Health, Microsoft Nuance, Iodine Software, Craneware, CodaMetrix,
Fathom, SmarterDx, AKASA, MDAudit, Waystar, and AGS Health, among more than a dozen
others recognized across the four segments.

Why the Split Matters More Than the Rankings

Black Book founder Doug Brown framed the change simply: AI is changing what a coding
or documentation solution actually does, which means a single leaderboard can no longer
describe the market honestly. For a compliance officer evaluating a vendor, that’s the
useful part — not who ranked first, but which of the 19 categories a given tool is
actually competing in, and whether that matches the gap you’re trying to close.

What This Means for Vendor Evaluation

Procurement conversations in coding departments have tended to compress very
different capabilities into one RFP line: “AI medical coding.” Black Book’s framework
is an argument that this compression hides real differences in liability and workflow
fit. An autonomous coding tool that assigns final codes without human review carries a
different audit-exposure profile than a pre-bill validation tool that flags charts for a
coder to review before submission — even if both vendors describe themselves as “AI
coding” products in a sales deck.

That distinction lines up with how CMS and OIG have been approaching AI-assisted
coding in recent guidance: the question isn’t whether AI touched the chart, but who made
the final coding decision and what evidence trail exists behind it. A category framework
that separates autonomous coding from clinical validation gives compliance teams a
cleaner way to ask vendors exactly where their tool sits — and what level of human
oversight it assumes.

A Practical Way to Read Vendor Rankings

Teams using this or any category framework to shortlist vendors should ask a few
questions before treating a “category leader” badge as due diligence. Start with which
specific category the vendor is actually recognized in — autonomous coding, CDI,
pre-bill validation, or denial prevention — and whether that matches the gap you’re
trying to close, rather than the broader “AI coding” label on the homepage. Then ask
whether the tool makes final coding decisions or surfaces suggestions for a coder to
confirm, since the audit-trail requirements differ substantially between the two. It’s
also worth checking how the underlying survey was weighted and whether the respondent
mix lines up with your own team’s composition, and whether a vendor’s outsourced-
services arm is being scored separately from its software, per Black Book’s segment
split, or quietly blended together in marketing material.

The Bigger Picture

Market-research category splits are rarely exciting reading, but this one is a
useful signal about where the mid-revenue-cycle software market is heading: toward
specialization rather than one all-purpose “AI coding” label. For coding and compliance
teams already juggling RADV exposure, payer audits, and FY2027 code changes, a
framework that forces vendors to say plainly which narrow function they’re actually
automating is a small but real improvement over the status quo. You can read Black
Book’s full announcement on
Newswire.

Whichever category framework your team references when shortlisting vendors, the
underlying question stays the same: who is accountable for the final code, and can you
show your work if a payer or auditor asks. Medikode’s automated medical coding platform
is built around that question — keeping a clear, auditable record of every coding
decision rather than treating “AI-assisted” as a single, unexamined label. Learn more at
Medikode’s automated medical coding platform.