FDA clears first sepsis AI 🏥, The note was right but the order didn't fire 🔇, Pods
FDA Clears First-Ever Continuous AI Sepsis Monitor — But There’s No Code to Bill for It
Bayesian Health received 510(k) clearance for the first continuous AI sepsis monitoring system. The tool, developed at Johns Hopkins, integrates with the EHR to flag sepsis up to 48 hours before a clinician suspects it. In a study of 764,000 patient encounters across five hospitals, patients were 18% less likely to die when clinicians acted on the alerts.
This is a landmark for clinical AI validation. It’s also the canonical “no CPT code” problem. Sepsis is bundled into MS-DRG 871/872/873. The hospital captures the cost-avoidance value (shorter stays, fewer ICU days). The AI vendor captures whatever the hospital is willing to pay — because there’s no billing code for “AI detected sepsis earlier.”
😤 “If the tool saves lives, the market will figure out payment.” The market has been “figuring out” CDS reimbursement for a decade. Meanwhile, Bayesian’s best near-term path is CMS’s New Technology Add-on Payment (NTAP) program, with a decision expected August 2026.
😤 “Hospital-value-capture without vendor-revenue-capture is unstable.” Correct. And that instability is every clinical AI vendor’s problem until CMS creates new codes or the NTAP path proves scalable.
“The Note Was Right. The Order Didn’t Fire.”
Doug Fullington’s analysis of a Stanford benchmark (arXiv:2605.02240) names the gap hiding inside every clinical AI demo: the AI generates a clinically accurate note, but the corresponding EHR order doesn’t execute.
This isn’t an AI accuracy problem. It’s a workflow integration problem. And it means the current evaluation paradigm — benchmarking AI on note quality — systematically overstates real-world clinical impact.
😤 “Sounds like an EHR vendor problem, not an AI problem.” It’s both. The AI companies building outside the EHR and throwing notes over the wall will keep hitting this. The ones building inside the order-entry workflow won’t.
The Hardest Clinical Skill Is Deciding Not to Act
Graham Walker (MDCalc, Offcall) posted a follow-up to his “friction is the design” piece. The core insight: the unique move an ER physician makes ~50 times a shift is deciding not to act. Don’t make the diagnosis yet. Don’t send them home. Hold.
AI agents are built to close their loop. They’re never built to refuse to complete.
The hardest ER cases aren’t computation-hard. They’re data-wrong. A confident wrong answer is worse than a deliberate pause.
😤 “So AI can’t handle uncertainty — we knew that.” Knowing it and building for it are different things. Name an AI clinical tool that has a “pause — something’s off” button with the same UI weight as the “confirm and close” button. I’ll wait.
Evidently Lands UNC Health Enterprise Deployment
UNC Health selected Evidently as its clinical data intelligence partner across Triangle-region hospitals and clinics. The deployment spans the full care team — physicians, APPs, CDI, nurses, pharmacists, social workers, case managers. Pilot results: specialists saving ~40 minutes a day on chart review.
⚠️ Verify: “Enterprise deployment” after a 12-week, 100-user pilot is promising but early. Track outcomes at the 6-month mark before treating this as a validated playbook.
MedStar’s Raj Ratwani Launches Consortium for Safe AI in Healthcare
Raj Ratwani (VP Scientific Affairs, MedStar Health Research Institute) and the Mid-Atlantic Patient Safety Center are establishing a Consortium for Safe Artificial Intelligence in Healthcare, wrapped into a Patient Safety Organization. Kickoff session: June 9, 2026, 12-1 PM, virtual. Open to AI developers and patient safety leaders.
This is clinical AI safety governance getting institutional scaffolding. PSO designation means legal protections for reported safety events — which matters enormously for getting hospitals to actually report AI failures instead of burying them.
Microsoft Spending $190B on AI Infra — Still Expects Capacity Shortages
Microsoft is pouring $190 billion into AI infrastructure and still projecting capacity constraints. If you’re a clinician-builder relying on Azure, AWS, or GCP for inference at scale, the capacity-crunch risk is real.
🎙️ From the Pods
🎙️ HIMSSCast — “Scaling a Profitable Company with Little Venture Funding”
WISP CEO Monica Sepak built the largest women’s telehealth platform in the US — 2 million patients across all 50 states — on less than $2 million in primary capital. While competitors raised hundreds of millions, WISP stayed profitable by optimizing bottom-of-funnel first, leaning into organic TikTok content, and launching new products within weeks of clinical evidence (BV male partner therapy in 3 weeks).
💡 Builder take: The capital-efficient playbook works in health tech. Start with the $0 marketing channels (organic content, community), optimize conversion before spending on brand, and ship new features fast enough that your speed IS your moat.
🎙️ Turn on the Lights — “Building Intelligent Health Around the Whole Person” with Dr. Nassim Afsar
Don Berwick and Nassim Afsar (former Chief Health Officer, Oracle/Cerner) discuss the gap between EHR promise and clinical reality. Afsar’s observation hit hard: in a privileged population with great insurance and frequent doctor visits, diabetes control still didn’t improve — because diabetes kept getting bumped from the visit agenda by more urgent issues. The variation problem isn’t access. It’s workflow.
What are you building this week? Reply and tell me — I read every one.
— Kevin