A demo day nobody announced 🚪, FHIR as agent guardrails 🛤️, /compact is a bad sign-out 📋
⚡ Around the Wards
FDA and CMS hosted a “clinical AI demo day” nobody announced — ten companies at White Oak on July 8, and the agenda covered both regulation and how to pay for it.
Explainable AI made primary care doctors better and lay people worse — 623 lay people, 153 PCPs, and the fairness-trained model that closed a skin-tone accuracy gap left lay users anchoring on whatever the AI said.
A FHIR team built the same personal health record twice to see if the standard is a good agent guardrail — the version with server-side validation on every write was the one worth keeping.
Sentara moved to terminate its Anthem contracts over a 7.2-point gap — 380,000 Virginians, and the CFO on the other side of your pitch is doing this math right now.
CMS finalized the FY 2027 inpatient rule and closed the Breakthrough Device shortcut to Medicare add-on payment — the designation no longer stands in for proof that the thing works better.
🧭 The Curbside
“Can I self-host a voice model instead of signing another scribe contract?”
Short answer: Closer than it was on Monday, and still not a product.
What changed: NVIDIA published NemotronLabs VoiceChat-11B on Monday — an 11-billion-parameter model doing streaming speech understanding, speech generation, and tool calling in a single architecture, with open weights. The reason that combination matters is that it collapses a three-vendor pipeline — ASR, LLM, TTS — into one artifact you can run inside your own boundary. No third-party BAA in the audio path.
Builder read / Watchout: Open weights are a licensing fact, not a clinical one. Nothing here has been validated on accented speech, interpreter-mediated visits, or an ED at 2 AM with a monitor alarming — and real-time full-duplex at 11B is a GPU line item, not a laptop. The license is OpenMDW-1.1, which is permissive and does allow commercial use — but the model card itself says the model is “ready for research purposes only,” which is the sentence your compliance office will read. What this genuinely unlocks is evaluation: you can now build a scribe-eval harness without paying a vendor for the privilege of testing them.
😤 Haters: “Great, another open model that will be superseded in six weeks.” Probably. But the thing that persists isn’t the checkpoint — it’s your harness, your test set, and your knowledge of which failure modes matter in your setting. Those outlive every model release. Build the part that doesn’t expire.
“A patient just handed me a QR code containing a summary of their whole chart. What is that?”
Short answer: A Smart Health Link, and it’s now a default consumer feature rather than a standards demo.
What changed: Google Health 5.05 shipped Smart Health Links to US users on August 3, letting anyone generate a secure, shareable summary of their medical records as a URL or QR code (Google describes the rollout as phased over the coming weeks) — no portal login, no CCD export, no FHIR endpoint to negotiate. The same release turned on two-way sync with Apple HealthKit, so Fitbit and Pixel Watch data now crosses into iOS natively.
Builder read / Watchout: Interesting concept but read the google post disclaimer: “Not intended for medical purposes or as a substitute for official clinical health records. “
🔬 The Big Thing
Ten companies got a demo day with FDA and CMS. Nobody was told it happened.
On July 8, officials from the FDA and CMS hosted what an internal agenda called a “clinical AI demo day” at FDA’s White Oak headquarters. Ten companies presented.
Anthropic. Microsoft AI. Amazon One Medical. K Health. Curai. Counsel Health. Doctronic. Ellipsis Health. Hippocratic AI. Welldoc.
The meeting was not publicly announced. STAT’s Mario Aguilar reviewed the agenda and published it yesterday.
Read the list twice. There is no health system on it. No specialty society. No nursing organization. No FQHC network. No academic evaluation group. No open-source project.
The agenda wasn’t only “is this safe.” It was also “how should Medicare pay for it” — and that second question is the one that decides what actually gets built.
Here’s why that distinction matters more than the guest list.
FDA clearance tells you a thing is legal to sell. It does not get the thing into a workflow. What gets a technology into a workflow is a payment mechanism — a code, a rate, an add-on, a bundle. That is why the FY 2027 inpatient rule finalized this week is a bigger deal for medical AI than most 510(k)s, and why every serious health tech founder eventually stops reading FDA guidance and starts reading the Federal Register.
The companies in that room understand this. Several of them are building autonomous or near-autonomous clinical products — the kind that don’t fit any existing evaluation-and-management code, because there is no physician performing the service. Somebody has to invent the payment category. The people shaping how that category gets defined were in a room in Silver Spring on a Wednesday in July, and the people who will have to live with the result were not.
I want to be fair to everyone involved. Regulators talking to builders is good. Agencies that write rules about technology they have never seen operate write bad rules, and hands-on sessions are how you avoid that. Four of the attending companies talked to STAT openly about what they said.
But “we met with industry to understand the technology” and “we met with industry to work out how to pay for the technology” are different meetings, and only one of them is a policy process.
If you build clinical software and you are not reading proposed rules and filing comments, you have outsourced the definition of your market to ten companies who were invited and you were not.
The comment docket is the room that is actually open. It is unglamorous, it is slow, and it is the only venue where a community health center’s operations director and Microsoft get the same word count.
😤 “This is a nothingburger. Agencies meet with industry constantly, that’s what a regulator does.” Constantly and, ordinarily, on the record — advisory committee meetings are noticed, minuted, and open. The thing that makes this one worth a paragraph is that it wasn’t announced and we only know the guest list because a reporter got the agenda. If the process is unremarkable, publishing it costs nothing.
😤 “What exactly do you want, a physician on every panel?” Yes, and it’s not a big ask. There are federal advisory committees for hearing aids.
😤 “Clinicians can already comment on proposed rules. Nobody does.” Correct, and that’s the actual problem in this story.
🧪 Try the interactive: The Underwater Line — every Medicare DRG price, and the technology cost that sinks it — all 773 national MS-DRGs plotted at once, average Medicare payment against annual discharges, with a slider that drags a new technology’s cost across them so you can watch how much of American inpatient care it cannot fit inside. Built with real CMS data.
📡 Builder’s Radar
The same AI explanation made experts sharper and everyone else worse
A Nature Medicine study of 623 lay people and 153 primary care physicians tested LLM-generated explanations alongside dermatological diagnoses.
The headline finding is the good one: assistance from a fairness-constrained model — one trained to perform evenly across skin tones — improved final diagnostic accuracy and reduced skin-tone-related performance disparities for both groups. Credit the fairness training, not the explanation.
The finding underneath it is the one builders need. Lay users showed automation bias — their accuracy rose when the model was right and fell when it erred. Experienced PCPs stayed resilient irrespective of the AI’s accuracy. Separately, the authors flag an ordering effect that applies to everyone: showing the model’s diagnosis before the human decides produces stronger anchoring.
The same explanation is a decision aid for someone with a prior and a suggestion engine for someone without one.
This is the cleanest evidence I’ve seen that “who is the user” is not a product-marketing question — it’s a safety parameter. A tool validated on physicians and then shipped direct-to-consumer is not the same tool.
😤 “So don’t give patients AI. Got it.” Not what it says. It says an interface that shows a confident explanation to someone with no way to falsify it is doing something different than the same interface shown to someone who has seen four hundred rashes. Design for the difference — friction, uncertainty display, an explicit “here’s what would change my mind” — instead of shipping one UI and calling it democratized.
A clinician read Steve Yegge on agent context and recognized the sign-out
Doug Fullington makes the argument I wish I’d made: agentic context handoffs are a patient handoff problem, and medicine spent thirty years solving it.
The literature he pulls is exactly the right literature. Petersen’s 1994 work found 6.1 times the odds of potentially preventable adverse events under cross-coverage (a wide confidence interval, 1.4–26.7, off 54 events — the direction is solid, the point estimate is not). The 2014 NEJM I-PASS trial cut medical errors 23% across 10,740 admissions — by standardizing what gets transmitted, not by asking people to try harder.
His line lands: /compact is a discharge summary written by someone who never met the patient.
Every clinician already knows that the dangerous moment is not the work — it’s the transfer of responsibility for the work. AI engineering is rediscovering this from scratch, and clinicians are the only people who arrive with the solved version.
⚠️ Disclosed in his post: Fullington is a physician part-owner of Catalyst Health Group, which has a financial interest in Matic, an AI clinical documentation platform. It doesn’t change the handoff argument, but you should know it’s there.
🔮 Where this lands: structured agent handoff becomes a named pattern within a year, and whoever writes the I-PASS of context compaction gets cited for a decade. I don’t think it’s an AI lab that writes it.
Sentara would rather drop 380,000 people than take a 1% cut
Sentara Health issued a termination notice to Anthem after eight months of stalled negotiation. Sentara asked for a 6.2% blended increase for 2027; Anthem countered with roughly a 1% decrease. Most affected commercial and Medicare agreements run through at least December 31, 2026; the Medicaid agreement runs to January 28, 2027, and others expire on a rolling basis during 2027.
That is a 7.2-percentage-point gap across commercial, Medicare, and Medicaid lines covering roughly 380,000 Virginians.
A health system that will walk away from 380,000 covered lives rather than absorb a one-point cut is not negotiating. It’s out of room.
Ultra-shorts
Hinge Health is buying Cylinder for $105M
The publicly traded musculoskeletal company is going all-cash for a gastrointestinal-care startup, extending from MSK and migraine into IBS and IBD for its existing member base. Condition-by-condition consolidation, at speed.
Amae Health is wiring Fitbit data into serious mental illness care
Sleep, activity, and heart-rate variability from Google Health Enterprise, pushed into clinical workflows to flag early relapse signs between visits for patients with SMI. The passive-signal thesis finally pointed somewhere it might matter.
A health system led a Series B
Wellinks closed the first $10M tranche of its Series B with participation from UMass Memorial Health — a health system, not a venture fund. No lead investor was named. When your customer writes part of the check, the pilot conversion problem gets a lot easier.
🛠️ From the Workbench
Health Samurai’s PHR, built twice
A team rebuilt the same personal health record twice with Claude Code — once on plain React/Node/Postgres, once FHIR-native — to test whether FHIR functions as a framework for agentic development rather than just a data standard.
The v1 failure mode will be familiar to anyone who has driven an agent past a toy project: it invented its own data model, then drifted away from it every session. The v2 result was a smaller, more coherent codebase, because the agent had rails — a fixed data model of 150+ FHIR resources, server-side validation on every write, and generated types so a wrong field name fails at compile time instead of at 2 AM.
The detail that convinced me is small: asked for a patient summary, the agent reached for Composition, FHIR’s own model for a sectioned clinical document, and wired it to existing Condition, MedicationStatement, and AllergyIntolerance resources. No bespoke schema. A feature became a conversation.
Both the PHR source and the Claude Code skills are open.
💬 Standout Quote
“Doctors as builders — no dev team in the middle; describe the workflow, get a working app.”
🎙️ From the Pods
🎙️ Relentless Health Value — “EP523: The Sleeping Giants of Healthcare, with Suhas Gondi, MD, MBA”
Gondi walks through a GLP-1 denial where the physician did everything right — shared decision-making, told the patient to verify coverage, patient confirmed the employer covers it, clinic cleared every prior-auth criterion — and the patient still got quoted list price at the counter. The reason: the employer had recently decided to cover the drug only through a third-party wraparound vendor, and that vendor is the sole covered prescriber under the plan. Nothing in a formulary check surfaces that.
The structural point is worse than the anecdote. There is no path at all from a pharmacy claim rejection back to the clinician who wrote the prescription. The doctor usually finds out at the three-month titration visit, which is to say the patient took nothing for three months.
“There’s no feedback, right, from that pharmacy about that claims denial to that clinician and to their office.” — Suhas Gondi, MD
🔇 Speaker Blindspot: False cause substitution. Gondi carefully establishes that both employers and clinicians are acting in good faith, which leaves ignorance as the only remaining explanation — so his remedy is awareness and local conversations. But he supplies the fact that kills that remedy himself: a clinician cannot possibly track which of hundreds of plan sponsors each patient has and what each one changed last quarter. He raises the impossibility and then recommends meetings anyway. This is an information-routing problem that needs machine-readable benefit design at the point of order, not an information-awareness problem that needs better-informed doctors.
🎙️ Vital Signs — “Ep 70: Nourish CEO Aidan Dewar on Hiring in the AI Era”
Two things worth stealing. First, Dewar reports the bottleneck moving in opposite directions on either side of his company: in engineering, code stopped being the constraint and product definition became it; in strategy and operations, AI made scoping so fast that they now hold a backlog of well-specified work they lack people to execute.
Second, and more concrete: they took meal logging, progress tracking, goal setting, meal planning, recipes, and messaging — six roadmap features living in six parts of the app — and collapsed all of it behind a single AI health assistant. Engagement and retention went up.
💡 Builder take: If AI-assisted coding removed implementation as your limiting factor, then spec quality is your binding constraint — and precise clinical specification is exactly the asset a practicing clinician has and a product manager doesn’t. Stop optimizing build speed. Also: go count the discrete features in your own tool’s nav tree, and ask what survives if you collapse them behind one conversational surface.
🔇 Speaker Blindspot: Composition fallacy dressed as Jevons paradox. Dewar argues AI makes care cheaper and better, so demand rises, so employment rises — ending on more clinicians than today. Jevons needs elastic demand and a substitutable constrained input. Clinical demand is gated by payer willingness to pay, not consumer appetite, and the constrained input is a credentialed dietitian requiring a master’s plus 1,000 supervised hours. The tell is in the transcript: asked directly whether they’d train their own supply, he says they haven’t considered it. He asserts the outcome while declining the only lever that produces it. Worth noting the whole episode contains not one outcome endpoint, effect size, or comparator behind repeated claims that the product improves outcomes, and the host never asks.
💡 BTW
💡 BTW: Suhas Gondi — the physician arguing on this week’s podcast that clinicians don’t understand how their patients’ benefits work — interned at CMS, the Brookings Institution, and the U.S. Senate before he ever went to medical school. He learned the payment system first and the medicine second, which may explain why he can see the seam the rest of us walk past.
💺 Builder Seats
Physician Informatics Executive (IC4) — Oracle · Remote (US)
EHR-vendor side, which is a rare chance to build from the platform instead of on top of it. Band runs $193,600–$414,400. Two real filters before you click: roughly 80% travel, and it requires US citizenship plus the ability to obtain a government security clearance.
🔗 Apply on LinkedIn
AVP, Digital Transformation — Sarah Cannon Research Institute (McKesson) · Remote (Texas-based)
Enterprise digital and AI transformation across 200+ research sites and 1,300+ physicians, with interoperability and product lifecycle ownership written into the description. Not a physician role, but it’s the seat where clinical trial infrastructure actually gets rebuilt.
🔗 Apply on LinkedIn
Know someone hiring for a clinical AI or informatics leadership role? Reply and I’ll include it.
What are you building this week? Email and tell me (kevin@clinicians.build) — I read every one.
— Kevin