Primary care declares independence 🗽, Two AI laws go live ⚖️, UpDoc's paperwork tells another story 🔍

He earned a PhD in AI, then went to med school on purpose. Was he early — or just paying attention?

On June 30, a Dallas company called Matic exited stealth with a “Declaration of Independence for Primary Care,” co-developed inside a real provider group (Catalyst Health Group) rather than pitched at one from the outside.

The founding pair is the tell. Calvin Carter spent 30 years making consumer software effortless — his shop built the Chick-fil-A, LEGO, Southwest, and NPR apps. His co-founder, Dr. Alex Sheppert, earned a PhD in AI and ran algorithmic options-trading systems, then deliberately went to medical school around 2020 because he wanted to be a physician before the AI wave arrived.

Here’s the part worth sitting with: Sheppert’s doctoral thesis was on stopping hallucinations through adversarial training — and that’s the whole product philosophy. Matic runs multiple models against each other (”Thunderdome”), turns every physician correction into a permanent training case, and frames the goal as “error prevention versus error correction.”

The bottleneck was never the model. It’s the clinician who knows when the common answer is the wrong one.

Their own worked failure makes the point: an early note wrote “start empagliflozin” — with no dose. A naive model guesses the statistically common answer because that’s what the internet says most. A clinician knows the dose, and knows this patient.

That’s the same nerve John Lee hit this week: medicine doesn’t have a stable ground truth. The map — consensus, codes, the most-common answer — is not the territory, which is this patient in front of you. Lee’s confession lands hard: he was trained to treat pain as the “fifth vital sign” and wrote opioid scripts from a map someone else drew. Betting on error prevention is really a bet that the map is unreliable and the clinician is the correction.

😤 “It’s a ten-week pilot with vendor numbers. ‘99.9% note accuracy’ is a marketing slide, not a study.” Fair, and you should hold them to it — durable accuracy and ROI need quarters, not weeks, and “physicians change one word per twenty notes” is a claim I’d want to audit myself. But notice what they optimized for: a candid, published failure mode and a self-correcting review loop, not a leaderboard. That’s the right thing to be measuring, even if the number isn’t proven yet.

😤 “A consumer-app guy and a resident are going to fix primary care?” Stranger things could happen I guess.

❓ What’s the smallest version of “error prevention over error correction” you could build on synthetic data this weekend — a checker that flags the confidently-common answer before a human signs it? I keep thinking the verification layer is a product category before it’s an EHR feature, but I can’t quite draw its edges yet.

💡 80/20: Steal the mechanism, not the marketing. The reusable idea is turning every human correction into a stored test case (bad input → wrong output → right output → why). Do it on 20 Synthea patients and one narrow task, and you have an eval harness that gets smarter every time someone fixes it.

---

📡 Builder’s Radar

Two AI laws quietly go live today — and both are about who’s still in the loop.

As of July 1, Indiana’s HB 1271 bars insurers from using AI as the sole basis to downcode a claim without a human reviewing the medical record — and bars providers from submitting AI-generated claims without human review.

Same day, Tennessee’s SB 1580 makes it a deceptive practice to market a chatbot as a qualified mental or behavioral health professional — with a private right of action and civil penalties per violation.

The regulatory pattern is consistent: the human review step is becoming the legally load-bearing part of your architecture, not a UX nicety.

😤 “Two states. Who cares.” The private right of action in Tennessee is the part that scales without waiting for the next legislature — it’s plaintiffs, not regulators, who enforce it.

💡 80/20: If you’re building anything patient-facing, write down the exact sentence a clinician says when they review the AI’s output — then make sure your product actually creates that record. “A human reviewed this” is now a compliance artifact you can be asked to produce.

---

UpDoc made headlines last week. This week, someone pulled the actual FDA file — and the paperwork tells a different story.

Dr. Sam Ashoo read the clearance documents for the “physician-grade agentic AI” everyone was buzzing about, and found three claims that don’t connect. The famous “81% vs 25%” trial tested a deterministic Amazon Alexa flowchart in 2021 — and appears nowhere in the FDA submission.

The FDA cleared it (K253281) by substantial equivalence to a 2018 insulin dose calculator, with the decision summary stating “no clinical testing was performed.” The change-control plan legally locks the dosing engine as deterministic — so the LLM layer that’s marketed as “agentic” is the one part never clinically validated.

“Cleared,” “clinically validated,” and “agentic” were three separate stories sold as one.

😤 “This is just a hater dunking on a startup that shipped.” No — the care gap is real, and they chose the FDA pathway instead of dodging it, which deserves credit. The critique is narrower and fairer: know what’s actually running in the commercial product versus what ran in the trial, because they’re not the same system.

🔮 My bet: within a year, “read the 510(k) decision summary, not the press release” becomes a standard diligence step — and at least one “agentic” clearance gets publicly re-litigated on exactly this gap.

