Objective: Train the two-way link between basic science and clinical diagnosis explicitly — diagnosis → mechanism, and mechanism → diagnosis list — rather than leaving the connection to form implicitly over years of clinical exposure.
Indication: Any point in training where a learner can state a diagnosis but not its mechanism, or can recite a mechanism but cannot generate the clinical presentations that follow from it. Particularly useful directly after Module 15, since an illness script’s “fault” component is the basic science — this module drills that single component in isolation, in both directions, before it gets folded back into full scripts.
[!NOTE] Theoretical Basis: This module operationalises vertical integration in medical education — the deliberate interweaving of basic and clinical sciences throughout training, rather than the traditional two-stage model of basic science first, clinical application later (Brauer & Ferguson, 2015, “The Integrated Curriculum in Medical Education,” AMEE Guide 96, Medical Teacher, 37(4), 312–322). The specific mechanism this module targets is encapsulated knowledge (Schmidt, Norman & Boshuizen, 1990) — the empirical finding that as clinicians gain experience, detailed basic-science knowledge becomes compiled (“encapsulated”) into higher-level clinical concepts and illness scripts, so that it is used fluently without being consciously recalled. The risk this module is designed to counter is premature encapsulation — a learner who has memorised the clinical pattern without ever having built the underlying mechanistic link, leaving a script that looks compiled but has no mechanistic foundation to fall back on when a case doesn’t fit the pattern (see Module 15, Step 15.4). Bidirectional drilling — diagnosis-to-mechanism and mechanism-to-diagnosis — is specifically what distinguishes genuine integration from one-directional memorisation; a learner who can only go one direction has not actually integrated the two domains.
Phase 1 · Initiation → Phase 2 · Execution → Phase 3 · Closure / Review
Prompt:
#VibeRounds You are a clinical reasoning partner helping me build explicit
two-way links between basic science and clinical diagnosis. There are two
directions we will work in, and you must tell me clearly which one we are
doing before each exchange: (A) Diagnosis → Mechanism: I name or you give
me a diagnosis, and I have to explain the underlying basic science —
physiology, pathology, pharmacology, microbiology, or anatomy as relevant
— in my own words before you confirm or correct. (B) Mechanism →
Diagnosis: you give me an isolated basic science mechanism with no
diagnosis named, and I have to generate the list of diagnoses or
presentations that follow from it, before you tell me what I missed. In
both directions, make me commit to an answer first — do not explain the
mechanism or list the diagnoses for me until I have made a genuine
attempt. Confirm you understand both directions before we begin.
[!NOTE] Application Note: Run once per integration session. The explicit “tell me which direction” instruction matters because most LLMs default to direction A (explaining mechanism after being given a diagnosis) since it is the more common pattern in medical text generally — direction B has to be forced or it will rarely occur on its own.
Prompt:
#VibeRounds Give me a diagnosis. Before you say anything else, ask me to
explain the core basic-science mechanism that produces it — in my own
words, at the level of physiology or pathology, not just naming the
process. Only after I attempt it, tell me what was accurate, what was
incomplete, and what I should add. Then ask one follow-up: which specific
clinical finding in this condition is most directly explained by the
mechanism I just described — the one finding a clinician could not predict
without knowing the mechanism?
[!NOTE] Application Note: The follow-up question is the integration test, not the mechanism explanation itself. A learner can often state a mechanism and a finding as two separate memorised facts without ever connecting them — asking them to name which finding the mechanism predicts forces the link to be made explicit rather than assumed.
Prompt:
#VibeRounds Give me an isolated basic-science mechanism — a physiological
derangement, a pathological process, a pharmacological action, or a
microbiological behaviour — with no diagnosis named. Ask me to generate as
many diagnoses or clinical presentations as I can that would follow from
this mechanism. Do not give me the diagnosis list yourself until I have
generated my own. Once I have, tell me which ones I got, which common ones
I missed, and whether I included anything that does not actually follow
from this mechanism — a false positive is as informative as a missed
diagnosis here.
[!NOTE] Application Note: This is the direction most curricula under-train (see vertical-integration literature — most “integration” in practice still runs basic-science-to-clinical, rarely the reverse). It is also the more clinically realistic direction in one specific sense: a clinician who finds an abnormal lab value or imaging finding mid-workup is often reasoning from mechanism toward diagnosis, not the other way round. Flagging false positives (mechanisms the learner over-generalised from) is as important as flagging missed diagnoses.
Prompt:
#VibeRounds Give me a basic-science mechanism that underlies two or more
different diagnoses — for example a shared pathophysiological pathway with
different triggers, or a shared drug mechanism with different clinical
uses or toxicities. Ask me to name all the diagnoses or presentations that
share this mechanism, and then ask: what is the one upstream or downstream
difference that explains why these conditions present differently despite
sharing the core mechanism?
[!NOTE] Application Note: This step trains the discrimination skill from Module 15, Step 15.3 but at the mechanism level rather than the script level — useful for conditions that are frequently confused precisely because they share an underlying pathway (e.g. conditions sharing a final common inflammatory or ischaemic pathway with different upstream triggers).
Prompt:
#VibeRounds Give me a diagnosis that can arise through more than one
distinct basic-science mechanism or pathway — for example a single
clinical syndrome with several different underlying causes that converge
on the same presentation. Ask me to name as many distinct mechanistic
routes to this diagnosis as I can. Then ask: if I only had time to
investigate one route first, which would I prioritise, and why — based on
prevalence, reversibility, or danger if missed, not just listing them in
no particular order.
[!NOTE] Application Note: This is the mirror image of Step 16.3 and closes a common integration gap — learners often know one mechanistic route to a diagnosis well (the one taught first) and treat it as the only route, missing that the same clinical syndrome can converge from genuinely different pathophysiology requiring different work-ups.
Prompt:
#VibeRounds Give me a drug class and only its core mechanism of action —
no indications, no side effects yet. Ask me to derive, from the mechanism
alone: (1) what conditions this drug class should treat, (2) what adverse
effects or toxicities are predictable from the same mechanism, and (3) what
drug-drug or drug-disease interactions would follow logically from this
mechanism. Only after I attempt all three, tell me what I derived
correctly and what required information beyond the mechanism that I
couldn't reasonably have predicted.
[!NOTE] Application Note: Pharmacology is the basic-science domain where the mechanism-to-clinical-effect link is most directly derivable by reasoning rather than requiring memorisation — this step exploits that to build the habit of deriving rather than recalling. Naming what genuinely couldn’t be predicted from mechanism alone (idiosyncratic reactions, population-specific effects) is as important as the derivation itself — it teaches the boundary of what basic science can and can’t predict.
Prompt:
#VibeRounds Pause. Give me a formative checkpoint: (1) diagnosis-to-mechanism
direction — score out of 10, with one specific strength and one targeted
gap; (2) mechanism-to-diagnosis direction — score out of 10, same format.
Tell me explicitly if one direction is notably weaker than the other — that
asymmetry is itself the most useful finding from this checkpoint, more
useful than either score alone.
[!NOTE] Application Note: The asymmetry between the two directions is the actual diagnostic signal this module is built to surface — a large gap between forward and reverse performance indicates memorised, non-integrated knowledge even when the forward direction looks strong on its own.
Prompt:
#VibeRounds Based on everything we covered this session, build a compact
two-way map: list each diagnosis we discussed, its core mechanism in one
line, and at least one other diagnosis it connects to either through a
shared mechanism or a shared clinical presentation. Format it so I could
redraw it from memory as a simple node-and-link sketch.
[!NOTE] Application Note: Concept mapping is a validated technique specifically for making basic-science/clinical links explicit and shareable (see vertical-integration literature on concept maps as an integration tool). The instruction to make it redrawable from memory — rather than just presented as a reference table — is deliberate; the consolidation value comes from the learner being able to reconstruct the links, not from having a copy of them.
Prompt:
#VibeRounds Apply a critical awareness lens to the integration work we did
today: (1) For any diagnosis where I could state the clinical picture but
struggled with the mechanism, what is the risk of relying on that
diagnosis pattern-matched rather than mechanistically understood — where
might it fail me on an atypical case? (2) For any mechanism where I could
explain the science but missed an obvious diagnosis it should have
predicted, what does that gap suggest about how I've been studying basic
science — as connected knowledge or as an isolated subject? (3) What is
one diagnosis-mechanism pair from today I am at risk of forgetting within
a month, and what would re-test it most efficiently?
[!NOTE] Application Note: This step extends Framework D’s critical-awareness lens to a risk specific to this module: clinically fluent but mechanistically hollow knowledge, which is exactly the failure mode that genuine vertical integration is designed to prevent and that premature encapsulation (see module-level Theoretical Basis note above) can mask.
Previous: ← Module 15 — Illness Script Acquisition
This is currently the final module. Up next: browse the Supplementary Frameworks or Reference Material.