--- title: "Blue Cross Says AI Coding Added $942M to Its Costs. Who Audits the Coder?" slug: "ai-medical-coding-intensity-bcbs-942m-who-audits-the-coder" author: "ibl.ai Engineering" date: "2026-10-01 09:00:00" category: "Premium" topics: "AI medical coding, coding intensity, BCBSA analysis, hospital revenue cycle, DRG upcoding, clinical documentation integrity, healthcare AI governance, self-hosted healthcare AI" summary: "The Blue Cross Blue Shield Association estimated in September 2026 that rising inpatient coding intensity added about $942 million to Blue plan spending between 2023 and 2025, and noted that more than 60% of hospital systems now run AI tools over clinical notes. BCBSA did not prove AI caused it, because claims data cannot show you the reasoning, which is the actual governance problem on both sides of the claim." banner: "" thumbnail: "" linkedin: | The Blue Cross Blue Shield Association published an analysis in September estimating that rising inpatient coding intensity added roughly $942 million to Blue plan spending between 2023 and 2025. The numbers are worth reading precisely, because the headline version gets the direction of the money backwards. The share of inpatient cases coded as medically complex went from about 37% in early 2023 to 40% by the end of 2025, with no matching increase in the treatment intensity the claims data shows. Roughly 70%, more than $650 million, traced to secondary diagnoses that moved stays into higher-paying DRGs. BCBSA also notes that more than 60% of hospital systems now use AI-enabled tools that read clinical notes for codable diagnoses. Three things the careful reader should hold onto: 1. The $942M is added spending for the Blue plans. That is the payer's cost, not a hospital expense. Hospitals received those payments. 2. BCBSA stopped short of proving AI caused any individual increase. The analysis works from claims rather than complete patient charts, and names no hospital and no vendor. 3. The American Hospital Association disputes the reading, arguing patients are older and sicker, that AI helps document legitimate complexity, and that insurers run their own automated systems to downcode claims in the other direction. Which is the part that actually interests me. Both parties are running models over the same encounter, and neither can inspect the other's. The dispute is not resolvable from claims data, because the reasoning is the evidence and the reasoning sits inside somebody's vendor. A hospital cannot audit the payer's downcoding model. It can decide whether its own coding assistant produces an inspectable record: which note, which phrase, which code, which human confirmed it. On ibl.ai you own all the code and the data, so that audit trail is yours rather than a vendor's export. Clinical documentation integrity was always a governance discipline. Automating it on both sides just raised the cost of not being able to show your work. #iblai #HealthcareAI #AIGovernance #RevenueCycle #ClinicalAI --- ## The Short Answer **The Blue Cross Blue Shield Association estimated in September 2026 that rising inpatient coding intensity added roughly $942 million to Blue plan spending from 2023 to 2025, and that more than 60% of hospital systems now run AI tools over clinical notes. It did not prove AI caused it, because claims data cannot show the reasoning. On ibl.ai you own all the code and the data, so the reasoning behind each suggested code stays an artifact you can audit.** The analysis was announced in **late September 2026**. It is a serious piece of work, and the way it travelled is a good illustration of how a careful claims finding turns into a headline that inverts it. ## What did Blue Cross Blue Shield actually say about AI medical coding? It described a divergence between how sick patients are coded and how much treatment the claims show them receiving. The share of inpatient cases classified as medically complex rose from approximately **37% in early 2023 to 40% by the end of 2025**, without the corresponding increase in care that clinical complexity normally brings with it. About **70% of the incremental cost, more than $650 million**, was associated with secondary diagnoses that moved a hospital stay into a higher-severity, higher-paying diagnosis-related group. The association's September whitepaper, [Hospital Coding Intensity Analysis: Major Bowel Procedures](https://www.bcbs.com/media/pdf/BCBSA-AI-Coding-Intensity-Whitepaper.pdf), works through more than **55,000 excess complex cases** in a single procedure family. The AI link is an adoption statistic rather than a causal finding: **more than 60% of hospital systems** now use AI-enabled technology capable of examining clinical notes and records for diagnoses that affect coding. ## Did Blue Cross Blue Shield prove AI caused the $942 million? No, and the association is explicit about it. This is the single most important sentence in the coverage and the one most often dropped. BCBSA **stopped short of proving that artificial intelligence caused each increase**. Its analysis relies primarily on claims data rather than complete patient charts, and it identifies no individual hospitals and no AI vendors. That is not a weakness in the research. It is a description of what claims data can and cannot establish. A claim records the code that was submitted. It does not record why. The earlier companion analysis, [Rising Coding Intensity and Its Impact on Health Care Affordability](https://www.bcbs.com/dA/70bb93b3a9/fileAsset/Rising-Coding-Intensity-and-Its-Impact-on-Health-Care-Affordability.pdf), found an approximately **9% per-member increase** in inpatient costs from 2023 to 2024 across a subset of plans covering about **62 million members**, with roughly **20%** of that increase attributable to rising coding intensity. Two consecutive analyses, consistent direction, and in both cases the mechanism is inferred from the output rather than observed in the process. ## Who actually paid the $942 million, hospitals or insurers? The Blue plans did. The $942 million is **added spending absorbed by BCBS companies**, which flows through to premiums and ultimately to employers and members. This matters because the widely circulated framing has it as a cost *to hospitals*. It is the opposite: hospitals received those payments. The payer booked the cost. Getting that backwards changes who the story is about. A hospital reading "AI billing tools are costing hospitals $942 million" would reasonably conclude the tools are a financial risk to the hospital's own margin. The real exposure for a hospital is different and arrives later: payer audits, denials, repayment demands, and in the worst case a False Claims Act theory built on a pattern the hospital's own vendor generated. ## What does the American Hospital Association say about AI coding intensity? It disputes the interpretation, and the counterargument is not frivolous. The AHA's position is that hospitals now care for **older and sicker patients**, and that AI helps clinicians document legitimate medical complexity that manual coding missed. On that reading, rising complexity codes are a correction rather than an inflation. The AHA also makes a point that reframes the whole dispute: insurers run their own automated systems to **downcode** claims in the opposite direction. So both parties to the claim are running models over the same patient encounter. Each one's model is optimized toward its own revenue position. Neither can inspect the other's. ## Why is AI medical coding a governance problem rather than a model problem? Because the disagreement is about reasoning, and reasoning is the one thing neither side currently has to produce. A claims-level analysis can show that complexity codes rose faster than treatment intensity. It cannot distinguish a coder catching a documented comorbidity that a human would have missed from a model reaching for a defensible code the clinical picture does not support. The distinction lives in the chart, the note, and the inference that connected them. That is an artifact, and whether it exists at all is a procurement decision made before the first claim goes out.
Control What goes wrong without it Where it has to live
Note-to-code provenance An audit asks which documentation supported a secondary diagnosis and the answer is a vendor support ticket Your own records, per suggestion
The optimization target A model tuned for capture rate rather than documentation support, set by someone whose revenue depends on capture rate A prompt and policy you can read and change
Human confirmation record No way to show a certified coder reviewed and accepted the suggestion, which is the defense In the workflow, not reconstructed later
Liability alignment The vendor's terms route responsibility to the provider while the vendor keeps control of the model With whoever controls the behavior
The last row is the one that decides the others. A hospital that cannot change the optimization target has accepted the liability for a behavior it cannot adjust. The in-house alternative and what it takes to run is in [AI Medical Coding In-House](/blog/ai-medical-coding-in-house), and the mirror-image problem on the payer side of the same claim is in [Healthcare AI for Revenue Cycle: Prior Authorization and Denials](/blog/healthcare-ai-revenue-cycle-prior-authorization-denials). ## Where does ibl.ai fit in a hospital's medical coding stack? On ibl.ai you own all the code and the data. The coding assistant, the prompts that define what it optimizes for, the retrieval over your clinical documentation, and the audit log of every suggestion and every human decision all run inside your own perimeter, model-agnostic across any LLM, with no per-seat pricing. That answers the specific exposure this analysis creates. A health system cannot stop its payers from running downcoding models, and should not expect to. It can make sure that when a payer audit arrives, the chain from note to code to the coder who approved it is a record it holds rather than an export it has to request. **1.6M+ users across 400+ organizations** run the platform this way, including NVIDIA, MIT, and Syracuse University. The broader version of this question, covering observability across clinical AI rather than coding alone, is in [Clinical AI Governance and Observability: Hospitals Own the Stack](/blog/clinical-ai-governance-observability-hospitals-own-the-stack). ## Want a coding stack your health system actually owns? We deploy clinical documentation and coding agents as source code you keep, with the provenance and audit trail in your own systems, in your cloud, on-premise, or fully air-gapped. [Book a 30-minute demo](https://cal.com/iblai/30min) or [talk to the ibl.ai team](/contact). ibl.ai is family-owned and operated from New York, NY. *Sources: the $942 million estimate, the 37% to 40% complexity shift, the 70% secondary-diagnosis share and the 60%+ AI adoption figure from BCBSA's September 2026 announcement, reported in [the Dallas Express](https://dallasexpress.com/business-markets/blue-cross-says-ai-enabled-hospital-coding-added-942-million-in-costs/); the 55,000 excess complex cases from [BCBSA's Hospital Coding Intensity Analysis whitepaper](https://www.bcbs.com/media/pdf/BCBSA-AI-Coding-Intensity-Whitepaper.pdf); the 62 million members, 9% and 20% figures from [Rising Coding Intensity and Its Impact on Health Care Affordability](https://www.bcbs.com/dA/70bb93b3a9/fileAsset/Rising-Coding-Intensity-and-Its-Impact-on-Health-Care-Affordability.pdf); BCBSA's own summaries at [New BCBSA Research on AI Hospital Billing](https://www.bcbs.com/about-us/association-news/new-bcbsa-research-on-ai-hospital-billing-driving-higher-health-care-costs); the AHA response as reported in the same coverage.* ## Why does owning the AI stack matter? **ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.** - **You own all the code and the data.** Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours. - **Model-agnostic.** Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform. - **No per-seat pricing.** Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ. - **Deploy anywhere.** Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University. ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.