On October 2, 2026, revenue-cycle AI company AKASA launched what it calls an autonomous AI platform for the “mid-cycle.” It says the platform can fully code complex inpatient stays, with no human intervention, in under 90 seconds after discharge. It also covers clinical documentation integrity (CDI). The accuracy claims come from the company’s own third-party studies, which haven’t been published in detail. For coders, the job is shifting from assigning codes to auditing them. For patients, faster coding means faster bills, and errors could spread faster too.
Inpatient coding is one of the hardest jobs in billing. A single stay sets the MS-DRG, which drives most of the hospital’s payment. Until now, most vendors have used AI to assist inpatient coders rather than replace them. AKASA’s announcement is a bet that the hardest charts can go “touchless.” It lands while insurers are publicly blaming AI coding for higher costs.
Key takeaways
- AKASA says its system is “designed to fully code highly complex inpatient cases across all specialties with no human intervention.” Outpatient facility coding is coming “soon,” the company says.
- The company says blinded third-party tests showed its AI matched or beat human coders on MS-DRG, principal diagnosis, quality capture and present-on-admission (POA) accuracy. The test covered case types making up 65%–85% of inpatient volume.
- Those are vendor-reported results. The methods and error rates aren’t public.
- The hospital remains responsible for every claim it sends, no matter who or what assigned the codes.
How this article was checked: product claims are quoted from AKASA’s October 2, 2026 press release and TechTarget’s October 5 coverage. Coding rules come from the FY 2027 ICD-10-CM Official Guidelines. We did not test the product. Last reviewed 7 October 2026. This is educational content, not legal advice.
Table of Contents
What AKASA announced
According to AKASA’s press release, the platform extends the company’s existing pre-bill review tools into full autonomy for inpatient coding and CDI. Here are the main claims, side by side with what’s actually verifiable today:
| Claim | Source | Independently verified? |
|---|---|---|
| Fully codes complex inpatient cases with no human intervention | AKASA press release | No |
| Codes a case in under 90 seconds after discharge (vs. 30–60 minutes for a coder) | AKASA press release | No |
| Matched or exceeded human coders on MS-DRG, principal diagnosis, quality capture and POA | Company-commissioned blinded evaluations | No; study details not published |
| Customers represent about 10% of U.S. inpatient discharges and $180B+ in net patient revenue | AKASA press release | No |
| Inpatient volume processed grew almost 6x in the past year | AKASA press release | No |
The release also cites a 2025 study in npj Health Systems that reported medical coding error rates of up to 20%. It also cites a July 2026 GAO review that flagged verifiable accuracy as a central challenge for AI in notes and coding. Both points cut both ways: human coding isn’t perfect, and AI accuracy is hard to prove.
Cleveland Clinic, an existing AKASA pre-bill review customer, “intends to explore” the autonomous product, the release says. That is not the same as a live deployment.
TechTarget’s coverage adds useful context. It cites a MedCodex Health benchmark of 4–6 complex inpatient charts per day for a certified coder. It also notes that vendors are, for now, “keeping human experts in the loop to catch errors and ensure compliance.”
Why the timing matters
A week earlier, the Blue Cross Blue Shield Association said AI-assisted hospital coding added about $942 million to Blue plan costs from 2023 to 2025. Most of that came from extra secondary diagnoses. We break that report down in our analysis of the BCBSA AI coding report.
So an autonomous coder enters a market where payers are watching AI-coded claims closely. Not every coding expert likes the idea. Vanessa Moldovan, who heads RCM strategy at automation company Magical, told CNBC she opposes fully autonomous coding: “There should always be a human in the loop.”
What this means for coders and HIM teams
Autonomous coding doesn’t remove the coding job. It moves it. Here is our read of where the work goes:
- From coding to auditing. Someone has to validate the AI’s output. Plan a standing pre-bill sample by DRG family, plus 100% review for high-risk cases such as MCC-driven DRGs, mortality cases and short stays.
- Secondary diagnoses get the hardest look. Under Section III of the FY 2027 ICD-10-CM Official Guidelines, an “other diagnosis” must be clinically significant. It must require evaluation, treatment, testing, a longer stay, or more nursing care or monitoring. Abnormal labs aren’t coded “unless the provider indicates their clinical significance.” An autonomous system has to follow the same rule.
- POA indicators matter more. POA errors can affect quality reporting and hospital-acquired condition penalties. Audit them as closely as the DRG.
- Exception queues become the real workload. Cases the AI won’t code, or codes with low confidence, still need humans. Staff those queues before you turn autonomy on.
- Keep the evidence. Log the model version, the codes it assigned, and any human overrides. If a payer or auditor questions a pattern months later, you’ll need to show how each code was chosen.
Leaders are already saying the threat runs both ways. “The greatest threat is not autonomous coding replacing staff,” UC Davis Health’s Tami McMasters Gomez told Becker’s, in an October 2 article on the revenue cycle leader role. “It is payer automation denying or delaying reimbursement faster than providers can identify and respond to it.”
What it means for denials and compliance
Faster coding helps cash flow only if claims hold up. Before going autonomous, track these numbers on AI-coded claims versus human-coded ones:
| Metric | Why it matters |
|---|---|
| DRG downgrade rate after payer review | First sign that payers dispute AI-coded severity |
| Clinical-validation denials by diagnosis (anemia, malnutrition, sepsis, etc.) | Shows which “bump codes” draw challenges |
| Medical necessity denials (CO-50) | Separates coding problems from coverage problems |
| Corrected or rebilled claims | Rework cost that offsets the speed gain |
| Appeal overturn rate | Tells you whether your documentation backs the codes |
The compliance rule is old, but it still applies. The organization that submits a claim is responsible for its accuracy. A vendor’s accuracy study doesn’t change that. If AI-assigned codes drift upward without support in the record, the hospital carries the risk. That includes audits; see OIG audit triggers in medical billing.
What it means for patients
- Bills may arrive sooner. Inpatient accounts can wait days for a coder. If coding takes seconds, your claim, EOB and bill may all move faster.
- Mistakes can repeat at scale. One human coder’s error affects that coder’s charts. A flaw in an automated rule could repeat across many patients before anyone notices.
- You can still check the codes. Ask for an itemized bill and compare it with your Explanation of Benefits. If a diagnosis looks wrong, ask the hospital’s billing office for a coding review. If the claim was denied, our guide to the most common claim denial reasons explains what the codes mean.
The bottom line
AKASA’s launch is a real step toward touchless inpatient coding, but the proof so far is the company’s own. Hospitals that try it should treat it like a new coder on probation. Audit heavily at first, measure payer pushback, and expand only when the numbers hold. Coders who learn auditing, CDI and denial work will be the people these systems still need.
FAQ
What is autonomous medical coding?
It’s software that assigns diagnosis and procedure codes and sends the claim forward without a human coder reviewing that chart. Assisted coding, by contrast, suggests codes for a human to accept or change.
Does AKASA’s system really need no human review?
AKASA says it’s “designed to fully code” complex inpatient cases “with no human intervention.” It also says it will work with each health system on a custom plan to scale autonomous volume. How much human review each hospital keeps is up to that hospital.
Is AI coding more accurate than human coders?
AKASA says blinded third-party tests showed its AI matched or beat human coders on key measures. The study details aren’t public, so outside experts can’t check them yet.
Will autonomous coding replace medical coders?
It’s more likely to change the job than end it. Auditing AI output, handling exceptions, CDI and denial work still need trained people.
Who is liable if an AI codes a claim wrong?
The provider or hospital that submits the claim is responsible for its accuracy. That doesn’t change because a vendor’s software chose the codes.
Sources
- AKASA, AKASA Launches First Autonomous AI Platform for Coding and Documentation, Oct. 2, 2026.
- TechTarget RevCycle Management, AKASA launches AI for autonomous mid-cycle coding, Oct. 5, 2026.
- CNBC, Health insurer points finger at AI as nearly $1 billion in questionable hospital charges appear, Oct. 1, 2026.
- Becker’s Hospital Review, 4 things to know about the revenue cycle leader role in 2026, Oct. 2, 2026.
- CMS, ICD-10-CM Official Guidelines for Coding and Reporting FY 2027, Section III.
- U.S. GAO, Science & Tech Spotlight: AI for Medical Notes and Coding (GAO-26-109116).
Manikandan J is a CPC (AAPC) and CRCR (HFMA) certified medical billing professional with billing and RCM experience at athenahealth, Omega Healthcare, UnitedHealthcare, Blue Cross Blue Shield and Access Healthcare. He writes Medical Billing 101’s guides on denial codes, appeals and patient billing help for US billers, providers and insured patients.
