Objective: Train reasoning across the body’s interconnected physiological systems — recognising how a failure, adaptation, or intervention in one system propagates through others, and how a complete clinical picture requires assembling cross-system interactions rather than analysing each organ in isolation.
Indication: Reach for this module when a case involves multi-organ involvement, when a patient is deteriorating despite apparent management of the index organ, when polypharmacy effects span multiple systems, or when a learner can reason fluently within a single system but struggles to trace how a pathological process crosses system boundaries to produce the full clinical presentation.
[!NOTE] Theoretical Basis: This module operationalises systems-based clinical reasoning — the cognitive capacity to hold multiple physiological systems in view simultaneously and reason about their interactions. It draws on the foundational work of Cannon’s homeostatic feedback model, the integrative physiology tradition of Guyton & Hall, and contemporary systems medicine frameworks that model disease as a dysregulation of interconnected networks rather than a failure of a single component. The core skill trained here is cross-system transfer: recognising that a haemodynamic event has renal consequences, that a renal consequence has electrolyte consequences, that an electrolyte disturbance has cardiac consequences — and that each link in this chain is both causally structured (not merely correlated) and clinically actionable. This module sits downstream of Module 16 — Bidirectional Basic Science ↔ Clinical Integration (which trains single mechanism-to-diagnosis links) and Module 18 — Causal vs. Probabilistic Network Reasoning (which trains how findings within a single diagnostic frame interact). This module extends both: it demands that the learner trace causal chains across organ systems, not just within them.
Phase 1 · Initiation → Phase 2 · Execution → Phase 3 · Closure / Review
Prompt:
#VibeRounds You are a clinical reasoning partner helping me practise
systems-based analysis — the ability to trace how a pathological process
in one organ system propagates through, compensates in, or disrupts other
systems. For every case we work through, present the index problem
(the primary organ system involved) first. Then reveal cross-system
consequences one step at a time, and ask me to predict the next system
affected before you confirm it. When I name a cross-system consequence,
ask me to state the actual mechanistic link — the physiological bridge
that carries the disturbance from system A to system B — not just the
clinical finding in system B. Do not let me describe a downstream finding
without naming the upstream cause. Confirm you understand this contract
before we begin.
[!NOTE] Application Note: Run once per session before any case is introduced. The “mechanistic bridge” requirement is load-bearing — it is the feature that separates this module from a simple multi-organ case presentation. A learner who can list cross-system findings without articulating the mechanism connecting them has not trained systems-based reasoning; they have trained a differential-diagnosis list.
Prompt:
#VibeRounds Give me a clinical scenario that begins in one organ system
and has established downstream consequences in at least two others.
Reveal only the index system finding first. Ask me to predict: (1) which
system is most directly disrupted next, and (2) by what mechanism.
After my answer, reveal one step of the cascade and repeat the prediction
cycle. Do not reveal more than one step ahead at any point. After the
final step, ask me to reconstruct the entire cascade — index system to
final downstream consequence — in my own words, mechanistic link by
mechanistic link.
[!NOTE] Application Note: The step-by-step reveal forces prospective prediction rather than retrospective explanation, which are cognitively different skills. Most learners can explain a cascade shown to them; fewer can accurately predict the next step before it is revealed. This drill exposes the boundaries of genuine physiological understanding.
Prompt:
#VibeRounds Give me a case where one organ system has mounted a
compensatory response to a primary failure in another system. Present the
compensatory findings (vital signs, lab values, clinical signs) without
telling me which findings are compensatory and which are part of the
primary pathology. Ask me to classify each finding into one of three
categories: (1) primary pathology — directly from the failing system;
(2) appropriate compensation — physiologically expected and currently
protective; (3) failed or exhausted compensation — a response that has
become pathological in its own right or has reached its ceiling.
After I classify, challenge any misclassification and explain the
physiological status of the disputed finding.
[!NOTE] Application Note: The three-way classification — primary, compensatory, decompensated — is clinically significant because interventions can differ sharply depending on the category. Treating an appropriate compensation as primary pathology (e.g., suppressing a tachycardia that is maintaining cardiac output in a hypovolaemic patient) is a recognised and avoidable error that this step directly targets.
Prompt:
#VibeRounds Present a treatment decision made for the index system in a
complex case — drug, fluid, procedure, or ventilator setting. Then ask
me to audit that treatment for its cross-system effects across each major
physiological domain: cardiovascular, renal, respiratory, neurological,
hepatic, electrolyte/metabolic, and haematological. For each domain,
I should state whether the treatment's effect is (a) beneficial, (b)
neutral or negligible, (c) a clinically significant adverse interaction,
or (d) uncertain in this patient's context, with a one-sentence
mechanistic explanation for each non-neutral call. After my audit,
identify any cross-system effect I missed that has immediate clinical
management implications.
[!NOTE] Application Note: This step is the systems-based complement to Module 13 — Medication Reconciliation & Polypharmacy Audit. Module 13 drills drug-drug interactions within a pharmacological frame; this step drills the physiological cross-system consequences of a single therapeutic decision across organ systems — a distinct and frequently under-rehearsed skill, particularly for procedural or ventilatory interventions that have no pharmacological interaction to flag.
Prompt:
#VibeRounds Give me a case that is being managed with a clear focus on
two organ systems. Then identify for me a third system that is silently
affected — one whose involvement is clinically significant but is not yet
producing symptoms, has not yet been investigated, and has not appeared
in the management plan. Do not name the silent system. Ask me to identify
it by reasoning from the pathophysiology of the two active systems
outward. After I answer, whether correct or not, ask me: what is the
first investigation I would order to assess that silent system, and at
what point in the illness trajectory does its involvement typically
become clinically overt?
[!NOTE] Application Note: The “silent organ” concept targets anticipatory reasoning — identifying a system that has not yet declared itself clinically but will, given the trajectory of the primary pathology. This is distinct from differential diagnosis (asking what the condition is) and is instead a prognostic, preventive skill: seeing the next system failure before it arrives.
Prompt:
#VibeRounds Present a case where it is genuinely ambiguous whether a
clinical finding belongs primarily to System A or System B — where the
same finding could reasonably be attributed to either system's dysfunction,
and the mechanistic argument can run in both directions. Ask me to argue
the case for System A first, then for System B. Then ask me: does it
actually matter for management which attribution is correct? If yes, what
single investigation would best arbitrate between the two? If no, explain
why the mechanistic ambiguity is clinically irrelevant in this case.
[!NOTE] Application Note: This step trains tolerance of ambiguity at systems boundaries — a real feature of clinical medicine that single-system reasoning frameworks cannot handle. Cardiorenal syndrome, hepatopulmonary syndrome, and neurocardiac injury are canonical examples where the boundary dispute is not merely academic; it determines monitoring priorities, investigation sequencing, and specialist involvement.
Prompt:
#VibeRounds Based on a case I describe, help me build a systems-based
problem list rather than a symptom-based or diagnosis-based list. Group
every active clinical issue under the physiological system that is its
primary driver. For each system, identify: (1) the primary problem in
that system; (2) whether it is the driver of problems in other systems,
a downstream consequence of another system's failure, or bidirectionally
linked; (3) the one management priority for that system that, if addressed,
would most benefit the other linked systems. After I build the list, ask
me: which system, if we improve it by 30%, produces the greatest
downstream benefit across the rest of the network?
[!NOTE] Application Note: The “30% improvement” question is a deliberate forcing function — it requires the learner to prioritise systems not by severity within that system but by leverage across the whole network, which is a qualitatively different clinical skill from routine problem-list construction. The concept maps onto real therapeutic decisions in, for example, the sequencing of interventions in cardiorenal-hepatic failure, where treating the system with the greatest network leverage — not necessarily the most obviously disordered system — often produces the fastest global improvement.
Prompt:
#VibeRounds Pause. Give me a structured formative checkpoint on my
systems-based reasoning in this session across four dimensions:
(1) Cascade accuracy — did I correctly predict cross-system consequences,
or did I miss steps in the propagation chain? Score out of 10 with
one specific strength and one targeted gap.
(2) Mechanistic articulation — did I provide genuine mechanistic bridges
between systems, or did I describe associations without mechanism?
Score out of 10, same format.
(3) Compensatory vs. pathological discrimination — did I correctly
categorise findings as primary, compensatory, or decompensated?
Score out of 10.
(4) Anticipatory reasoning — did I identify silent or emerging system
involvement before it was made explicit? Score out of 10.
End with one sentence identifying which of the four dimensions is my
current ceiling in systems-based reasoning.
[!NOTE] Application Note: The four dimensions correspond to the four distinct cognitive demands of this module — propagation tracing, mechanistic articulation, physiological categorisation, and anticipation — and can decompensate independently. A learner may be strong on cascade accuracy while systematically failing at mechanistic articulation; the checkpoint is designed to surface that asymmetry so remediation can be targeted.
Prompt:
#VibeRounds Looking back at this session, identify any moment where I
reasoned about a clinical finding as if it belonged to a single system in
isolation — a moment where single-system thinking produced a different
and less complete conclusion than cross-system analysis would have. Name:
(1) the specific finding I treated in isolation; (2) which other system or
systems it was actually coupled to; (3) what I missed as a result; and
(4) whether the missed cross-system consequence was clinically
consequential (would have changed management or monitoring) or was
academically interesting but practically irrelevant in this case.
[!NOTE] Application Note: Step XX.8 is the reductionism analogue of Module 18, Step 18.7 (Network vs. Linear reasoning debrief). Both steps audit the mode of reasoning used rather than just the conclusion reached, because identifying the mode of error — reductionism, in this case — is more transferable than identifying the specific mistake made in a specific case.
Prompt:
#VibeRounds Apply a critical awareness lens to systems-based clinical
reasoning specifically:
(1) Complexity risk — at what point does cross-system thinking become
so elaborate that it delays a time-sensitive management decision that
a focused single-system response would have made correctly and quickly?
Give a clinical scenario where systems-level analysis is actually the
wrong tool.
(2) AI-specific risk — when using an AI reasoning partner for cross-system
analysis, what is the specific failure mode that systems complexity
introduces that is not present in single-system queries? How would
you detect it?
(3) Safeguard — what is the single most reliable cognitive habit that
prevents a well-constructed systems narrative from shielding a
fundamental diagnostic error from scrutiny?
Be honest about the limits. The goal is calibrated use of systems
reasoning, not uncritical adoption of it.
[!NOTE] Application Note: This step applies Framework D — Critical Awareness Framework to the specific risks of systems-level thinking: that a plausible and internally coherent cross-system narrative can feel more rigorous than it actually is, obscuring a wrong index diagnosis beneath an elaborate and convincing downstream analysis. The AI-specific risk question (point 2) targets a failure mode particular to AI-assisted reasoning, where a language model’s tendency to generate fluent, internally consistent cross-system chains can lend false confidence to a cascade built on a flawed premise.
🟡 In Progress — Prompts drafted and structured; not yet tested against live de-identified cases. Sequence logic reviewed against Modules 16, 18, 31, and 38 for coverage gaps and overlaps. Maturity target: 🟢 Mature pending at least one documented live session with debrief.
This module sits most naturally between Module 18 (Causal vs. Probabilistic Network Reasoning) and Module 19 (Community & Social Medicine Insights) in the module index, as it builds directly on Module 18’s within-case network reasoning and extends it to the inter-system physiological level — the logical next layer of complexity before the framing shifts outward to community and social determinants in Module 19.
Alternatively, if the index is reorganised by the thematic cluster Clinical Reasoning & Cognitive Frameworks (Modules 1, 12, 14, 15, 17, 18, 20, 28, 30, 32, 33, 35, 36, 37), this module belongs in that cluster, positioned after Module 18 and before Module 20.
Previous: ← Module 18 — Causal vs. Probabilistic (Network) Reasoning
Next: Module 19 — Community & Social Medicine Insights →
Vibe Rounds Prompt Modules — Module XX · Systems-Based Clinical Analysis & Insights. Coined and developed within the VibeRounds framework by Dr. Avinash Kumar Gupta · Vibe Rounds, June 2026 #VibeRounds — A Socratic AI Paradigm for Clinical Medicine
[!IMPORTANT] Clinical Disclaimer & Independent Verification Required All AI-generated outputs produced using these prompts — including but not limited to cross-system cascade predictions, compensatory-vs-pathological classifications, therapeutic interaction audits, and systems-level problem lists — require independent clinical verification before being acted upon. This module does not substitute for clinical judgment, professional medical advice, or established institutional safety protocols at any stage.