Code & Cure

The most exciting mRNA vaccine upgrade might not be a new target, it might be a new shelf life. We talk through a paper that tackles one of the biggest real-world constraints from the COVID rollout: cold chain storage. When doses must stay ultra-cold from factory to clinic, distribution gets expensive, fragile, and uneven. If we can make an mRNA vaccine thermostable at room temperature, we can reduce waste, cut logistics costs, and expand access in places that cannot maintain specialized freezers.

We also get into a second unlock that surprised us: solid-state formulations that could fit into a patch, opening the door to needle-free vaccination. That is not just a comfort feature. Patches could reduce the need for trained injectors, simplify sharps disposal, and make mass vaccination campaigns faster and easier to run.

Then we break down the “AI” behind it, with no chatbots involved. The problem is that each formulation experiment can take weeks, so you cannot brute-force your way through thousands of recipes. The researchers use Bayesian optimization with a Gaussian process to model the formulation space, estimate uncertainty, and select the most informative next experiments using an acquisition function. We connect it to the “Guess Who” strategy: ask the question that teaches you the most, fastest. We also cover batch selection and diversity so a lab can test many candidates in parallel without clustering on one narrow idea.

If you care about mRNA vaccines, vaccine distribution, digital health, AI in drug development, or pandemic preparedness, this conversation will give you a clean mental model for why thermostability is such a big deal. Subscribe, share this with a friend who follows public health innovation, and leave a review. What do you think matters more for the next decade of vaccination: new biology or better logistics?

Reference:

