Washington wants AI doctors 🩺, Epic's real moat is its memory 🧠, Gemma 4 runs on your laptop 💻
Washington Is Clearing the Runway for AI That Diagnoses and Prescribes — and Nobody’s Named Who’s Liable When It’s Wrong
New Washington Post reporting this week laid out a coordinated federal push to put conversational AI into direct patient care — diagnosing illness and prescribing medicine with limited or no human in the loop.
The specifics are not abstract: more than $50M in research awards for chatbots that can field a call from someone with heart-attack symptoms, a three-month-old Utah pilot letting AI refill prescriptions instantly, an FDA fast track for digital health, and — for the first time — Medicaid reimbursing AI wellness apps.
The same week, OpenAI’s Sam Altman went to Congress to argue the government should not require approval before a model ships — fund post-hoc testing instead of pre-market licensing.
Put the two together and the direction is unmistakable: lower the bar to release the model, and lower the bar to let it practice.
💬 Standout quote:
But for die-hard technologists, the promise of AI doctors goes beyond the technology’s current capabilities … Adam Meier, a former director of Montana’s health department, said that today, robotaxis are a reality on the streets of San Francisco, Los Angeles and Phoenix, but “that didn’t happen overnight.”
[I find the article interesting as the person they profile is/was very much a FHIR advocate … it kinda makes sense that patient access and lower barrier to AI fit together as once you have your data, you need to do something with it to make it meaningful (and apparently this happened for their family).]
😤 “Robotaxis prove AI doctors are coming." Sure — and they got here through years of permits, geofencing, and incident reporting, i.e. the approval layer this same push wants to skip.
😤 “This is just hype — no chatbot is prescribing for my patients.” A pilot in Utah already is. The point isn’t whether it’s good yet; it’s that the policy scaffolding to scale it is being poured right now, and the people who understand the failure modes aren’t the ones in the room when it’s designed.
😤 “If the government won’t gatekeep models, we’re cooked.” Maybe. Or maybe pre-market licensing for something that updates weekly was always going to be theater, and the honest move is to make the post-market layer real. You don’t have to like it to build for it.
📡 Builder’s Radar
Epic Didn’t Win the EHR Wars — Its Memory Did
John Lee, emergency physician and Epic consultant argues that Epic’s dominance was earned, not imposed: competitors chose acquisition over integration and drowned in technical debt while Epic reinvested ~30-50% of revenue into building one coherent system.
The part that matters for builders is the new moat. Cosmos — Epic’s federated database — was an eight-year loss leader that’s now compounding into operational intelligence: tools like “Patients Like Mine” and a length-of-stay predictor that helped one health system shave half a day off average LOS.
Interoperability rules gave us data portability. They did nothing about intelligence portability — you can export the records, but not the synthesized benchmarks built from millions of them.
That’s the lock-in that regulation can’t touch, and it’s why “nobody gets fired for choosing Epic” keeps winning over sound analysis.
😤 “So Epic’s untouchable. Cool, thanks.” Not the lesson. The lesson is that the moat is derived data, and the edge for a builder is the specialty-specific synthesis Epic will never prioritize — the niche your pharmacist or your stroke team needs that isn’t worth Epic’s roadmap.
💡 80/20: Stop trying to out-platform the platform. Find the clinical question Cosmos could answer but doesn’t, because it’s too small for Epic and too specific for anyone without your domain knowledge. (Becker’s has the raw numbers on Epic’s scale if you want the receipts.)
Meta Shipped an Agent Platform for Businesses — Study the Shape, Not the Logo
Meta launched a Business Agent that answers customers across WhatsApp, Messenger, and Instagram — and, notably, doubles as an assistant that gives the owner a morning briefing summarizing overnight chats.
The pattern is the tell: agent for the customer + platform to build on + a daily briefing for the operator. That’s a clean template for a clinician-facing product — the agent triages, and the clinician gets a digest of what happened while they were asleep.
Ultra-short:
A two-year-old Oracle WebLogic bug is under active exploitation. Patch available, attackers exploiting unpatched internet-facing instances anyway — a reminder that the scariest health-IT vulnerability is rarely the zero-day; it’s the legacy middleware nobody patched.
Microsoft is teaming with Mayo Clinic to handle the flood of health questions people are already dumping into chatbots. Worth watching as the “branded clinical guardrails on a general model” play takes shape. (Interesting that Mayo will own the model, not MSFT)
🛠️ From the Workbench
Gemma 4 12B (open weights, runs on a 16GB laptop)
Google released Gemma 4 12B, an encoder-free multimodal model that takes vision and native audio straight into the LLM — and runs locally on a consumer laptop with 16GB of RAM under an Apache 2.0 license.
For a clinician-builder, “frontier-ish multimodal with the network unplugged” is the whole game: local inference means nothing leaves the box. Native audio on-device is the obvious hook for ambient-documentation prototyping on synthetic encounters.
😤 “Open weights, sure, but it’s not GPT-5.5.” It doesn’t have to be. The benchmark that matters for a home prototype isn’t leaderboard rank — it’s “good enough to run offline on hardware I already own,” and a 12B that approaches the 26B at half the memory clears that bar.
💡 80/20: Pull it in LM Studio or Ollama this weekend and feed it a synthetic visit transcript. If you already run MedGemma, you now have a local audio-capable sibling to compare against — no cloud.
[if you haven’t tried unsloth/gemma-4-E2B-it-GGUF yet, it is worth checking out. It is only 3gigs for UD-Q4_K_XL quant and it really flies in unsloth studio]
🎙️ From the Pods
🎙️ Latent Space — “Reality: The Final Eval” (Andon Labs)
The cofounders behind VendingBench make the case that the real test of an autonomous agent isn’t a clean benchmark — it’s giving it a wallet, inventory, and customers and watching what happens over weeks. What happens is unsettling: agents lie to suppliers, form price cartels, and spiral into “meltdown loops” (one Claude instance tried to report a $2/day fee to the FBI as cybercrime). (episode)
💡 Builder take: Before you let an agent touch a real clinical workflow, eval it on a long-horizon task with real consequences and a real exit — the failure modes only show up when the stakes and the time-window are real.
🎙️ HEALTH CARE un-covered — “No One Likes Medicare Advantage” (EP 4)
A roundtable with three legislators across the political spectrum — including a former GOP congressman who helped write the law that created modern MA — arguing the program has drifted into prior-auth denials, narrow networks, and upcoding. The signal: scrutiny of MA is now genuinely bipartisan. (video)
💡 Builder take: If the political winds on prior-auth and risk-adjustment are shifting, the durable build is the one that makes a plan’s documentation defensible, not the one that games the score — the headline risk just got bipartisan teeth.
💰 Money Plumbing
The CMS ACCESS Model: a brand-new $30 line a PCP can actually bill
CMS’s ACCESS Model goes live July 5, 2026 — a 10-year, outcome-aligned model in Original Medicare. The piece builders should care about: a new co-management payment of roughly $30 per service (up to once every four months per beneficiary per track), plus a ~$10 onboarding modifier the first time it’s billed, with no beneficiary cost-sharing.
That’s a CMS-blessed buyer with a decade-long runway — but the structure is the catch. The payment is legally for documented review and coordination, not for sending a patient anywhere.
A “$100 to refer” payment cannot legally exist — Stark Law and the Anti-Kickback Statute see to that. Money only moves as compensation for clinical work actually performed and documented. Build a routing-fee dressed as a referral bounty and you don’t have a product; you have a qui tam exhibit. (obviously this substack is not legal advice)
💡 Builder move: Build the documentation-and-review workflow that makes the co-management payment legitimately billable — the note, the review record, the coordination trail. The compliance structure isn’t overhead here; it is the product.
💡 BTW: Wendell Potter — co-host of that Medicare Advantage roundtable above — was once head of corporate communications at Cigna. What turned him into a whistleblower was wandering into a free Remote Area Medical clinic at the Wise County, Virginia fairgrounds in 2007 and seeing hundreds of uninsured people being treated in the open air and the livestock barns. He quit the next year. (Wikipedia)
What are you building this week? Email and tell me (kevin@clinicians.build) — I read every one.
— Kevin