<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Handover: the Clinicians That Code briefing</title>
    <link>https://cliniciansthatcode.com/briefing/</link>
    <atom:link href="https://cliniciansthatcode.com/feed.xml" rel="self" type="application/rss+xml" />
    <description>One email a week. Five minutes. What happened at the crossroads of medicine, code and regulation; no vendor marketing, no filler.</description>
    <language>en-GB</language>
    <lastBuildDate>Fri, 21 Aug 2026 08:00:00 GMT</lastBuildDate>
    <item>
      <title>The Handover, Issue 3</title>
      <link>https://cliniciansthatcode.com/briefing/issue-3/</link>
      <guid isPermaLink="true">https://cliniciansthatcode.com/briefing/issue-3/</guid>
      <pubDate>Fri, 21 Aug 2026 08:00:00 GMT</pubDate>
      <description>This week: the FDA asks how to examine a generative AI device, a nephrologist turns the week's papers into a podcast, and pharmacists and nurses fill the shipping log.

Top signal: The FDA opens the file on generative AI devices. A discussion paper from the FDA's Digital Health Center of Excellence (18 August) sets out how generative-AI-enabled medical devices might be regulated: risk assessment on two axes, premarket evaluation, postmarket monitoring, and considerations for foundation models and agentic systems. The idea to watch is a competency assessment &quot;inspired at a high level by how physicians are trained and evaluated&quot;: non-clinical benchmarking of clinical knowledge, analytical ability, safety behaviour and communication, then clinical confirmation with real patients and clinicians. Clinicians are explicitly invited to comment; docket FDA-2026-N-7874 is open until 19 October.

16 signals, 4 min read.</description>
    </item>
    <item>
      <title>The Handover, Issue 2</title>
      <link>https://cliniciansthatcode.com/briefing/issue-2/</link>
      <guid isPermaLink="true">https://cliniciansthatcode.com/briefing/issue-2/</guid>
      <pubDate>Fri, 14 Aug 2026 08:00:00 GMT</pubDate>
      <description>This week: the AI testing gap gets measured, clinician ships from emergency simulation to insulin titration, and six new names in the directory.

Top signal: Health systems are deploying AI faster than they can test it. A new UPMC Center for Connected Medicine and KLAS Research report finds 93% of health systems run third-party AI and 92% say they test tools before deployment, yet only 44% have a dedicated data platform or environment to actually do that testing in. The gap between claiming to test and being equipped to test is where clinician-builders earn their keep; the same week, Doximity placed over 150 physicians inside clinical AI product teams as its 2026-2027 Clinical AI Fellows.

28 signals, 4 min read.</description>
    </item>
    <item>
      <title>The Handover, Issue 1</title>
      <link>https://cliniciansthatcode.com/briefing/issue-1/</link>
      <guid isPermaLink="true">https://cliniciansthatcode.com/briefing/issue-1/</guid>
      <pubDate>Fri, 07 Aug 2026 08:00:00 GMT</pubDate>
      <description>This week: the UK regulator opens a sandbox, hackathon momentum keeps building, and eight clinician-shipped builds (three of them by nurses).

Top signal: The MHRA opens a regulatory sandbox for AI medical devices. The UK regulator is convening AI device makers, NHS organisations and regulatory experts to explore safe real-world deployment, and clinician-builders are eligible to apply as manufacturers. Read it as a sign of where things are heading: even the regulator now builds safe places to experiment. Expressions of interest are open.

22 signals, 3 min read.</description>
    </item>
  </channel>
</rss>