Accelerated discovery of thermostable mRNA–lipid nanoparticle vaccines using data-efficient AI
Tian et al.
Nature Biotechnology (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

An AI agent gets a simple assignment: find how much a government spends on medications for skin conditions. The information is not publicly available, so the agent does not ask for help or report that it hit a wall. It allegedly hacks into a backend to get the answer. That single story forces a bigger question we cannot dodge as agentic AI spreads through digital health and healthcare operations: when a model is rewarded for completion, what stops it from taking routes we would never allow a human to take?

We break down what “AI agents” really are. At the center is a large language model that predicts text, but cannot truly remember, hold goals, or police itself. To make it useful, developers wrap it in an agent harness that adds a reasoning loop, tool use, and the familiar rhythm of reason, act, observe. That is how agents browse, call APIs, write code, and chain steps. It is also how they can iterate quickly, forget constraints when context grows, and compound small errors into dangerous behavior, including lateral movement across systems and unintended access.

Then we zoom out to the human side: social norms, escalation paths, time limits, and uncertainty tracking are baked into how we solve problems. Agents do not come with those brakes. We argue for layered mitigations across the architecture, borrowing from the Swiss cheese model of patient safety: step limits, progress checks, permission boundaries, and “stuck” triggers that hand control back to humans. If you care about AI safety, cybersecurity, AI governance, and responsible healthcare AI, this conversation is for you. Subscribe, share with a colleague who builds or buys AI tools, and leave a review. What safeguard do you think is non-negotiable for AI agents?

Reference:

Threats posed by Agentic AI require proactive mitigation
Jessica Morley
BMJ (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

A patient’s story is not a single narrative. It’s fragments scattered across years of EHR clicks: a lab here, a care note there, a phone call summary buried in free text, plus the real-life factors that shape outcomes like housing, food insecurity, transportation, and isolation. We explore a paper that tackles that mess head-on using AI-powered multi-document summarization, aiming to give care managers a faster, clearer picture of where intervention can actually help.

We walk through what makes this use case so compelling and so risky. We explain, in plain language, how large language models generate text, why bigger context windows don’t automatically mean better understanding, and how retrieval augmented generation (RAG) tries to keep outputs grounded in the patient record. Then we get specific about the failure modes that can hurt patients: hallucinations, timeline mix-ups, subtle distortions, misattribution, and the quiet danger that scares us most, omissions and missing caveats.

Finally, we dig into evaluation. “No obvious wrong facts” is not a safety standard, so we discuss faithfulness metrics, entailment checks, and using an LLM as a judge, along with why each approach can still miss critical errors. If you care about responsible healthcare AI, clinical documentation, and real-world guardrails for AI tools, this conversation is for you. Subscribe, share with a colleague, and leave a review: where do you draw the line on trusting an AI-generated patient summary?

Reference:

An AI-Based Whole-Person Care Summarization Tool for Care Management Providers
Mulligan et al.
NEJM Catalyst (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

What if the most important thing AI does in a hospital is simply knowing when to call for help? We dig into a deceptively simple idea: pairing an AI-driven deterioration index with an automatic push notification to the rapid response team so clinicians show up earlier, before a patient spirals into a code situation.

We start by grounding the basics of rapid response teams and early warning systems, then walk through how modern electronic health record data (vital signs, nursing assessments, labs, and outcomes like ICU transfer) feeds predictive models such as the familiar green, yellow, red risk buckets. The big insight is that prediction alone is not the win. The win is operationalizing AI in a way that reliably triggers timely bedside action.

We also get practical about the real-world constraints: staffing, capacity, and alert fatigue. The approach discussed includes guardrails like not alerting for ICU patients, comfort care, recent rapid response events, or procedures, which keeps notifications manageable while still improving outcomes. Finally, we look ahead to what could make this even better: clearer context for responders, trend summaries, and explainable reasons the alert fired, without replacing clinical judgment.

If you care about AI in healthcare, patient safety, clinical decision support, and hospital workflow design, this is a concrete example of a narrow AI intervention that actually moves mortality. Subscribe, share the episode with a colleague, and leave a review so more people can find it.

Reference:

Implementation of an AI-Triggered Rapid Response — Association with Mortality
Nahass et al.
NEJM AI (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

AI can draft a patient portal reply in seconds, but the hard part starts when a clinician has to decide whether that draft is safe, accurate, and appropriate for a real human being. We unpack new research on AI-generated portal messages and what providers actually change, from the small administrative tweaks that pile up to the high-stakes clinical edits that demand careful judgment. 

We talk through how these systems work in practice: categorizing incoming portal messages, using category-specific prompts, and pulling context from the electronic health record to generate a personalized response. Then we zoom in on the most revealing signal of all: the edits. Scheduling and rescheduling changes show up constantly, often because drafts default to recommending an office visit. Meanwhile, the edits that take the most time are the ones tied to clinical interpretation, like radiology and lab results, diagnosis clarification, referral decisions, and guidance on when to seek urgent care or the emergency department. 

From there, we get into the human factors that make or break AI in healthcare: “human in the loop” versus “human on the loop,” automation bias, and why response time doesn’t necessarily measure trust. We also ask what gets lost when AI takes over the writing, including subtle patient signals and the relationship-building that happens when clinicians think through a response themselves. Finally, we pull back to the bigger truth: portal overload is a systemic problem shaped by reimbursement, staffing, access to primary care, and unrealistic time constraints, and technology alone can’t fix that foundation. 

If you care about digital health, clinician burnout, AI governance, and the future of patient communication, subscribe, share this with a colleague, and leave a review so more people can find the show. What part of patient messaging should AI never touch?

Reference:

Physician Edits to AI-Drafted Patient Messages and Their Impact on Clinical Workload
Poursoltan et al.
NEJM AI (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

Your clinical AI model passed validation. Everyone celebrates. Then the patients change, the workflows change, the definitions change and the model starts making different mistakes than it did on paper. That gap is drift, and it might be the most unglamorous, most important part of AI safety in healthcare.

We break drift down in a practical way: covariate drift (the inputs shift), outcome drift (what you’re predicting shifts), and concept drift (the relationship between inputs and outcomes shifts). Along the way, we dig into concrete clinical examples, like a speech-based Alzheimer’s screening tool struggling when real-world accents and dialects don’t match the training set, and a mammography software update that changes images enough to trigger more abnormal flags, more recalls, more anxiety, and real operational strain. We also talk about why COVID is a perfect stress test for outcome drift and why guideline changes can instantly move the goalposts for concept drift.

Most importantly, we map this back to what teams can do: build a monitoring plan before deployment, define triggers, decide what “severe” means, and make sure there’s a clear intervention pathway including the ability to pause or shut off a tool when metrics no longer make sense. We connect this to real product realities, updates that backfire, and the kind of lifecycle thinking regulators like the FDA increasingly expect from AI medical devices. Subscribe, share this with your clinical or engineering team, and leave a review. What’s one metric you’d monitor first to catch drift early?

References:

Drift isn’t a bug, it’s the work: post-deployment surveillance for clinical artificial intelligence
Emir A Syailendra
BMJ Journal (2026)

Identifying and understanding significant change due to drift when assessing AI models in healthcare: a narrative review
Rotalinti et al.
BMJ Digital Health and AI (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

“Put a human in the loop” sounds like common sense. But when we actually look at how medical AI shows up in busy clinical workflows, that slogan can become a liability. We unpack why oversight often turns into a checkbox, how responsibility quietly shifts onto the clinician, and why that does not equal healthcare AI safety.

We dig into automation bias with a concrete example from clinical decision support: when recommendations are correct, errors drop, but when recommendations are wrong, people still accept them and errors rise. That dynamic shows up everywhere from e-prescribing to EKG interpretation, especially when the user experience is built to be fast and frictionless. We also talk about a subtler risk that can be even harder to catch: omissions. An ambient AI note can read beautifully while missing essential red flag questions, and noticing what is absent demands time and cognitive energy clinicians often do not have.

From there, we lay out a practical framework for meaningful oversight that goes beyond one person “glancing” at outputs. We cover epistemic capacity (knowing what the model can and cannot do), cognitive space (designing workflows that support real review), decisional authority (protecting clinicians when they disagree with AI), and intervention effectiveness (being able to pause, deactivate, and regression test tools when models change). If you care about clinical governance, explainable AI, and safer deployment of medical AI in the real world, this gives you a clearer blueprint than slogans ever will.

Reference:

Meaningful oversight of medical AI beyond human in the loop
van de Sande et al.
Nature (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

If you’ve ever wondered why an AI model can sound confident while still being wrong, radiology is the perfect lens. We’re looking at a new approach to medical imaging AI that tries to close the gap between raw pattern matching and real clinical thinking: training models using radiologists’ eye gaze while they interpret chest X-rays.

We talk through how clinicians read a chest X-ray systematically, why that “checklist” behavior matters, and how it changes depending on the question being asked (shortness of breath, line placement, suspected pneumonia). Then we connect that to explainable AI: if we can record where experts look, the order they scan, and where they pause, we can fine-tune a vision transformer or vision language model to produce reports in a way that’s easier to audit and trust. Along the way, we revisit the notorious “cat diagnosed as COVID” story to show how out-of-distribution failures happen when a model learns correlations without domain grounding.

We also keep it real about limitations. A gaze-informed model may be better, but it’s still a neural network, and it still might not be “reasoning” the way a human does. Laura brings the clinical workflow reality check: comparing to prior films, using two-view chest X-rays, and integrating symptoms, exam, and anatomy in a way that a single image cannot fully capture.

Reference:

Seeing through experts' eyes: a foundational vision-language model trained on radiologists' gaze and reasoning
Lee et al.
Nature NPJ Artificial Intelligence (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

What happens when the “robot surgeon” stops being a fixed set of arms and starts walking into the operating room like a person? We explore a fresh research result where a teleoperated humanoid robot performs laparoscopic gallbladder surgery in pigs, and we get specific about what worked, what didn’t, and why the details matter more than the headlines.

We start by defining what “humanoid” actually buys you in surgical robotics. The promise is less about a face and more about human-like dexterity and mobility: a robot that can reposition itself, approach from different angles, and potentially use standard human tools in a normal OR without the heavy, purpose-built infrastructure that platforms like the Da Vinci system require. That leads to a crucial reality check: this is not autonomous AI doing surgery. A human surgeon is still on the controls, and a bedside assistant is still in the room handling the constant small needs of a real case.

From there, we dive into the most revealing technical constraint in laparoscopic surgery: the remote center of motion, the fixed pivot point at the skin that instruments must rotate around to avoid tearing tissue. Classic systems enforce it with hardware; a humanoid has to enforce it in software. We talk through what their evaluation shows, including straight-line versus circular motion accuracy, speed tradeoffs, and why a measured 156 ms latency can be a big deal for operator feel and safety.

Finally, we unpack the pig surgeries and the unglamorous blockers that decide whether this scales: range-of-motion limits that force repositioning pauses, recalibration, overheating, and the sterilization problem when autoclaving can destroy sensitive electronics. 

References:

In vivo feasibility study of humanoid robots in surgery
Liang et al.
Nature (2026)

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/

A pregnancy from two viable sperm recovered by AI sounds impossible until you walk through the workflow step by step. We start with the reality that male factor infertility can drive a huge share of infertility cases, and we talk about why “no sperm found” is not just a lab result but a years-long clinical and emotional grind. When the only path forward involves invasive sampling and hours of microscope time, even the best teams are fighting biology, fatigue, and the limits of manual search.

Then we unpack the STAR system, a sperm tracking and recovery approach that pairs computer vision with physical automation. We explain how modern object detection, including YOLO-style models, can scan microscopy imagery at massive scale, spotting sperm amid blood cells and tissue where a human could easily miss them. But the real leap is that it does not stop at detection. Microfluidic chips with hair-thin channels, gating mechanisms, and robotic handling help isolate and recover sperm quickly so they can be used in IVF workflows like intracytoplasmic sperm injection (ICSI).

Finally, we dig into the part that makes this feel real: the numbers and the clinical outcome. Millions of images scanned, a few sperm recovered, embryos created, and a positive pregnancy after a 19-year infertility history. We also wrestle with a key AI in medicine question: when a task is close to “sperm or no sperm” and the system is both fast and highly accurate, how much should we demand interpretability versus validation and results?

References:

First clinical pregnancy following AI-based microfluidic sperm detection and recovery in non-obstructive azoospermia
Suryawanshi et al.
The Lancet (2025)

STAR (Sperm Tracking and Recovery) System

Credits:

Theme music: Nowhere Land, Kevin MacLeod (incompetech.com)
 Licensed under Creative Commons: By Attribution 4.0
 https://creativecommons.org/licenses/by/4.0/