<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/c797186b5528470bace8afe2b3f8c46c&quot; frameborder=&quot;0&quot; width=&quot;1954&quot; height=&quot;1465&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1465</height><width>1954</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1465</thumbnail_height><thumbnail_width>1954</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c797186b5528470bace8afe2b3f8c46c-4d2e336310bd1477.gif</thumbnail_url><duration>447.519</duration><title>How I Use AI to Fact-Check My Own Clinical Reasoning (Real Patient Example)</title><description>In this video, I walk through how I&apos;ve been using generative AI tools like Doximity to stress-test my own clinical reasoning — not to replace my thinking, but to catch what I might be missing after I&apos;ve already done the work.

I share a real de-identified case: a 70-year-old male presenting with recurrent falls, a new progressive headache worse with straining, visual changes, and cognitive decline. I walk through my original assessment and plan, then show exactly what happens when I paste the full H&amp;P into Doximity using a structured attending-style prompt.

The AI flagged chronic subdural hematoma (even without a witnessed head strike) and giant cell arteritis — diagnoses I hadn&apos;t fully considered. I ended up ordering an ESR/CRP, which came back negative, but the process helped me close gaps in my reasoning before the patient&apos;s plan was finalized.

The key principle: reason first, let AI react second. These tools should be stress-testing your thinking, not doing it for you.

This video is a companion to my Inefficiency Insights article in Healthcare Huddle. Full breakdown linked below.

📩 Read the article here: [https://www.healthcarehuddle.com/p/how-physicians-can-use-ai-to-catch-what-they-miss]</description></oembed>