---

Medicare launches a chronic-care model this week that turns “generate a note” into a payment requirement.

CMS’s ACCESS Model — a 10-year, outcomes-aligned program for tech-enabled chronic care (hypertension, diabetes, MSK, depression) — begins this week, pulling 150+ tech-enabled organizations into Original Medicare. Participants must use FHIR-based APIs to share clinical updates with the patient’s other providers.

The wedge: a lot of these entrants know how to monitor and generate data. They don’t know how to generate a note a PCP can review, co-sign, and get paid for in under two minutes.

There’s a real difference between a blood-pressure trend chart and a clinical update a physician can act on — and Medicare is now paying for the difference.

---

The other cost of your ambient scribe — the one nobody at the go-live could quote.

Dr. Gigi Magan convened a sharp conversation on what clinical AI costs before it reaches the exam room: energy, water, emissions — and who bears them. A health system rolled out an ambient scribe clinicians love, and no one could say how much energy a single encounter uses.

The usable part is a framework: SAHAI (Sustainably Advancing Health AI, NEJM Catalyst, from pediatrician-informaticist Dr. Chethan Sarabu and colleagues) — measure the energy/emissions/cost of a specific clinical use, like energy per AI-answered inbox message, and choose the lighter option.

😤 “This is guilt, not engineering.” It’s the same discipline you already preach: you cannot manage what you cannot count. “Use the model when you need reasoning; use a plain search when you need a link” is just cost-per-correct-task applied to watts instead of dollars.

---

⚡ Quick hits

Claude Sonnet 5 shipped — roughly Opus-4.7-class on coding and agents at the same price and speed as the last Sonnet, 1M-token context. If you route complex tasks to a pricier model for quality, re-run your evals — a same-price capability jump quietly resets a lot of routing decisions.

“Shift for healthcare” — a VC-lens read on the robotics-training-data gold rush argues privacy in a clinic is “10x harder and 100x riskier” than blurring faces in an apartment — “you can see that as a challenge, or as a moat.” 🔮 Bet: a dedicated healthcare data-pipeline company gets funded within three years.

---

🛠️ From the Workbench

fhirHydrant — an open-source FHIR MCP server (Node.js): SMART Backend Services auth, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, terminology lookup. In plain terms: it’s the interface layer that makes clinical data legible to an agent — the missing primitive between “I have a FHIR endpoint” and “my agent can safely read and write to it.”

It pairs with a thesis worth internalizing: agents win where software is open enough to give them context and API-first enough to let them act. That’s the whole reason MCP matters for clinical tooling.

⚠️ Verify: this is early, unaudited community infrastructure. It’s a superb thing to learn on with synthetic data / a public sandbox — but SMART Backend Services auth touching real PHI is a security-review conversation, not a weekend deploy.

💡 80/20: Stand it up against a public FHIR sandbox (Medplum is great) and point an agent at it. In an afternoon you’ll understand why “my tool integrates with the EHR” is a checkable claim, not a slogan — and you’ll have a repo to point your innovation team at.

---

🎙️ From the Pods

🎙️ The 229 / Unhack — “Wrangling Hidden AI Agents” (Drex DeFord + Jason Elrod, MultiCare)

The security angle nobody budgets for: shadow AI agents are already proliferating inside health systems, and the interesting defense is building your own counter-agent that feeds bad data to adversarial research bots. The pearl underneath, though, is a discipline: “Don’t delegate thinking. Cognitive atrophy will happen. Use it as a thought partner, not a replacement.”

💡 Builder take: The next governance category isn’t “which AI did we buy” — it’s “which agents are running that we didn’t deploy.” Build the inventory before you build the fifteenth tool.

🔇 Speaker Blindspot: Anecdotal generalization — a two-CISO conversation (”I built one, so everyone should”) is a vivid story, not evidence of what works at scale. The “everyone needs an agent” advice skips the org where an unmonitored agent is the breach.

🎙️ Radio Advisory — “The work isn’t easy, but it’s clear” (Rachel Woods + Advisory Board State of the Industry team)

The tonal shift worth noting: leaders moved from last year’s “plan for every scenario” paralysis to “we know the game plan now” execution. The word they kept hearing was resiliency — not optimism, but a refusal to treat failure as an option.

💡 Builder take: A buyer with clarity and urgency buys tools that help them execute a known plan — not tools that ask them to imagine a new future. Pitch the plan they already have, faster.

🔇 Speaker Blindspot: Survivorship bias — you interview the leaders and organizations still standing, and “resiliency” is exactly the story survivors tell. The systems that already folded under the same pressures aren’t in the sample.

---

What are you building this week? Email and tell me (kevin@clinicians.build) — we read every one.

— Kevin & AI