AI Billing Added $942M to Health Costs, Plus 4 Stories
Today’s lead is one of those AI stories that sounds boring until you follow the money. Blue Cross Blue Shield Association says changes in hospital coding associated with AI-assisted documentation contributed an estimated $942 million in additional spending for Blue Cross companies between 2023 and 2025. Also this morning: a TeamCity flaw is now showing up in ransomware activity, an older Roundcube patch has become urgent, Microsoft fixed a Windows backup problem, and Tesla’s Semi is finally moving into a larger commercial rollout.
AI may be finding more diagnoses — and more billable ones
Blue Cross Blue Shield Association says hospital records are getting more medically complicated on paper without an equivalent change in the care patients actually receive.
Its analysis of Blue Cross claims found that growth in documented medical complexity contributed an estimated $942 million in additional spending between 2023 and 2025. More than $650 million of that came from secondary diagnoses that moved patients into more expensive billing categories. BCBSA says more than 60% of hospital systems now use AI coding tools that can scan medical notes, lab results and other records for diagnoses that may not have been explicitly captured by a human coder.
That needs some explanation, because “AI made healthcare cost $942 million more” would be a much cleaner headline and a worse description of the evidence.
Hospital payments are often tied to diagnosis-related groups, or DRGs. The basic idea is that a more complicated patient is expected to require more resources, so the hospital can be paid more for treating that patient. Add a qualifying secondary condition and the same hospitalization can move into a higher-paying category.
AI didn’t invent that payment staircase. It may just be getting very good at finding the next step.
BCBSA points to examples such as anemia, where diagnoses increased without a corresponding increase in treatments such as blood transfusions. That is a legitimate reason to ask whether documentation is becoming more severe faster than the actual care is becoming more complex.
I’m not ready to jump from that to “AI is inventing illnesses.” This is an insurer association analyzing claims, not a clinical audit of every diagnosis. Better documentation can absolutely uncover real conditions that humans previously missed, and BCBSA’s analysis can’t prove that every new secondary diagnosis is inappropriate. But when the code gets more severe while the treatment mostly doesn’t, that deserves an auditor before it deserves applause.
This is why AI hospital billing belongs in a technology brief for ordinary people. The extra money doesn’t remain an abstract accounting problem between hospitals and insurers. It works its way into premiums, employer health plans, government spending and out-of-pocket costs. A tool that changes how aggressively a chart gets coded can eventually change what everybody pays.
Turning on AI is the easy part
Deciding what an AI tool should be allowed to see, who should use it, what work it should perform, and what happens when it gets something wrong is the more interesting problem. Raymond Tec helps businesses connect and automate the tools they actually use without treating every new feature like a button that obviously needs to be switched on.
TeamCity bug is now a ransomware problem
JetBrains disclosed CVE-2026-63077 in July, and the reason it matters more today is simple: CISA now says ransomware operators are using it.
The flaw affects TeamCity On-Premises and can let an unauthenticated attacker who can reach the server over HTTP or HTTPS bypass authentication through the agent-polling protocol and execute operating-system commands as the TeamCity server process. JetBrains fixed it in TeamCity 2025.11.7 and 2026.1.3, and it also provides a security-patch plugin for older supported installations that can’t be upgraded immediately. TeamCity Cloud customers don’t need to do anything for this vulnerability.
A build server is not just another web app. It can hold source-code access, deployment credentials and secrets, and it may be trusted to produce the software or artifacts everybody else installs. Compromise the build system and the blast radius can move well beyond the machine running TeamCity.
JetBrains had already warned about active or attempted exploitation. CISA’s ransomware designation raises the priority again. If you run TeamCity On-Premises, patch it now, restrict network access if it doesn’t genuinely need to be public, and review the server for evidence of earlier access. Updating closes the hole. It doesn’t prove nobody used it first.
Roundcube’s May patch is suddenly September’s emergency
Roundcube released versions 1.6.16 and 1.7.1 in May to fix CVE-2026-48842. Canada’s Cyber Centre now says open-source reporting indicates attackers are exploiting the flaw in the wild.
The vulnerability is a pre-authentication SQL-injection bug in Roundcube’s virtuser_query plugin. SQL injection means attacker-controlled input is able to alter a database query instead of being treated only as data. In this case, the bug involves an escaping bypass in the plugin and can be reached before the attacker is logged in.
There is an important qualifier here: this does not mean every Roundcube installation on the internet is automatically exploitable. The vulnerable version and relevant plugin configuration still matter. But Roundcube is commonly bundled into hosting environments and control panels, which means plenty of businesses use it without thinking of themselves as running a separate webmail application.
If you administer Roundcube, verify the actual version and update to 1.6.16, 1.7.1 or newer. If your webmail is managed by a hosting provider, this is a good time to confirm that they have already done that rather than assuming somebody else must have handled it.
Technical discovery & auditing
The public page doesn’t tell you much about the machinery behind it. Raymond Tec audits inherited and long-running projects to uncover the plugins, integrations, data, dependencies, and old decisions that determine what the next change will really involve.
Windows File History can back up again — verify it actually does
Microsoft has fixed a September Windows 11 problem that could leave File History unable to back up or restore files to an external drive or network location. Affected systems could also display a “Reconnect your drive” message even when the drive was connected and working normally.
The fix is in KB5124010, Microsoft’s September 22 optional preview update for Windows 11 24H2 and 25H2.
I would not solve this by uninstalling September’s security updates. Those updates fixed vulnerabilities that were already being exploited. If File History broke on a machine you depend on, install the corrective update — or wait for the fix to roll into the normal cumulative update if you don’t want an optional preview — and then verify that a fresh backup actually completes.
That last part matters. A backup feature failing loudly is annoying. A backup feature nobody checks is worse. Look for a new backup timestamp and, ideally, restore a harmless test file. “The drive is plugged in” is not the same thing as “the backup works.”
Backups & recovery
Backups are comforting right up until you need one. Raymond Tec helps small businesses build practical backup and recovery plans — including the decidedly unglamorous part where we make sure the thing can actually be restored.
Tesla Semi finally becomes a delivery story
Tesla says its dedicated Nevada Semi plant has begun a larger commercial rollout, with new customer deliveries starting this week almost nine years after the truck was first unveiled.
The company says the factory is designed for as many as 50,000 trucks a year. That is capacity and a target, not current output. Tesla also continues to advertise about 500 miles of loaded range for the long-range Semi and roughly 325 miles for the standard-range version.
The scale is finally getting interesting. Reuters reports that a new coalition has ordered 2,500 Semis, including orders tied to companies such as Microsoft and PepsiCo. If those trucks are delivered, the order alone would nearly double the current U.S. fleet of electric Class 8 trucks. Tesla had already delivered a limited number of Semis to PepsiCo beginning in 2022.
For ordinary people, freight technology matters even if nobody is buying an 18-wheeler for the commute. Trucks affect shipping costs, local air quality, warehouse operations and the charging infrastructure built along major routes. Electric semis also have much less room for wishful thinking than a consumer gadget: range under load, charging time, depot power, reliability and total cost per mile all have to work in an industry that notices downtime immediately.
Nine years after 2017, we finally have a better question than “when will the Semi arrive?” Now we get to ask whether it works economically at commercial scale. That’s a much more useful test.
Still in a reading mood? The Raymond Tec News archive covers security, AI, small-business technology, policy, and the places technology collides with ordinary life — without requiring a computer-science degree to get through it.
Sources / Further Reading
- Blue Cross Blue Shield Association: Analysis of AI coding tools and healthcare costs
- Reuters: AI tools generated nearly $1 billion in extra costs, Blue Cross insurers say
- JetBrains: CVE-2026-63077 TeamCity security advisory
- JetBrains: Additional guidance after active TeamCity exploitation
- BleepingComputer: CISA flags TeamCity flaw in ransomware attacks
- Canadian Centre for Cyber Security: Roundcube CVE-2026-48842 advisory
- Roundcube: Security updates 1.6.16 and 1.7.1
- Microsoft: KB5124010 Windows 11 preview update
- Reuters: Tesla begins Semi electric truck deliveries
Photo by Vitaly Gariev on Unsplash.
