UnitedHealth's $100M upcode suit ⚖️, healthcare data is trapped oil 🛢️, your app needs to be agent-friendly 🤖
The Boring Layer Just Got a $100M Lawsuit
Friday, the Massachusetts AG sued UnitedHealthcare for allegedly making low-income seniors look sicker than they were to pull at least $100M in extra MassHealth payments over a decade.
The mechanic is almost mundane: nurses coached to document patients’ “worst days”, occasional headaches written up as migraines. No algorithm, no breach. Just diagnoses, slightly inflated, at scale.
While capital floods into the 40th ambient scribe, the place where billions move and AGs now subpoena is the boring plumbing: how a diagnosis becomes a code becomes a payment. That layer is barely tooled, and it’s where domain expertise — knowing what a defensible HCC actually looks like — is the scarce input.
😤 “This is a payer compliance story. I build clinical tools.” The line between “clinical” and “payer plumbing” is exactly where the opportunity is hiding. A documentation-integrity tool that flags an unsupported HCC before submission is a clinical tool — it just happens to also keep your health system off the AG’s list.
😤 “Risk-adjustment software already exists.” It exists to maximize capture. Almost nothing exists to defend it — to prove every code was supported, with an audit trail you’d hand a regulator. After this week, that’s the side of the trade with the tailwind.
Healthcare’s Data Is Trapped Oil — and the Codes Are the Missing Drill Bit
The argument making the rounds this week: clinical data is pre-fracking oil — abundant (one vendor sits on records for 300M+ Americans) but trapped in unstructured notes, and AI is the extraction tech.
The vivid example: GLP-1 side effects are almost never coded. There’s no ICD entry for “abdominal pain secondary to a GLP-1 agonist,” so the signal lives in free text, invisible to every analytics layer downstream.
The bottleneck isn’t the model — it’s knowing where the trapped value is, and that’s a clinical-domain question.
😤 “Extracting structured data from notes is a solved NLP problem.” Extraction is solved. Knowing that GLP-1 nausea hides under a generic “nausea” code, or that a med-rec discrepancy lives in the discharge summary and not the problem list — that’s not an NLP problem. That’s a clinician noticing.
“Agent-Friendly” Is Becoming a Product Requirement
The emerging idea in builder circles: stop bolting AI features onto your SaaS and instead make the tool agent-friendly — usable by a user’s own agent, not just the user.
In practice that’s starting to mean BYOA (”bring your own agent”) access policies — agents hitting your data and services without a human login, which means per-session logging, scoped permissions, and functionality certification, mirroring how you’d onboard an employee.
For provider- and institution-facing tools, “can an agent safely use this” is about to be an RFP line item — and most health IT products have no answer.
😤 “My users are patients, not agents.” Maybe today. But the provider and institutional side is where this bites first — and if your product is a system of record, someone’s agent is going to try to read it whether you designed for that or not.
The Hassle Factor Is an Architecture Problem, Not a Wellness One
A new physician survey making waves: “hassle factor” and “too stressful” are now the top reasons doctors leave clinical practice early — malpractice premiums, which topped the 2008 list, have fallen to the bottom. Average departure age: 48, nine years younger than the 2008 cohort.
Hassle is non-clinical work routed onto the most expensive layer in the building — the physician. That’s a queueing-and-routing problem, not a resilience deficit. You don’t fix a misrouted queue with a pizza party.
💡 80/20: If you’re building clinician-facing software, measure it by work removed or rerouted, not features added. The best inbox tool deletes messages that never needed a doctor.
Epic Moves to Bar AI Tools From Discovery
In a pro se suit against Epic, the plaintiff filed a brief flagged “assisted with AI,” and Epic is now arguing AI tools (ChatGPT, Claude, Gemini) should be barred from touching confidential discovery materials. A small case with a big question: as agents read everything, who’s allowed to feed them what?
824 of 1,024 Agent Skills Were Malicious
A scan of one popular agent-skill marketplace audited 1,024 “skills” and found a large share malicious — a preview of the supply-chain problem coming for anyone wiring third-party MCP servers or skills into a clinical agent. Vet your dependencies like they touch PHI, because eventually one will.
Ultra-short:
Clover beats CMS on Star Ratings. Clover won its Medicare Advantage Star Ratings lawsuit against CMS — another data point that the ratings/risk machinery is now litigated as hard as it’s built.
Out-of-Pocket announces “Ship It.” A healthcare software-engineering micro-conference (NYC, Sept 17–18, apps due July 1, capped ~60–80) — workshops on Anthropic BAAs, forward-deployed engineering, EHR integrations, and Chrome sidecars. Plus a free AI × RCM class June 29–July 1.
Cognition raises $1B at $26B. The Devin maker raised a $1B Series D at a $26B valuation — async coding agents keep pulling capital. The harness, not the model, is increasingly the product.
🎙️ From the Pods
🎙️ The 229 Podcast — “Healthcare at Home Is Closer Than You Think”
The reusable idea isn’t hospital-at-home — it’s the orchestration layer underneath it: a “virtual floor” attached to the EHR, and a platform that turns hospital orders into home orders so a dispatched team can execute them. The host’s line lands: the command center is “air traffic control” — “where families call when they’re scared at 2 a.m.”
💡 Builder take: The hard part of care-anywhere is the translation/routing layer between systems, not the care itself. That’s a builder problem with no dominant winner yet.
🎙️ CEO Pajama Time — “Distribution as an Extinction-Level Event”
A founder’s blunt framing: in healthcare, the thing that kills you usually isn’t the product — it’s distribution. Capital discipline and hiring for character buy you the runway to survive solving it.
What are you building this week? Reply and tell me — I read every one.
— Kevin