AI in Daily Medical Practice — Module 1 of 6
Handout — self-paced study material
How this module works. Take the short Preview Quiz first — it takes five minutes, isn't graded, and simply shows you what to pay attention to. Then read this handout (or use the accompanying slide deck, which covers the same material more visually) at your own pace, in one sitting or across several. Finish with the Post-Test, which is graded and checks whether the ideas actually stuck.
By the end of this module you will be able to:
Before any vocabulary, one distinction matters more than the rest of this module combined, because it decides whether everything that follows helps you or quietly makes you worse at your job.
A tool can be used two completely different ways. A physician can ask an AI system to generate a differential diagnosis and copy it into the chart without a second thought — that is cognitive outsourcing: the thinking has been handed over, not assisted. Or a physician can ask the same system to generate a differential, then interrogate it — what's missing, why did it rank this first, does it fit this specific patient — before deciding anything. That is cognitive augmentation: the tool extended the physician's reasoning without replacing it.
The technology is identical in both cases. The outcome is not. Every module in this curriculum, starting now, is built around one working rule:
Medicine has always required physicians to carry a large amount of knowledge in their own heads. That hasn't changed and won't change — a physician who has to look up the danger signs of aortic dissection while a patient is actively dissecting has already lost time that matters. What has changed is how much everything else needs to live in memory. This course sorts knowledge into three layers, and it's worth understanding the sort before you start memorizing anything.
Core vocabulary, core failure modes, and the judgment calls you need to make in real time, mid-encounter, with no time to look anything up. This module's vocabulary and failure-mode content falls here — not because it's the most important knowledge in medicine, but because you can't apply the rest of this course without it on hand.
Specific product names, version numbers, exact pricing, technical specifications. You don't need to memorize which company makes which tool — you need to know these categories of tools exist and know how to find current, local information when you're actually choosing one.
Judging whether a given tool fits a given situation, a given patient, a given clinic's constraints. This is the layer where most of this module's real value sits — the worksheet at the end of this handout is a THINK exercise, not a KNOW exercise.
Every section below is labeled so you know which layer you're in and how hard to work at retaining it.
You do not need to become a computer scientist. You need enough working vocabulary to read a product description, follow a conversation with an IT vendor, and know what question to ask when something goes wrong. Nine terms cover essentially everything you'll need for the rest of this course.
Notice what's not on this list: no neural network architecture, no discussion of parameters or model sizes, no coding. That detail sits in the FIND layer — a curious reader can go deeper, but nothing later in this course depends on it.
This is the section to read most carefully. Everything downstream in this curriculum — using AI for documentation, for diagnostic support, for anything — depends on you internalizing this before you touch a tool with a real patient.
An LLM generates text by predicting what word plausibly comes next, not by checking a database of verified facts. Most of the time, for common topics, this produces accurate output because accurate patterns dominate the training data. But the system has no built-in mechanism that distinguishes "I am certain" from "I am guessing" — both come out sounding equally confident.
AI output rarely hedges the way a cautious colleague would. A tool will often generate a single confident-sounding answer even when the underlying evidence is thin, conflicting, or simply outside what it was trained on. The danger is not that the tool is wrong — every diagnostic aid is sometimes wrong — it's that the tool's wrong answers look identical to its right ones.
Because these systems learn from training data, they inherit whatever imbalances exist in that data. A tool trained overwhelmingly on one population may under-perform, or fail in ways that are hard to predict, on patients from a different population — different demographics, different disease prevalence, different presentation patterns. This is covered in depth in Module 4; for now, simply know that "the tool works well" is a claim that depends heavily on whom it was validated against, and is never automatically true for your patients.
Every one of the failure modes above becomes most dangerous at exactly one moment: when the AI's answer happens to match what you already suspected. That is precisely when scrutiny drops, because the output feels like confirmation rather than a claim that needs checking. This single insight is the seed of Module 4, which is built entirely around training a habit of extra vigilance at that exact moment.
You don't need to memorize product names or pricing — that information changes constantly and belongs in the FIND layer. What's worth carrying in your head is the shape of the landscape: the four broad categories almost every clinical AI tool falls into.
| Category | What it does | Where it appears in this course |
|---|---|---|
| Ambient documentation / scribing | Listens to or transcribes a clinical encounter and drafts a structured note automatically. | Module 2 |
| Diagnostic / clinical decision support | Suggests differentials, flags abnormal findings in imaging or labs, estimates risk scores. | Module 3 |
| Patient-facing tools | Symptom checkers, chatbots, and consumer apps patients use themselves and bring into the consultation. | Module 3 |
| Administrative / operational | Scheduling, billing support, referral triage, inventory and supply-chain tools. | Referenced in Module 6 |
A practical habit worth building now: whenever you encounter a new AI product, the first question is simply "which of these four is this?" — it tells you immediately what kind of scrutiny it needs and which later module's skills apply to it.
This is a self-directed reflection, not reading. There is no live seminar for this section anymore — you work through it on your own, and it's worth doing with an actual pen or a saved document, because you'll draw on your answers again in Module 6 when you build your implementation plan.
1. Which of the four tool categories from Section C is most relevant to your day-to-day work right now — and why that one first?
2. What is your actual internet connectivity like where you practice, at the times you'd realistically use an AI tool? Would a tool that requires constant connectivity work for you, or do you need something that tolerates offline or low-bandwidth use?
3. What languages do your patient encounters happen in, and what languages does the tool you're considering actually need to handle well — your notes, your patients' own words, or both?
4. What would this tool realistically cost — subscription, hardware, data plan — against what your practice or institution can actually sustain, not just afford once?
5. Where was this tool validated, as far as you can tell? Does anything suggest it was tested on a population that resembles — or doesn't resemble — the patients you see?
You are not expected to have confident answers to all five yet — Modules 2, 3, and 5 will give you more to work with. The goal here is simply to start the habit of asking these questions before adopting anything, rather than after.
| Layer | What this module put there |
|---|---|
| KNOW | Nine core terms (AI, ML, LLM, generative AI, multimodal AI, training data, prompt, inference, hallucination) and the three failure modes: hallucination, overconfidence, bias — with confirmation bias flagged as the most personally dangerous of the three. |
| FIND | The four categories of clinical AI tools, and where to look for current product-specific detail when you actually need it. |
| THINK | A first pass at judging tool fit for your own practice — connectivity, language, cost, and validation population — to be revisited and sharpened in later modules. |