Healthcare goes headless 🔌, Your org chart is the AI bottleneck 🏭, AI fails a 2 AM ECG 🫀
Healthcare’s Systems of Record Are Going Headless — and That’s a Door, Not a Wall
The dominant systems of record are starting to expose their guts as APIs and agent tools instead of locking everything behind a screen.
The frame is “headless”: take the clicks a human (or a bot) makes in a UI and turn them into metered, billable API and MCP calls.
This month’s headless-healthcare roundup from Health API Guy put real names on it. Cognizant TriZetto — whose Facets/QNXT/QicLink platforms touch more than half of insured US lives — launched “Unify,” and a major LTPAC vendor stood up the first sanctioned, governed screen-scraping (RPA) program instead of pretending the bots weren’t there.
The shift is economic, not technical: invisible UI clicks are becoming line items with a meter on them.
For a clinician-builder, this is the door opening. The thing you’ve wanted to automate — pulling a prior auth status, reconciling a roster, checking eligibility — stops being a brittle scraping hack and becomes a sanctioned call you can build on, govern, and defend.
The catch: “headless” is being rolled out selectively, often with no public docs or pricing, frequently just enough to satisfy the CMS-0057 prior-auth API mandate landing in January. Some of these doors are real; some are a peephole with a turnstile.
“The bots are already in the building... the only question has been whether to evict them and incur regulatory risk or charge rent to the squatters and see who leaves.”
😤 “This is just vendors finding a new thing to charge for.” Yes. That’s exactly what it is — and it’s good news, because a metered API is a documented, governed, buildable surface.
😤 “Selectively headless means it’s vaporware until the docs are public.” Fair. Until there’s a spec sheet and a price, treat the announcement as intent, not infrastructure. Build against the standard (FHIR, CMS-0057) so you’re ready when the door actually opens.
😤 “I can’t afford per-call pricing on a side project.” Then prototype on synthetic data and a sandbox now, and let the people who can afford it discover the price. Your job is to know which call is worth making.
❓ If every meaningful UI action becomes a metered call, the most valuable map in healthcare becomes “which workflows are worth paying per-call to automate?” I think there’s a product in just ranking them — a pricing oracle for headless healthcare — but I can’t quite see its shape yet.
💡 80/20: Pick one workflow you do by reflex and ask “if this were an API call with a price tag, would I pay it?”
Health AI’s Real Bottleneck Is Your Org Chart, Not the Model
Two pieces — Jan Beger’s Installation Trap and Stephen Ranjan on why most AI pilots fail to scale — have same diagnosis: clinical AI stalls because of how organizations are built, not because the technology fell short.
The analogy is factory electrification — electric motors hit 53% of factory power by 1919, but productivity barely moved until factories physically reorganized their floors in the 1920s. Most health systems have installed AI and left the workflow untouched.
The receipts: a Stanford lab found 77% of the hardest enterprise AI challenges are organizational; Catalonia registered ~200 AI health tools by late 2025 and fully implemented exactly one; the deployments that worked (e.g., a radiology group that redesigned its operating model before turning on ultrasound AI, hitting up to 30% scan-time reduction) redesigned first and installed second.
If less than half your AI budget goes to changing how people work, you’ve misallocated it.
😤 “So the answer to bad AI is more change management consultants?” No — the answer is a clinician who owns the workflow redesign because they live in it. That person is cheaper and better than a consultant who’s never run the clinic or seen a patient. That’s you.
😤 “My health system will never reorganize around a tool.” Then don’t sell them a tool. Sell them the redesigned workflow with the tool already inside it. Nobody buys a motor; they buy a faster factory.
💡 80/20: Before you build a model, write the one-page “what changes on Monday” doc — who stops doing what, who starts. If you can’t write it, the model won’t land.
An ER Doc Gave Medical AIs an ECG. Most of Them Failed It.
Ashoo Review put the leading medical AIs through an ECG test — a second-degree AV block with 2:1 conduction, ventricular rate 36, with a left bundle. It’s a counting problem, not a pattern-matching one.
Nearly every general medical AI missed it; one popular tool called it AFib with possible STEMI. The models that scored an A were the ones that declined to interpret the tracing at all. A purpose-built model (ECG-GPT) got it essentially right.
Refusing to answer was the safest answer — and almost none of the general tools knew to refuse.
😤 “This is cherry-picking a hard strip to dunk on AI.” It’s a strip an intern is expected to count correctly at 2 AM. If your tool overcalls a STEMI on a rate-36 block, the problem isn’t difficulty — it’s that it doesn’t know what it doesn’t know.
⁉️ “The model that knew to say ‘I can’t read this’ beat the models that confidently guessed.” The product feature hiding in plain sight isn’t accuracy — it’s calibrated refusal. Who’s shipping that as a first-class behavior?
💡 80/20: When you evaluate any clinical AI, include cases it should punt on. A tool that never says “I don’t know” is more dangerous than one that says it too often.
[note: curious what queen on hearts would say about it.]
A $490,000 Denial, and the 82% Nobody Appeals
A retired family physician’s $490,000 emergency hospitalization was denied as “medically unnecessary,” and resolved only after 13 months and a state insurance regulator stepping in.
The systemic numbers are the story: insurers deny ~20% of ACA marketplace claims, as few as 1% of patients appeal, and prior-auth denials that are appealed get overturned more than 82% of the time.
A >82% reversal rate on a 1% appeal rate is not a tragedy — it’s an unbuilt product.
💡 80/20: The builder opportunity is the appeal, not the denial. A tool that drafts a defensible, criteria-cited appeal from a denial letter is squarely buildable on synthetic data today.
Hot Peptide Summer: Care Is Leaving the System, and So Is the Data
By the end of 2026, roughly one in five Americans will have injected a GLP-1 — increasingly through DTC telehealth that routes around insurers, PBMs, and the traditional chart.
The builder problem isn’t the drug; it’s the surveillance gap. An estimated one in four GLP-1 scripts written via telemedicine never makes it into a unified record, because patients file “wellness” purchases in a different mental folder than “healthcare.”
Every script that skips the chart is a med-rec landmine waiting at the next visit.
Downstream of the Data Center
A family physician reframes AI’s environmental cost not as a distant climate stat but as the childhood asthma in her clinic — and notes ~two-thirds of new US data centers are going up in water-stressed regions.
The builder takeaway is refreshingly concrete: ask of any AI tool not just whether it works, but what it costs to run and who lives next to that cost.
“Use the smallest tool that does the job” is now an ethics statement, not just an optimization one. [cf with concept of ALARA but for AI?]
❓ The smallest-model-that-works discipline keeps showing up — privacy, latency, cost, and now equity all point the same direction. Is “right-sized clinical AI” a product category nobody’s named yet?
Ultra-short:
Anthropic filed a confidential draft S-1. The SEC paperwork for a proposed IPO is in; no price, share count, or date — but it puts the lab on the same 2026 runway as SpaceX and OpenAI.
Microsoft Build: seven from-scratch MAI models. Microsoft AI shipped its own model family, led by MAI-Thinking-1 (its first reasoning model, with a 109-page report and “zero distillation” claims) — Microsoft is now a frontier lab, not just a platform.
⭐️⭐️⭐️ The Joint Commission launched a voluntary “Responsible Use of AI in Healthcare” certification. First-of-its-kind; watch whether it becomes a B2B status symbol the way URAC accreditation did.
Elation Health acquired Aster. A primary-care EHR adding to its stack — a small but telling consolidation in the independent-practice tooling layer.
🛠️ From the Workbench
Perplexity “Search as Code”
Perplexity published a new architecture called “Search as Code” that lets a model control the search pipeline programmatically — exposing retrieval primitives an agent assembles via sandboxed code generation, instead of firing fixed queries.
For a clinician-builder, the interesting bit is composability: an agent that can write its own retrieval logic on the fly is the shape of a clinical search tool that adapts to the question instead of forcing the question into a box. Worth a read if you’re building anything that retrieves evidence.
😤 Haters
“Letting a model generate and run its own search code is a prompt-injection buffet.” A real risk — sandboxing is doing heavy lifting here, and you’d want hard limits before pointing anything like this at real data. For synthetic-data prototyping, it’s a fascinating pattern to study.
💡 80/20: Read it as a design pattern, not a product to adopt — the takeaway is “let the agent compose retrieval,” and you can prototype that idea against public datasets long before it touches a patient.
🎙️ From the Pods
🎙️ Lifers with Christina Farr — “How SaaS Is Evolving from Software to AI Solutions”
The line that should be tattooed on every clinician-builder: “Builders, not engineers. Solutions, not software.” The argument is that AI is becoming a blend of services and software — bespoke solutions delivered at SaaS speed and cost.
💡 Builder take: If you’re still framing your project as “software I need an engineer to build,” you’re playing last year’s game. Frame it as a solution you can assemble.
🎙️ Health Tech Nerds Radio — “The Grand Roundup”
A useful gut-check on the platform hype: how many $100B health-AI admin companies can the market actually support? “Probably fewer than you think” — for reference, there are barely a handful of $100B healthcare companies of any kind.
💡 Builder take: Don’t build to become the $100B platform. Build the specialty-specific wedge the platform can’t be bothered to build — and that it’ll eventually want to buy.
💡 BTW: Halle Tecco — whose review of the evidence on private equity in healthcare made the rounds this week — founded a nonprofit called Yoga Bear, offering free yoga to cancer patients and survivors, years before she started Rock Health, the first seed fund built solely for digital health.
What are you building this week? Reply and tell me — I read every one.
— Kevin