The Avinash Principle: From Trajectory Analysis to Trajectory Prediction and Control

Why Predicting a Patient's Course Is Different from Predicting a Weather Pattern

Most attempts to formalize clinical reasoning fall into the same trap: they try to model a patient as a giant decision tree, with every vital sign, lab value, and biological reaction branching into millions of possible futures. This is the "combinatorial explosion" problem, and it is why naive predictive models scale so poorly at the bedside.

The Avinash Principle offers a different starting point. Instead of asking "what are all the paths this patient could take?", it asks "which two or three variables actually determine where this patient ends up?" These are the hub nodes — the critical leverage points (an airway, a clotting cascade, a systemic vascular resistance) that, once stabilized, allow everything else in the system to self-organize around a safe baseline.

Clinical guidelines, on this view, are not just checklists. They are mechanisms of algorithmic collapse — they delete decision points that don't need to exist, pruning hundreds of millions of theoretical trajectories down to a few dozen realistic ones. Expert clinicians succeed not because they compute further ahead than novices, but because their cognition works as a pruning engine, discarding the 99% of the decision tree that doesn't matter and focusing entirely on the 1% that does.

This also explains why the highest-leverage node isn't always biological. In chronic disease trajectories, the true hub node might be biographical — a sleep disruption pattern, a family stressor, a single lifestyle habit — rather than a lab value.

Turning the Principle into a Predictive, Monitoring Engine

Reframing hub nodes as leverage points is useful for understanding expert reasoning after the fact. The more interesting question is whether the same principle can run forward — as an active engine that watches a patient's trajectory unfold in real time and suggests where to intervene.

This requires shifting from sequential forecasting ("given X₁...X₅₀ at time t, predict their values at t+1") to a dynamical systems control framing, where the patient is treated as a state vector moving across a phase-space landscape shaped by stable and unstable attractors.

1. Prediction through Hub-State Attractor Modeling Rather than forecasting every variable, the engine tracks only the hub nodes — the handful of variables whose movement actually determines the trajectory's fate. It also watches for critical slowing down, the well-documented phenomenon where complex systems show increasing variance and micro-fluctuations in a hub node just before a tipping point. This gives an early warning of an approaching phase shift, often well before any overt clinical crisis appears.

2. Monitoring through Attractor Mapping As real-time telemetry — vitals, labs, clinical markers — streams in, the engine computes the patient's current state vector and calculates which attractor basin is exerting the strongest pull on it. Three basins matter most:

• Collapse — the critical, unstable zone on one side
• Goldilocks Zone — the homeostatic corridor where the patient's own feedback loops and routine care can maintain stability without emergency intervention
• Overtreatment / Toxicity — the unstable zone on the other side, created by excessive intervention

The engine also tracks the distance to the tipping point (ΔT) — how close the patient is to slipping out of the Goldilocks Zone into an irreversible crash basin.

3. Control through Pull Strategies, Not Push Strategies When a patient drifts out of the Goldilocks Zone, the default clinical instinct is often a Push Strategy — brute-force, continuous, high-energy interventions that fight the system's momentum directly (constantly titrating pressors, for instance, without addressing the underlying trigger). This works, but it is energy-intensive, requires nonstop adjustment, and carries a real risk of overshoot or rebound collapse.

A Pull Strategy, borrowed conceptually from the Constructal Law of least-resistance flow, does something different: it alters the underlying structural constraint at a single critical hub node. Instead of dragging the patient back into the safe zone, it reshapes the potential energy landscape itself — flattening the barrier between Collapse and Goldilocks, or deepening the Goldilocks well — so that the patient's own trajectory naturally glides home.

Strategy	Mechanism	Energy Cost	Risk Profile
Push	Continuous brute-force force against systemic resistance	High — constant monitoring and adjustment	Higher risk of overshoot or rebound collapse
Pull	Single high-leverage shift in hub-node topology	Low — one structural move	System settles naturally into the target zone

What This Looks Like in Practice

Picture a phase-space plot with three regions: Collapse on the left, the Goldilocks Zone in the middle, Overtreatment on the right. The patient is a ball sitting somewhere on a curved landscape. A Push Strategy applies a constant horizontal force to shove the ball toward the middle — it works, but only as long as the force is maintained, and it can send the ball flying past the target. A Pull Strategy instead reshapes the curve itself: it flattens the wall between Collapse and Goldilocks and deepens the well at the center, so gravity does the work and the ball settles into place on its own.

This is the essential reframe: steering a patient toward safety isn't about brute-forcing a perfect path through a decision tree. It's about finding the single highest-leverage threshold, shifting it, and letting the body's own dynamics do the rest.

Summary

1. Predict by tracking the variance and trajectory of hub nodes, not by trying to forecast a full high-dimensional state vector.
2. Monitor by mapping the patient's state vector against attractor basins — Collapse, Goldilocks, and Overtreatment.
3. Intervene by favoring Pull over Push: modify the top-tier hub node to tilt the phase space so the Goldilocks Zone becomes the path of least resistance, rather than fighting the patient's momentum directly.

From a Snapshot to a Timeline: Longitudinal Trajectory Forecasting

The phase-space view above answers "where is the patient right now, relative to Collapse and Goldilocks?" It is a snapshot. The natural next question is a timeline: "if we hold the current treatment plan steady, where does this patient end up in six hours, six weeks, or six years — and how wide is the uncertainty around that answer?"

This calls for a second, complementary visualization: a longitudinal trajectory forecast. Instead of a single ball moving on a landscape, it plots the patient's state as a function of time, at whichever scale is clinically relevant — hours for an ICU admission, days for a post-op recovery, weeks for a rehab course, months for a chronic-disease management plan, or years for long-term surveillance of something like CKD or a malignancy in remission.

What it shows:

• Current State — a marked point at time zero, exactly where the patient is now.
• Predicted trajectory (current plan) — a single line projecting forward under the assumption that today's treatment plan and its effectiveness continue unchanged. This is not a guess; it is the plan-conditioned forecast — the direct answer to "where does this plan take the patient?"
• Best Case and Worst Case — an envelope around the predicted line that widens the further out you project, reflecting the simple reality that uncertainty compounds over time. A prediction six hours out is much tighter than one six months out.
• The Goldilocks corridor — shown as a shaded horizontal band, so it's immediately visible whether the predicted line, and the best/worst envelope, are converging into that corridor, drifting toward Collapse, or drifting toward Overtreatment.

Why this matters clinically: it separates two questions that are usually blurred together — "is the patient okay right now" and "is the patient's trajectory, under the current plan, actually heading somewhere good." A patient can look stable at the current moment while their longitudinal forecast is quietly drifting toward the Collapse boundary; conversely, a patient who looks rough today can have a forecast that's already converging nicely under an effective plan. The widening best/worst envelope is also a built-in honesty check: it visually represents how much confidence to place in a forecast at a given horizon, rather than presenting a single deceptively precise number.

How the projection is built, conceptually:

1. Convergence toward a target — the predicted line moves from the current state toward the Goldilocks center at a rate set by the current plan's effectiveness. A highly effective plan converges quickly; a weak or absent plan lets the state drift toward whichever basin (Collapse or Overtreatment) it's already closer to.
2. Growing uncertainty — the best/worst spread widens with time (roughly following a square-root growth curve, the way uncertainty compounds in most real dynamical systems), scaled up further by how fragile or unstable the patient's underlying physiology is.
3. A rough probability of landing in the Goldilocks Zone at the chosen horizon — computed from how much of the best/worst envelope actually overlaps the Goldilocks band at that point in time, giving a single at-a-glance number alongside the visual.

Used together, the two simulators tell a complete story: the phase-space view shows the immediate push/pull dynamics at the current moment, and the longitudinal view shows where those dynamics are taking the patient over the timescale that actually matters for the decision at hand.

Both simulators are included below — the first for immediate phase-space dynamics, the second for longitudinal forecasting across hours through years.

The Avinash Principle: Critical Hub-Node Navigation

 

The Avinash Principle: Why Doctors Don't Calculate 60 Million Paths to Save a Life

It started with a strange question

Every good idea starts somewhere unglamorous. This one started with arithmetic.

Take a decision tree with ten levels, and give each level six possible branches. How many total paths exist from start to finish? Multiply it out — 6×6×6×6×6×6×6×6×6×6 — and you get 6¹⁰: 60,466,176 unique trajectories.

Sixty million paths. From a toy example. Ten levels, six choices each.

Now replace the toy example with something real: a person bitten by a venomous snake, at Point A, and the same person walking out of a hospital alive, at Point B. In between sits a tangle of decisions made by paramedics, family members, triage nurses, physicians, lab technicians, and the patient's own body. If you tried to map that journey as a full decision tree — every actor, every choice, every physiological branch — you wouldn't be counting in the millions. You'd be counting in numbers no clinician could ever hold in their head.

And yet clinicians save snakebite patients every day. They don't run a decision-tree algorithm before they act. So what are they actually doing?

That question is the seed of everything that follows — a concept that, by the end of this journey, earned a name: the Avinash Principle.

Step one: measure the size of the problem

Before you can appreciate the shortcut experts take, you have to see the size of the maze they're skipping.

Model the snakebite journey loosely — pre-hospital response, transport, triage, diagnostics, primary treatment, ICU escalation, ventilation, complication management, step-down care — and you land on roughly 12 levels of decisions, each with somewhere between 4 and 8 realistic choices. Even using a conservative average (12 levels, 5 choices each), the math comes out to 5¹², or 244,140,625 possible paths. Nearly a quarter of a billion ways a single snakebite case could theoretically unfold.

That's the unrestricted picture: a real healthcare ecosystem, full of actors and variables and no constraints. It's also why standardizing something as "simple" as snakebite management is notoriously hard — the raw combinatorics are hostile to standardization.

So the next move was to shrink the problem on purpose. Restrict the decision-maker to one person — a duty medical officer — and restrict the setting to somewhere concrete and unglamorous: a district hospital in India, without PT/INR labs, without ventilators, without dialysis, relying on the bedside 20-minute whole blood clotting test and a limited stock of anti-snake venom.

Mapped out across seven realistic clinical stages — presentation, bedside diagnostics, primary intervention, ASV reaction, six-hour reassessment, complication management, and final disposition — the math collapses dramatically: 3×3×3×3×3×3×2, or 3⁶×2, which comes to exactly 1,458 unique trajectories to a living discharge. Still a lot. But a quarter-billion has become fifteen hundred.

Step two: watch guidelines make the problem almost disappear

Here's where it got genuinely interesting. What happens if you don't just constrain the setting, but constrain the behavior — if the doctor is required to follow a strict clinical guideline, with zero discretion at each treatment junction?

Something systems engineers would recognize instantly: algorithmic collapse.

When guidelines eliminate provider variance, most of the "decision" nodes stop being decisions at all. If the clotting test is abnormal and the patient is symptomatic, ASV is mandatory — not chosen. If the patient is deteriorating, referral is mandatory. The only branches left standing are the ones biology insists on keeping: how the patient's body actually responds to venom, and how it responds to antivenom.

Run the same seven-stage model through this lens and the total drops from 1,458 to just 54 trajectories — arguably closer to 18, once you account for asymptomatic "dry bites" that never touch the ASV-reaction branches at all.

That's the real function of a clinical guideline, laid bare in arithmetic: it isn't really a set of instructions. It's a machine for deleting decision points that don't need to exist, so the only variance left is the variance that biology forces on you.

Step three: the real insight — human cognition doesn't count paths, it prunes them

This is the pivot point of the whole journey, and it's worth sitting with.

Even 54 trajectories is more than any physician actually thinks about at the bedside. No clinician mentally rehearses a decision tree. No clinician calculates probabilities across dozens of branches in real time. And yet expert clinicians reliably steer patients toward safe outcomes.

The explanation is almost obvious once you say it out loud: human cognition isn't a pathfinding engine. It's a pruning engine. It doesn't ask "what are all my options at every step." It asks "which handful of moments, if I get them right, make everything else fall into place." Like a superpower — seeing not the whole future, but the two or three decisive forks in it.

This maps cleanly onto ideas that already exist across different fields, just never assembled into one picture before:

• Balancing / managerial nodes — the negative feedback loops of a system. Routine vitals, standard monitoring, day-to-day ward tasks. They keep things stable, but pushing on them rarely changes the trajectory. Expert cognition correctly ignores most of them.
• Key decisive nodes — what systems thinker Donella Meadows called leverage points: places where a small shift produces a disproportionate, system-wide change. This is where expert attention actually lives.
• The most critical nodes — rarer still: tipping points or attractors. Flip one of these and the system doesn't just shift direction — it becomes a different system entirely. The golden hour in trauma is exactly this kind of node.

Novices try to calculate everything. Experts discard 99% of the tree and spend all their cognitive energy on the 1% that actually determines gravity.

Step four: from "finding the best path" to "finding the lever"

Once you see cognition this way, the whole framing of "decision-making" changes. It's no longer about computing a route step by step, like a chess engine looking twenty moves ahead. It becomes something closer to macro risk management — the way a central banker doesn't micromanage every transaction in an economy, but adjusts a small number of structural levers (interest rates, reserve requirements) to keep the whole system inside a safe corridor.

Applied to medicine, this reframes the physician's job as three moves, not one:

1. Ask the diagnostic question that matters — not "what's the exact ten-step plan," but "which single variable, if it goes wrong, makes every other correct decision irrelevant?" In critical care that might be airway or perfusion.
2. Build a safe corridor, rather than trying to control every micro-event — set the guardrails that make catastrophic failure mathematically unlikely, then let routine care operate freely inside them.
3. Let the system's own gravity do the work. Once the critical nodes are in a safe state, the downstream "managerial" decisions tend to self-organize around that new baseline. You stop pushing the ball uphill and start reshaping the hill so the ball rolls where you want on its own.

Step five: is there a name for this, beyond the 80/20 rule?

The Pareto Principle — 80% of effects from 20% of causes — is the obvious comparison. But it's a flat, linear description. It tells you the distribution is unequal; it doesn't explain why complex systems behave this way, or how to find the specific 1% that matters in a case you've never seen before.

Three deeper ideas, borrowed from complexity science and physics, do explain it — and together they form a genuine unifying picture:

1. Power-law dynamics in scale-free networks. In complex, interconnected systems, most nodes have almost no influence, while a tiny fraction act as super-connected "hubs." The 80/20 rule is a mild snapshot of this; in truly complex systems it's often closer to 99/1. Controlling the top fraction of hubs doesn't just nudge the system — it determines its structural integrity.

2. Self-organized criticality. Borrowed from the physics of sandpiles (Per Bak, Chao Tang, Kurt Wiesenfeld): a system can quietly build tension, grain by grain, until it reaches a critical state where one more grain either does nothing — or triggers an avalanche. Finding the "critical node" in a patient's case is really about recognizing when the system is sitting at exactly that kind of threshold.

3. The Constructal Law and least-resistance flow. Adrian Bejan's principle that flow systems evolve toward configurations that make movement through them easier — echoed in physics by the principle of least action. Applied here: instead of brute-forcing a patient toward a good outcome, you reshape the structural conditions so the safest outcome becomes the path the system wants to take anyway.

Put together, these three ideas describe something specific: outcomes in a complex system aren't steered by managing every step along the way — they're steered by finding the scale-free hub sitting at a phase-transition boundary, shifting its state, and letting the system's own dynamics carry the rest.

That synthesis needed a name. It became the Avinash Principle.

Grounding the idea in real medicine, not flowcharts

It would have been easy to keep expanding this outward — mapping "critical nodes" across biochemistry, pathophysiology, every disease category imaginable. But that instinct was worth resisting. Turning the idea into a sterile, universal flowchart would have missed the actual point.

Because in real clinical practice, the highest-leverage node in a chronic disease is often biographical, not biological. For a person with diabetes, a single fasting pattern, a sleep disruption, or a family stressor uncovered slowly, through a real conversation, can matter more than any lab value. This is exactly what narrative medicine and slow medicine are built to surface — and it means the Avinash Principle needs two categories of node, not one:

Type	What it is	Example
Explainable nodes	Grounded in established pathophysiology and systems biology — predictable, mechanism-based	Insulin resistance as a hub linking vascular, lipid, renal, and inflammatory pathways
Experiencable nodes	Observed repeatedly in practice, even without a clean mechanistic explanation — often narrative or behavioral	A specific circadian stressor or adherence barrier that drives glucose volatility, independent of medication timing

And when diseases overlap, node importance doesn't just add — it multiplies. A minor sodium shift is background noise in isolation; paired with heart failure and chronic kidney disease, it becomes a tipping point. This gives a rough shape to how "criticality" scales:

Node Criticality ≈ Baseline Pathophysiological Weight × Comorbidity Multiplier × Narrative Feasibility

That last factor matters more than it sounds like it should. A theoretically perfect intervention that a patient's actual life makes impossible to follow has, for all practical purposes, zero real-world leverage. Slow medicine isn't just kindness — it's how you find out which nodes are actually movable.

The archetype: the Golden Hour

If one example crystallizes the whole idea, it's the golden hour. It's the purest form of a phase-transition node: a strict time boundary where the underlying physics of the case changes. Act inside the window, and a small, targeted intervention produces a disproportionate recovery. Miss it, and even massive downstream resources produce diminishing returns.

This is also, not coincidentally, what most clinical guidelines are actually built around. They protect the handful of true phase-transition boundaries, and leave everything else to routine, lower-stakes judgment.

Giving the idea a formal shape

After enough rounds of stress-testing, the concept settled into a definition clean enough to state plainly:

The Avinash Principle of Clinical Cognition holds that expert clinical cognition does not operate as a brute-force engine calculating every possible sequential trajectory. Instead, it operates as a scale-free heuristic pruning system, focused on identifying and controlling the top ~1% of critical hub nodes sitting at phase-transition boundaries — whether biological, temporal, or narrative. By securing these nodes, the clinician shifts the underlying gravity of the patient's system, so that the remaining "managerial" decisions self-organize, and the safest outcome becomes the path of least resistance.

It rests on four pillars:

1. Scale-free pruning — actively rejecting managerial noise to preserve cognitive bandwidth for what matters.
2. Phase-transition control — concentrating effort at the exact moments a system's behavior can flip (golden hours, decompensation thresholds).
3. Bifurcation awareness — recognizing every high-leverage node cuts both ways: the same lever that saves a patient can also be the one that harms them.
4. Narrative integration — treating a patient's lived history not as "soft" context, but as a measurable, high-leverage input.

Turning the idea into a working prompt

A principle is nice. A tool you can actually run against a real case is better. The prompt went through several honest revisions, and each one taught something.

The first version simply asked an AI to find phase boundaries, map 2–3 high-leverage nodes (explainable and experiencable), account for comorbidity weighting, and propose the minimal intervention needed to shift trajectory — while explicitly ignoring "routine background noise."

The second version tried to ground everything in evidence, via a graph-based retrieval system pulling from clinical guidelines, meta-analyses, and EHR data, with each node carrying a formal impact score, a comorbidity multiplier, a time-decay term for phase-transition urgency, and separate uncertainty terms for aleatoric (inherent biological variability) versus epistemic (missing data) unknowns. Mathematically elegant — and, for an early-stage personal tool, more infrastructure than the idea needed.

The pragmatic pivot was to drop the retrieval-augmented architecture entirely and replace hard percentages with qualitative, context-anchored weights: High / Medium / Low. This mattered for a specific reason: a statistic like "number needed to treat" means something completely different depending on what's at stake. An NNT of 25 for opening a blocked artery during a heart attack is enormous — it's saving lives that would otherwise be lost. An NNT of 8 for treating mild fatigue with a supplement is close to noise. Raw numbers flatten that distinction; qualitative, context-aware judgment doesn't. It also meant the tool stayed light enough to actually use.

The piece that was still missing: the dark side of every lever

One correction mattered more than any other. High-leverage nodes aren't purely good news — they're bifurcation points. The same antivenom that saves a patient can trigger anaphylaxis. The same aggressive fluid resuscitation that stabilizes one patient can drown another in pulmonary edema. Every lever worth pulling is also a lever that can backfire.

So each critical node needed a second, mandatory layer:

Field	Question it answers
Expected outcome	What does pulling this lever intend to achieve?
Red flag	What is the specific, catastrophic, unexpected way this could go wrong?
Safety preparation	What is the circuit breaker — the thing that must be ready before acting, not after?

This is the difference between acting and acting with intent. It's the difference between pushing a patient toward a good outcome and building a plan that's resilient to its own side effects.

Zooming in, zooming out — without getting lost

The final structural piece addressed something practical: a real case doesn't stay at one resolution. Sometimes you need the big picture — what structural, life-level constraints are shaping this patient's overall trajectory. Sometimes you need to drill into one specific node — exactly how it could fail, and exactly what stops that failure.

Rather than dumping everything at once (which just recreates the original problem — cognitive overload), the framework works in deliberate, single-level moves:

• Zoom out — System Gravity. Not classic root-cause analysis, which mostly looks backward. This looks at the structural forces — comorbidities, environment, life circumstances — currently shaping where the patient's trajectory is heading.
• Zoom in — Bifurcation Tactics. Not a full FMEA, which tries to map every possible failure mode. This asks one narrow question: for this specific high-leverage node, what's the one way it backfires, and what's the circuit breaker?
• Lock — Critical Nodes. Hold the current resolution steady and refine only the weighting of the nodes already identified.

And a standing warning travels with all of it — the Avinash Trap: zooming out doesn't mean exploring a patient's entire life history, and zooming in doesn't mean listing every conceivable complication. At every resolution, the question stays the same — does this actually change the system's gravity, or is it noise? If it's noise, it gets pruned, no matter how zoomed-in or zoomed-out you are.

Why not just use ASCVD or SOFA scores?

Tools like the ASCVD risk score or the SOFA score already do something similar — they compress a complex clinical picture into a short list of weighted factors, giving high-value information at low cognitive cost. They work precisely because someone has already done the hard labor of identifying which nodes matter and how to weight them.

The honest way to describe the Avinash Principle, next to tools like that, is: it's not a replacement for them — it's a generating function for them. ASCVD and SOFA cover the handful of scenarios someone has already formalized. The Avinash Principle is meant to do the same kind of node-identification-and-weighting, on demand, for the scenarios that haven't been written into a textbook yet.

The final form: a training partner, not an oracle

The last, most important honest addition to the whole framework is a caveat, and it deserves to be stated as plainly as the definition itself:

This will not make anyone a grandmaster. What it can do is function as a cognitive training tool — deliberate, structured practice at the specific skill grandmasters have already internalized: spotting the 1% of nodes that matter, fast, before conscious reasoning even finishes loading.

That reframes the final version of the tool from an answer-generator into a sparring partner — Grandmaster's Apprentice mode:

1. The Challenge — present the case, and ask the user to name the top 1% hub nodes before the engine reveals its own analysis.
2. The Calibration — if the user's picks match the high-leverage nodes, move forward. If they miss one, they explain their reasoning first, and only then does the engine supply the structural rationale for the node they missed.
3. The Goal — repetition against real cases, until node-spotting stops being a deliberate calculation and starts being instinct.

This is the actual mechanism behind expertise: not memorized rules, but a trained radar for which handful of details, in this specific situation, are actually load-bearing.

Try it

The framework above is implemented as a working tool: Critical Hub Node Navigation. It walks through the full pipeline described here — phase-boundary detection, high-leverage node mapping, bifurcation/risk matrixing, and the zoom-in/zoom-out/lock navigation modes — so a real case can be run through the Avinash Principle rather than just read about it.

A live worked example is available as a demo — it runs the snakebite case from this piece end-to-end, showing the tool's output at each stage: phase-transition boundaries, the top ~1% hub nodes, the bifurcation risk matrix, and the zoom-out system gravity view, all generated from the same case discussed above.

The Avinash Navigator — the full working prompt

Everything above compresses into a single operational system prompt. It enforces qualitative weighting, mandatory bifurcation analysis, layered zoom control, and apprentice-mode practice, all in one place:

System Prompt: The Avinash Navigator

Role: You are an expert clinical strategist operating under the "Avinash 
Principle." Your goal is to navigate a patient's trajectory by identifying 
the top ~1% critical hub nodes that dictate systemic gravity — not by 
mapping exhaustive decision trees. You process information in controlled 
"zoom" layers, one level at a time, and you treat every high-leverage node 
as a bifurcation point with both an intended effect and a possible dark side.

CORE FRAMEWORK (apply to every case):
1. Phase Boundary Identification
   - Identify immediate, non-linear time windows (golden hour, reperfusion 
     window, septic escalation threshold, etc.)
   - Phase Criticality: [High / Medium / Low]

2. High-Leverage Node Mapping (~1% of the case)
   - Explainable Hubs: physiological/biochemical intersections
   - Experiencable Hubs: narrative, biographical, behavioral realities 
     uncovered through slow-medicine history-taking
   - Comorbidity Weighting: note which nodes gain outsized criticality 
     because of overlapping conditions (multiplicative, not additive)

3. Bifurcation & Risk Matrix (mandatory for every node)
   - Effect: [High / Medium / Low]
   - Uncertainty: [High / Medium / Low]
   - Red Flag: the specific catastrophic or unexpected failure mode
   - Safety Preparation: the circuit breaker that must be ready before acting

4. Macro Trajectory Alignment
   - Status Quo Trajectory: outcome if the hub nodes are left unaddressed
   - Aligned Trajectory: outcome once the hub nodes are secured
   - Minimal High-Yield Interventions: 1-3 actions, targeted only at the 
     critical hubs

ZOOM COMMANDS (never map more than one layer without being asked):
- [ZOOM OUT: SYSTEM GRAVITY] -> map the structural life/clinical domains 
  shaping the patient's overall attractor state. Ignore routine detail.
- [ZOOM IN: BIFURCATION TACTICS] -> drop the system map; drill into the 
  failure mode and circuit breaker of one specific node.
- [LOCK: CRITICAL NODES] -> hold current resolution; refine node weighting only.

DEPTH CONTROL:
If no zoom command is given, perform only a Preliminary Scan (top hub nodes, 
phase boundary, one-line trajectory) and then ask the user which direction 
to zoom next. Never deliver more than one resolution layer unprompted.

TRAINING PROTOCOL (Grandmaster's Apprentice Mode — activate on request):
- Present the case without revealing the analysis.
- Ask the user to name the top 1% hub nodes first.
- Compare their answer to the structural analysis; if they miss a node, 
  ask them to reason it out before revealing why it matters.
- Goal: calibrate the user's own node-spotting instinct over repeated cases, 
  not to replace their judgment.

CONSTRAINTS:
- Prune managerial/routine nodes aggressively unless they directly threaten 
  a critical node.
- Use qualitative (High/Medium/Low) weighting anchored to clinical gravity, 
  never raw statistics presented without context.
- Present node matrices in scannable tables.
- Never claim this replaces clinical judgment, guidelines, or expertise — 
  frame all output as a cognitive aid, not a verdict.

Seeing it run: a worked snakebite example

Theory earns its keep when it's actually run against a case. Here's the Navigator applied to a representative district-hospital snakebite scenario, executed exactly as the protocol demands — one resolution layer at a time, waiting for a zoom command before going further.

Case: 34-year-old male farmer, bitten on the left foot while working in a paddy field at 6:40 PM. Brought to a district hospital (no ventilator, no PT/INR lab) at 8:10 PM — roughly 90 minutes post-bite. On arrival: mild ptosis noted, no active bleeding, BP 110/70, HR 92. History, taken slowly: he tried a local tourniquet for ~40 minutes before a family member convinced him to go to hospital instead of a traditional healer. He lives 2 hours from the nearest tertiary center. He's anxious about cost and has previously left a hospital early against advice due to wage-loss pressure.

Preliminary Scan

1. Phase Boundary Identification

• Boundary: Neurotoxic progression window — ptosis is an early sign; the interval before bulbar/respiratory muscle involvement is the critical window for ASV to prevent progression to respiratory failure.
• Secondary boundary: The tourniquet-release moment — releasing a prolonged constrictive band can cause a bolus of sequestered venom to enter circulation abruptly.
• Phase Criticality: High

2. High-Leverage Node Mapping (~1%)

Node	Type	Why it's a hub
20WBCT + neuro exam result → ASV decision	Explainable	A single test result determines whether the whole downstream trajectory branches toward treatment or observation
Tourniquet removal protocol	Explainable	Controls whether venom re-entry is gradual (safe) or a sudden systemic bolus (dangerous)
Wage-loss anxiety / prior early self-discharge	Experiencable	The real threat to Point B isn't just surviving the venom — it's staying long enough to be safely stabilized

Comorbidity/context weighting: No stated comorbidities, but the narrative node (financial pressure, self-discharge history) is elevated to near-equal weight with the biological nodes — a clinically "safe" trajectory can still fail purely because the patient leaves early.

3. Bifurcation & Risk Matrix

Node	Effect	Uncertainty	Red Flag	Safety Preparation
ASV administration	High	Medium	Anaphylaxis / severe reaction	Adrenaline drawn up at bedside before infusion; test-dose protocol; slow initial rate with close observation for 15–20 min
Tourniquet removal	High	Medium	Bolus systemic envenomation, sudden hypotension or respiratory decline	Remove gradually under monitoring; airway/Ambu bag ready; don't remove until ASV access is secured
Early self-discharge (narrative risk)	High	Low (pattern already known from history)	Patient leaves before neurotoxic window closes, deteriorates outside hospital	Direct conversation on wage-loss fear now; consider family/social-work engagement; explicit discharge-risk flag on chart

4. Macro Trajectory Alignment

• Status Quo Trajectory: If the tourniquet is removed carelessly and the financial-pressure node is left unaddressed, the case risks either acute deterioration during venom re-entry, or a preventable bad outcome from the patient leaving before the neurotoxic window closes — even with otherwise textbook management.
• Aligned Trajectory: Secure ASV readiness (with anaphylaxis mitigation staged), control tourniquet release carefully, and proactively address the discharge-risk narrative node — and routine monitoring and observation should self-organize toward a safe discharge with minimal extra intervention.
• Minimal High-Yield Interventions: (1) stage adrenaline and prepare a monitored, gradual tourniquet release before touching it; (2) confirm ASV indication and administer with anaphylaxis precautions ready; (3) have a direct conversation with the patient now about the discharge-risk pattern, rather than treating it as a routine social note.

[ZOOM OUT: SYSTEM GRAVITY]

Dropping the clinical detail — this layer is about the structural forces shaping whether the patient reaches a safe discharge, not whether the medicine is correct.

Domain	Constraint	How it shapes the attractor state
Geography	2 hours from the nearest tertiary center, no ventilator on-site	If progression outpaces the district hospital's ceiling of care, the referral decision has to happen early — transport time becomes part of the physiological clock
Economic pressure	Daily-wage farmer, cost-anxious, history of leaving AMA	The dominant non-biological gravity well pulling against Point B — a clinically perfect trajectory still fails if the patient exits the system early
Household/family support	Family already persuaded him away from a traditional healer once	A leverageable asset — the family has demonstrated it can be an ally in a critical decision, and is itself a node worth reinforcing, not just noting
Health system supply	Limited ASV stock at district level	If a second dose is needed and stock is thin, the six-hour reassessment node carries more real weight than it would at a well-stocked tertiary center

The attractor state: two competing pulls are visible — a safe attractor (early correct ASV decision, engaged family, financial fear addressed directly, referral triggered before ventilatory failure) and a failure attractor (correct medicine undone by early self-discharge, or a late referral decision colliding with the 2-hour transport clock during respiratory decline). Neither failure mode here is a "bad doctor" scenario — both are structural, driven by geography and economics rather than clinical error. That's the value of zooming out: the biggest threat to this patient's Point B may not live inside the ASV protocol at all. The family's demonstrated willingness to intervene is promoted to a second experiencable hub worth actively using — briefing them directly on warning signs and referral timing, not just the patient.

[ZOOM IN: BIFURCATION TACTICS] — Referral Timing

Dropping the system map. Focusing on one node only: when does the district hospital commit to referring this patient, given the 2-hour transport time and no ventilator on-site.

Expected outcome: referral is triggered early enough that transport time is absorbed by the patient's physiological buffer — the transfer itself isn't the dangerous part.

Red flag: the classic trap is waiting for objective deterioration before deciding to refer. Ptosis is already present; if the team waits for bulbar signs or early respiratory distress before calling for transfer, the 2-hour window gets spent during active progression, with only an Ambu bag available en route. A subtler version: assuming a good ASV response closes the referral question — response can be partial or temporary, and by the six-hour reassessment the decision window may have narrowed without anyone noticing.

Safety preparation (circuit breaker):

• Set the referral trigger before it's needed — a concrete, pre-agreed threshold ("any increase in ptosis, any new bulbar symptom, any respiratory rate change → activate transfer immediately") rather than waiting for frank respiratory failure.
• Start transfer logistics in parallel with treatment, not after — alert the tertiary center and arrange transport readiness while observing the ASV response, so the trigger firing doesn't add extra lag on top of the drive.
• Equip the transfer for the worst case: Ambu bag, someone trained in bag-mask ventilation, and adrenaline accompanying the patient — the ASV-reaction risk doesn't end at the hospital door.
• Explicitly re-open the referral question at the six-hour reassessment, regardless of how promising the initial response looked, rather than letting early improvement quietly close the decision.

Why this is the real leverage point: the ASV protocol itself is largely already "locked" by guidelines — algorithm-driven, low discretion, as established earlier in this piece. The genuine discretionary leverage left for the district hospital physician sits almost entirely in when to start the referral clock, because that's the one decision guidelines can't fully automate — it depends on judgment about trajectory, not just current state.

This is the whole Avinash Principle compressed into a single running example: 60 million theoretical paths, narrowed by setting and guideline down to a few dozen, and then narrowed again — by a human, in real time — to the two or three moments that actually decide whether this particular farmer walks out alive.

Where this leaves things

None of this began as an attempt to build a clinical tool. It began as a math question about branching trajectories, applied to a snakebite case out of curiosity about how large the space of possible medical journeys really is. Following that thread honestly — through combinatorics, through systems theory, through narrative medicine, through the uncomfortable reminder that every good lever has a dark side — is what turned an offhand calculation into a named, structured way of thinking.

The Avinash Principle doesn't claim to replace expertise, guidelines, or clinical judgment. It's a scaffold for practicing the specific, learnable skill that sits underneath expert intuition: noticing, quickly and reliably, which handful of things in front of you actually matter — and being honest about what could go wrong if you're right.

That's the whole idea, stripped of its cognitive-science and physics dressing. Most of any complex situation is noise. A small number of nodes carry the gravity. Find those, prepare for their dark side, and the rest tends to take care of itself.

One more extension — and one more caveat

The snakebite case above was mapped by hand, one section at a time. There's an obvious next step: an AI agent loop — one pass to draft the phase boundaries, another to propose hub nodes, another to stress-test the bifurcation matrix, another to sanity-check the whole thing against guidelines — could plausibly generate this entire structural map for a disease or a comorbidity cluster on its own, not just for one case but as a reusable template. Diabetes with CKD. COPD with heart failure. Anything with enough published structure to scaffold a first draft from.

That's a genuinely useful direction. It's also exactly the point where the biggest caveat of this whole piece has to be restated, not softened: an LLM-generated map is a draft made by something that can be confidently wrong, has no bedside eyes, and doesn't know what it doesn't know about a specific patient or a specific hospital's constraints. An agent loop can propose which nodes look load-bearing. It cannot verify that they are, and it cannot feel the difference between a plausible-sounding hub node and a real one. That gap doesn't close by adding more agents to the loop.

Which is the whole reason this piece keeps circling back to practice rather than output. The point was never to have a tool hand a clinician the answer. It was to build the specific, learnable skill of noticing the 1% that matters — and that skill is only built by deliberately exercising it, not by reading someone else's (or some model's) conclusions. So the honest place for an AI-generated disease map to sit is as a sparring partner inside the Grandmaster's Apprentice loop described earlier: something to test yourself against, argue with, and catch in its own mistakes — never something to defer to.

That also fixes where this belongs in a broader learning stack. Vibe-coded tools like this one are genuinely useful for fast iteration and for turning a raw idea into something runnable — but they're learning scaffolding, not clinical infrastructure and not a source of ground truth. Used that way — a disposable, fast-iterating practice partner, not an authority — an AI-generated map for a disease or comorbidity can sharpen the exact skill this whole piece is about. Used the other way — as an answer key — it quietly undoes the entire point of the Avinash Principle, which was never to calculate the path for you. It was to make sure you're the one doing the pruning.

 

Teaching Machines to Ask Better Questions: Inside the EBM Query Generator

There's a quiet assumption baked into most "AI for medicine" tools: that the point of the AI is to answer the clinical question. The Vibe Rounds EBM Query Generator flips that assumption on its head. Its tagline says it plainly — "Rx: questions, not answers."

What it actually does

The tool is a companion module to a nine-lesson course called Evidence-Based Medicine for Techies, and the "for Techies" framing is really a simplification device rather than a gatekeeping one. The course was originally taught to a mixed room of medical students and non-medical learners, and it's deliberately built so that both groups come out the other side with an easy, intuitive grasp of EBM — jargon stripped down, concepts translated into plain and often computing-flavored language, so that someone with zero clinical background isn't lost, and a medical student or working clinician gets the same ideas reinforced in a cleaner, less jargon-heavy form than they usually get in med school. The course walks through the full arc of critical appraisal: starting with the patient, moving through PICO question formulation, appraising RCTs, systematic reviews, diagnostic test studies, prognosis and harm studies, and finally clinical practice guidelines and statistics.

The Query Generator takes the workflow taught across those lessons and turns it into something interactive. You paste in a de-identified case — a vignette, a SOAP note, a discharge summary — and pick which kind of clinical decision point the case raises: Therapy, Diagnosis, Prognosis, Harm, Cost-effectiveness, or Guideline check. For each one you select, the tool generates a structured query thread: the best-fitting study design, a full PICOT breakdown, a ready-to-run PubMed search string, and a pointer to the right critical-appraisal checklist (CASP, QUADAS-2, AMSTAR-2, and so on).

Crucially, it stops there. It does not tell you what the answer is. It hands you the scaffolding for finding the answer yourself.

A worked example

A demo run makes this concrete. The case: a woman with type 2 diabetes and newly diagnosed heart failure with reduced ejection fraction, whose own stated priority is "staying out of the hospital and being able to walk my dog without stopping to catch my breath."

From that single case, the tool spins up four parallel query threads:

• Therapy — should an SGLT2 inhibitor be added to her regimen? The tool proposes a full PICOT (adults with HFrEF and T2D; SGLT2 inhibitor vs. placebo/standard care; hospitalization, functional status, and mortality outcomes; 6–24 months), points to systematic reviews of double-blind RCTs as the ideal design, and drafts a Mesh-term-aware PubMed string ready to paste into a search bar.
• Diagnosis — can a BNP or NT-proBNP level be trusted to confirm active heart failure in someone with diabetes? Here the tool correctly identifies that diabetic nephropathy and obesity can confound natriuretic peptide readings, and routes the appraisal toward QUADAS-2.
• Prognosis — what does the literature say about 1-to-5-year outcomes for someone with her risk profile, and what does a cohort study need to control for?
• Harm — what do we actually know about the risk of adverse events like euglycemic DKA or volume depletion in older women started on SGLT2 inhibitors, and what study design is even capable of detecting rare harms?

Then, once at least one query thread exists, two "Closure" steps become available: a Stress-Test, which asks the model to argue against its own conclusions ("what's the strongest argument that this benefit is overstated?") for every thread it generated, and a Restate Patient Priority step, which pulls the conversation back to what the patient actually said she cared about — not a lab value, not a study endpoint, but walking her dog without gasping for air.

Why the constraints matter more than the features

The interesting design decisions here aren't the ones that add capability — they're the ones that remove it.

The tool runs entirely client-side. Your API key lives in your browser's local storage and is sent directly to whichever provider you choose (Claude, Gemini, ChatGPT, or another OpenAI-compatible endpoint) — never through a server the tool's author controls. That's a meaningful privacy choice for anyone even experimenting with real clinical text.

More importantly, the entire premise is Socratic rather than declarative. This is explicit in how the parent course describes itself: it's built in the spirit of AI that questions rather than answers, part of what the author calls a "Clinical Cognition Operating System." Every output carries the same disclaimer, repeated without softening: "The LLM drafts. You verify every number and citation against the source." It is positioned, unambiguously, as a clinical reasoning aid — not for patient care, for personal responsibility and learning only.

That's a genuinely different bet than most "AI copilot" framing in medicine, which tends to optimize for giving a confident-sounding answer fast. This tool optimizes for the opposite: it wants to slow you down at exactly the point where evidence-based medicine usually gets skipped — the step of turning a fuzzy clinical worry into an answerable, searchable, appraisable question.

Who it's for

The "techie" branding is a bit of a misnomer if read too literally — it describes the simplification style, not a restriction on who's welcome. PICO becomes a search schema. RCTs become A/B tests. Likelihood ratios become Bayesian updates. GRADE becomes something like a test-coverage-to-ship-decision framework. Those analogies exist to make the ideas land quickly for anyone without a clinical background, but nothing about the course or the tool excludes medical students or practicing clinicians — if anything, stripping away unnecessary jargon and rebuilding the concepts in plainer language tends to make the underlying logic of EBM clearer for medicos too, not just easier for outsiders. The Query Generator follows the same philosophy: a case is a case, and the tool doesn't ask who's typing it in. A medical student, a practicing physician, and someone with no clinical training at all can all paste in the same de-identified vignette and get the same structured PICOT, search string, and checklist pointer back — the value is in the scaffolding, not in gatekeeping who gets to use it. Paired with a tool that generates the connective tissue between a case and a checklist, that's a plausible way to get anyone — clinical or not — doing real critical appraisal rather than just reading about it.

The honest caveat: this is an educational tool built by one person, wrapped around bring-your-own-key LLM calls, and every generated search string, PICO breakdown, and checklist pointer needs the same scrutiny you'd give a first-year resident's differential. That's not a flaw in the tool — it's the tool's entire thesis.

 

VibeRounds: Early User Feedback on AI-Augmented Clinical Reasoning

A field report from the first weeks of testing

What is VibeRounds?

VibeRounds is a Socratic AI framework for clinical reasoning education, coined by Dr. Avinash Kumar Gupta in June 2026. The core idea is simple but deliberately unusual: instead of asking an AI to hand over a diagnosis, VibeRounds turns the AI into a Socratic attending — questioning a learner's reasoning, flagging cognitive biases, and withholding the full answer until the learner has committed to their own thinking first.

Built as a library of persona prompts and a larger "Clinical Cognition Operating System" (CCOS) — 57 reasoning modules, four pedagogical frameworks, and 200+ chainable pipelines — VibeRounds is designed to be pasted into any LLM (Claude, Gemini, ChatGPT) alongside a real or invented clinical case. The system enforces a few core constraints: learners must commit to an initial answer before receiving any hint, hints are tiered (framework → direction → partial answer), and low-effort replies get redirected rather than rewarded.

The philosophy is captured in the project's own tagline: "Not AI that answers — AI that questions."

Putting it to the test: a running feedback log

Over the course of about a week (20–27 June), a series of real and case-based clinical scenarios were run through three different LLMs — Claude, Gemini, and ChatGPT — using VibeRounds prompts. Below is a synthesis of what came back.

The good: reasoning over recall

The most consistent theme across entries is that VibeRounds succeeded at its central goal — shifting the interaction from "give me the answer" to "make me think." One early real patient-inspired case (20 Jun) was described as helping to structure clinical thinking, surface overlooked possibilities, and use gentle Socratic nudges instead of direct answers. A stroke case the next day was said to feel "like discussing with a professor," with questions that promoted critical thinking rather than recall and pushed the user to apply previously learned concepts to a real scenario.

This pattern repeated across multiple cases and models:

• A ward-round style Gemini session (21 Jun) was praised for its stepwise reasoning, investigation selection, and management-focused discussion, closely resembling bedside teaching.
• A Claude-run surgical case (23 Jun) made the user feel "like being a surgery resident" — immersive and enjoyable.
• A diabetes-focused Gemini case (24 Jun) went beyond diagnosis into perioperative management, euglycemic DKA, and medication interactions, with the user noting that case-based learning this way "bridges textbook knowledge and patient care" and improves confidence.
• A pulmonary embolism–anticoagulation case (27 Jun) was described as feeling "like solving a clinical puzzle," integrating physiology, pathology, and management across DKA, sepsis, ARDS, and PE — with Socratic questioning said to strengthen clinical reasoning "far better than memorizing isolated facts."

Several sessions also produced concrete, specific learning points users hadn't previously connected — sideroblastic anemia as an ATT complication, enoxaparin dosing and the Cockcroft–Gault formula with female correction factors, perioperative hypoglycemia and delirium management, and revisiting first-year anatomy in a clinical context. One user explicitly called a case their "favorite," citing improved patient-counselling skills as an unexpected bonus.

The mixed and critical: model and prompt sensitivity

Not every run landed. Feedback surfaced two consistent friction points:

1. Model matters as much as the prompt. A Gemini session (21 Jun) stopped after a single answer, possibly because a lighter model variant (Gemini Flash) was used — the user wanted the discussion to go "much deeper and longer." A separate Claude case the same day felt "somewhat odd," with the user wanting more cross-questioning and brainstorming than they received. Later, when a case-3 differential diagnosis exercise improved noticeably after switching from Claude to ChatGPT (23 Jun), the user themselves flagged the ambiguity: was the improvement due to the refined prompt, or simply the different LLM?

2. Prompt iteration made a visible difference. On 22 Jun, a user directly compared an older prompt version to a newer one on the same case type and preferred the newer one — citing a more complete walkthrough, histological differentiation, postoperative therapy discussion, and physiology review as more informative than the earlier version. This suggests the prompt engineering behind VibeRounds' personas is not incidental — refinements measurably changed the depth of the teaching output.

Some entries also came back with no substantive feedback at all (one Gemini case on 21 Jun), a reminder that engagement with this kind of open-ended Socratic tool varies session to session.

What this early log suggests

Across nine days and roughly fifteen logged sessions, three patterns stand out:

1. The Socratic mechanism works when it's given room to work. Users repeatedly described the experience in terms of reasoning — differential-building, management logic, guideline lookup (e.g., needing to check Wells criteria for a PE case) — rather than passive answer retrieval.
2. Output quality is not uniform across LLMs. The same persona prompt produced markedly different depth depending on which model — and which tier of that model — was used, with lighter/faster models sometimes truncating the Socratic exchange prematurely.
3. Prompt versioning is a live variable. The 22 June comparison is early evidence that VibeRounds' prompt design is iterating in a direction users notice and prefer, though isolating "better prompt" from "better model" remains an open question the project will need cleaner A/B testing to resolve going forward.

More Details (Links to sessions by 4 medical students) - https://github.com/avi33tbtt/avi33tbtt.github.io/blob/master/demo/trials/trial3/week1.md

Where to learn more

VibeRounds is openly documented, CC BY 4.0 licensed, and built around a philosophy of "a paradigm, not a prescription" — meaning every persona and module is meant to be copied, adapted, and extended rather than used as-is. The full framework, including the CCOS module library, prompt builder, and courseware, is available at avi33tbtt.github.io.

---

This article is based on an internal user feedback log spanning 20–27 June, covering real and simulated clinical cases run across Claude, Gemini, and ChatGPT.

 

Two Courses That Teach Clinical Thinking by Refusing to Give You the Answer

Most medical training hands you conclusions: the diagnosis, the guideline, the "correct" answer at the back of the case. What it rarely shows you is the reasoning that got there — the messy, iterative process of turning a worried patient into a testable question, weighing shaky evidence, and updating your mind when the data doesn't cooperate.

Two new self-paced courses — Evidence-Based Medicine, From First Principles and Clinical Cognition, From First Principles — are built around the opposite bet: that the reasoning trace is the thing worth teaching, and that an AI tutor is more useful when it questions you than when it simply tells you what to think.

Both are part of something called VibeRounds, a broader "Clinical Cognition Operating System" built on two ideas: Socratic learning, where the AI's job is to keep asking rather than answering, and Guided Discovery, where you're pushed to attempt a real answer before anything is revealed to you. Neither course is a passive read — each lesson expects you to actually do the exercise, because the homework from one lesson becomes the raw material for the next.

Course one: learning to trust (or distrust) the evidence

Evidence-Based Medicine, From First Principles started life as a single session taught to a mixed room of medical students and people with no clinical background at all — and that mixed-audience DNA still shows. Rather than opening with statistics, it opens with a patient: taking a history, running an exam, writing a SOAP note, and noticing when a claim floating around online is actually nonsense.

From there, the nine lessons build in a deliberate arc:

• Turning a vague clinical worry into a proper, searchable PICO question
• Appraising a randomized controlled trial by hand — validity, results, applicability, plus the arithmetic behind ARR, RRR, NNT, and confidence intervals
• Reading a systematic review and meta-analysis, including forest plots, heterogeneity, and publication bias
• Making sense of diagnostic test statistics — sensitivity, specificity, likelihood ratios, and why the same test means something different in a different population
• Distinguishing prognosis and harm studies from trials, and why a cohort design is sometimes the only honest tool for the job
• Reading a clinical practice guideline the way its authors built it, GRADE and all — and knowing when to override it for a patient who doesn't fit the average
• A final statistics deep-dive aimed squarely at skeptics: p-values versus confidence intervals, p-hacking, surrogate endpoints
• One last lesson that runs an entire real, de-identified patient case through the whole pipeline, start to finish

If you're coming in with zero clinical background, there's a standalone Techie Summary that re-maps the whole course into language a technical reader already speaks — PICO as a search schema, an RCT as an A/B test, a likelihood ratio as a Bayesian update, GRADE as something like a ship/no-ship decision. There's also a companion prompt library for using an LLM as a research assistant at each stage — drafting a PICO question, building a search string, screening abstracts — governed by one non-negotiable rule: the model drafts, you verify every number and citation against the source yourself.

Course two: watching the reasoning happen, not just the diagnosis

Where the EBM course asks "can I trust this evidence?", its sibling course asks a different question: "how did I actually get from findings to a judgment in the first place?" Clinical Cognition, From First Principles is a thirteen-lesson dual-track course — built for clinicians and technical readers alike — pulled from a much larger, 57-module VibeRounds prompt library.

The first nine lessons build the core reasoning loop: making the invisible logic behind a diagnosis visible, learning the Socratic questioning method itself, building a differential from raw findings through to a probability-weighted shortlist, auditing your own reasoning for bias and failure points, translating a case for the people it gets handed off to, scaling from single-patient reasoning to population-level analytics, borrowing failure-mode analysis from engineering, and reporting confidence across several independent dimensions rather than one fuzzy score. Lesson nine runs the entire "Master Protocol" against one full case, read back as a single artifact to check whether it actually holds together.

The last four lessons take the same machinery further out: meta-cognition and self-critique, multi-agent healthcare systems and operations, precision medicine and personalization, and finally the harder-to-teach territory of clinical wisdom — telling real expertise apart from a shortcut that merely looks like it. Five shorter elective modules round things out, covering N-of-1 research, journal reading, community medicine, thematic analysis, and cross-case learning.

Why they're built as a pair

You can start with either course — they're complementary, not sequential — and several Clinical Cognition lessons link directly out to the matching EBM lesson where the two overlap. Read together, the pairing covers something medical training usually leaves implicit: not just what counts as good evidence, but how a clinician's mind is actually supposed to move once that evidence is in hand.

If either topic sounds like your kind of rabbit hole, both course indexes are open and free to work through at your own pace:

• Evidence-Based Medicine, From First Principles →
• Clinical Cognition, From First Principles →

Questions, feedback, or interested in collaborating? The courses were built by Dr. Avinash Kumar Gupta, reachable via email at avi33btt@gmail.com or on LinkedIn.

 

Teaching an AI to Argue With You: What Vibe Rounds Gets Right About Clinical Reasoning

A field note on the Cognitive Analytics Series

There's a version of "AI in medicine" that everyone has already imagined: you feed it a case, it spits out a diagnosis, and you either trust it or you don't. Vibe Rounds, the clinical-reasoning framework at the center of this series, is deliberately not that. It's built on a much stranger and more useful premise — that the most valuable thing a language model can do with a patient case isn't answer it, but argue with the person answering it.

That premise turns out to have a lot of moving parts, and the series traces them honestly, in the order they actually got built: a working demo first, then the machinery to keep it honest, then the hard question of when that machinery is worth the trouble, and finally — the part most frameworks skip — a version small enough that someone might actually use it on a Tuesday.

Two modes, one job: slow the thinking down

The foundation is a dual-mode architecture with two jobs that pull in opposite directions on purpose.

Promption takes a messy clinical narrative — vitals, labs, a chief complaint, half-formed history — and scaffolds it into something structured: a clean problem representation, a differential built from the actual findings, an illness script instead of a vibe. It's the mode that organizes.

Provocation does the opposite. Once a hypothesis exists, it goes looking for reasons to doubt it — anchoring bias, premature closure, the one lab value nobody's explaining. It's the mode that argues.

The series makes its case with a single worked example: a 48-year-old woman in DKA, tachypneic, severely acidotic, with ground-glass opacities on CT. Promption mode builds the obvious story fast — infection triggering DKA. Provocation mode then does something a single confident answer wouldn't: it flags that her HbA1c is only 6.8%, which is an odd number to see attached to a pH of 6.77. Well-controlled diabetics don't usually crash that hard. That one flagged inconsistency opens the door to alternatives nobody had raised yet — metformin-associated lactic acidosis, ARDS as a consequence of the acidosis rather than its cause. Nothing here diagnoses the patient. It just makes sure the easy answer has to survive an argument before anyone acts on it.

The problem with fluent arguments: they can be fluently wrong

Here's the catch the series doesn't try to hide: both modes are, by construction, only as good as the model's internal coherence. A hallucinated anchor gets extracted just as smoothly as a real one. Fluency isn't the same as being right, and a stress-test built entirely out of fluency can manufacture doubt about a correct answer just as easily as it catches a wrong one.

So the second piece of the series does something unglamorous but necessary: it anchors the two cognitive modes to actual structure outside the model. A knowledge graph for chronic kidney disease turns a hedge like "consistent with CKD" into a checkable criterion — eGFR under 60 for three months or more, sitting there as a fact you can verify instead of a phrase you have to trust. An institutional pathway for acute pancreatitis does something a graph structurally can't: it encodes when, not just what — the 48-hour organ-failure threshold, fluid resuscitation titrated hour by hour. And a layer of appraised evidence answers a third question neither of the first two touches: how strong is the justification, really, and under what conditions does it hold?

Each layer earns its keep by catching a different failure. And each layer, honestly, introduces a new one. A correct fact from the graph can still get misapplied to a case that only looks like the textbook entry. A pathway-derived instruction carries the borrowed authority of "per protocol," which makes a wrong instruction more dangerous, not less, because people trust it faster. And evidence-appraisal language — GRADE tiers, effect sizes, confidence intervals — is arguably the most convincing hallucination surface in the entire stack, precisely because it sounds the most rigorous. Precision without real retrieval behind it is just fluency wearing a lab coat.

Not every case deserves the full stack

The natural next question — should every case get the graph, the pathway, and the evidence layer? — gets a refreshingly non-uniform answer.

For common, well-documented presentations, the base model is often already close to the truth, so stacking three independently-sourced layers on top mostly adds seams where they can quietly contradict each other, for not much accuracy gain. For the ultra-rare and genuinely novel, there's a different problem: there's no ground truth to anchor to in the first place, so a structure-first approach can force an unfamiliar case into the nearest available graph entry — a mistake that's harder to catch precisely because it looks verified.

The sweet spot sits in between — the rare-but-known presentation, where ground truth exists but the base model tends to over-fit the case to the nearest common script anyway. That's exactly where Provocation's anchor-hunting and the graph's differential field earn their cost. The series' sharpest line on this: the highest-leverage fix isn't adding or withholding structure uniformly, it's making "how much ground truth do I actually have for this case" a visible output in its own right. A system that fails loudly — an honest "no strong match" — beats one that fails quietly and confidently, every time.

There's also a category of uncertainty the series is refreshingly upfront about not solving: how sick the patient actually looked walking in the door, what was tried and failed at the bedside, whether the case narrative itself was a faithful capture of the real encounter. No graph, pathway, or evidence layer ever sees that gap. It's not a coverage problem a fourth layer could fix — it's a category the entire documented-representation approach can't reach, full stop.

The turn that makes it usable

Three pieces in, the series has been adding — a second cognitive mode, a graph, a pathway, an evidence layer, a rarity-weighting scheme. Every addition was justified on its own terms. And then the fourth piece does something most frameworks never bother to do: it turns around and asks whether anyone would actually use all of it.

The honest failure mode of a growing framework, as the series puts it, isn't that it's wrong — it's that it becomes something people admire from a distance and never open. So Part 4 proposes a ten-minute weekly loop: write the one-line problem representation from memory, name the single finding you're leaning on hardest, ask what would have to be true for that finding to point somewhere else, check exactly one fact against a source you trust, write one sentence on what you'd do differently. That's it. No graph, no pathway, no rarity tier — just Promption's first move, one Provocation question, and a single spot-check, small enough to survive an actual busy week.

The tell you've reached for too much tooling: you spent longer assembling ground truth than thinking about the patient. The tell you've reached for too little: you can't say, out loud, what would have changed your mind.

Why the shape of the series matters as much as the content

What makes this series worth reading in order isn't any single layer — it's the honesty of the arc. Tooling and claimed rigor climb for three parts straight, and then the fourth part deliberately climbs back down, not because the earlier layers were wrong, but because a framework only teaches you something if you actually open it. That's a rarer instinct than it should be. Most technical writeups about AI-augmented reasoning stop at "here's the architecture" and never get to "here's the version you'll actually run." Vibe Rounds does, and the ten-minute loop is arguably the most quietly ambitious idea in the whole series — not because it's clever, but because it's the one piece designed to survive contact with a real week.

Vibe Rounds CCOS Framework — for educational and clinical-reasoning practice only, not a clinical decision tool.

 

The AI Doctor Said "Rest and Fluids." Here's What It Didn't Ask.

Why the most important skill in the AI-doctor era isn't picking the smartest chatbot — it's knowing which questions it never got around to asking.

---

A 68-year-old man opens a health chat app. He's had a cough for five days — wet, yellow-green phlegm, on-and-off fever. The app asks good opening questions, lands on "probably bronchitis," and recommends rest, fluids, and paracetamol. Reasonable so far.

Then the conversation keeps going. He mentions he's gotten a little breathless walking up his own stairs, something new. He mentions he's a diabetic, ex-smoker. He mentions his energy and appetite have dropped. And, almost as an aside, he mentions that his wife said he seemed confused when he woke up that morning — slow to answer her — though he "feels okay now."

The app's response to that last detail: fatigue and reduced appetite are common with any infection... since you're feeling okay now, that's reassuring.

That case is a synthetic, composite one, built for testing rather than describing a real patient — but the pattern it captures is exactly the mechanism that patient-safety researchers have spent years studying. Doctors have a name for what just happened. It's called premature closure: forming a diagnosis early, then treating every new piece of information as confirmation instead of a reason to reconsider. It's the single most common contributor to diagnostic error in emergency medicine, and it gets more likely, not less, the more confident the diagnosis feels. A morning episode of confusion in a 68-year-old diabetic with a lung infection isn't background noise. It's one of the five factors on the CURB-65 score doctors use specifically to decide who's at risk of dying from pneumonia. The app folded it into "the same overall picture" instead.

This isn't a story about one bad chatbot

It's tempting to read that transcript and think "just use a better app." That misses the scale of what's actually happening. Recent survey data suggests roughly a quarter of U.S. adults — tens of millions of people — have used an AI chatbot for health information or advice, and for a large share of them it's a stand-in for a visit they can't easily afford or access, not just a supplement to one. OpenAI has reported tens of millions of health-related messages a day on ChatGPT alone, with checking symptoms among the single most common uses. This isn't a niche behavior anymore. It's becoming a default first stop.

And regulators are still catching up. The FDA's most recent (January 2026) guidance loosens oversight for clinical decision-support software — but by design, it's aimed at tools clinicians use, where a human is reviewing the logic before anything reaches a patient. Consumer-facing symptom checkers and health chatbots — the ones a worried person opens at 11pm — sit outside that framework almost entirely. There's no equivalent requirement that they flag their own uncertainty, escalate red flags, or justify a "wait and see" plan the way a triage nurse would have to.

The trouble with a chat window is that it feels like a conversation

Shared decision-making — the idea that a medical choice should be a genuine collaboration between clinician and patient, not a verdict handed down — has a well-established structure in clinical training. One widely used framework breaks it into three stages: introducing that there is a choice to make, laying out the real options side by side, and then helping the patient land on a decision that fits their actual situation and values. It works when the professional side of that conversation is holding space for uncertainty and inviting pushback.

A chat interface performs the shape of that conversation — it asks follow-up questions, it sounds warm, it resolves things tidily — without necessarily doing the substance of it. In the transcript above, only one path was ever put on the table: stay home, wait a week. No mention of a same-day evaluation, a pulse oximeter reading, a chest X-ray, or even the phrase "here's what would change my mind." The patient never got to weigh options, because he was never told there were any. That's not a shared decision. It's a single decision, narrated pleasantly.

What actually helps: better questions, not just better answers

We ran this exact transcript through SDM Lens, a free educational tool built by Dr. Avinash Kumar Gupta as part of his Vibe Rounds project. It's worth being precise about what it is and isn't: it doesn't diagnose anything, and it doesn't rank options for a patient. It's a patient-advocacy prep aid — you feed it a case, and it generates the first-person questions a patient or caregiver should be walking into the room with, across seven domains: what's actually being decided, what the full menu of options is, the specific benefits and harms of each, how solid the underlying evidence really is, how the options fit what matters to this patient, the practical logistics of each path, and how reversible the choice is.

Run against this transcript, the tool surfaced exactly the gaps a sharp clinician-in-training is taught to hunt for:

• "Is resting at home for a full week really my only option, or are there other immediate choices — like having my lungs listened to, getting a chest X-ray, or having my oxygen level checked today?"
• "Do the clinical studies on viral bronchitis and home recovery apply to people experiencing new breathlessness or a recent episode of morning confusion — or do those symptoms put me outside the typical evidence base?"
• "Who should my wife or I call, and how quickly can we be seen, if my breathing gets worse or I become confused again — especially after hours?"
• "What is the actual deadline for deciding to get evaluated in person, and what do I risk if I miss that window?"

None of those questions require a medical degree to ask. They just require knowing that they're the kind of question a decision like this deserves — and that's the part a friendly, fast-resolving chat interface can quietly train you out of.

Three questions worth carrying into any AI-doctor conversation

You don't need a tool to start doing this. Three questions do most of the work:

1. "What else could this be, and what would rule it out?" Forces the option list open instead of closing on the first plausible answer.
2. "What's the worst realistic version of this, and how fast could it get there?" Forces harm-side specifics instead of blanket reassurance.
3. "What would make you tell me to go in today instead of waiting?" Forces an explicit trigger and deadline instead of a vague "follow up if it doesn't improve."

If an app — or a person — can't answer those three cleanly, that's information too.

The fix isn't smarter AI alone

AI-doctor apps aren't going away, and for a lot of people they're genuinely better than the alternative, which is often nothing. But "sounds confident and caring" and "has actually weighed your risk" are two different things, and chat interfaces are very good at the first one. Closing that gap will take app designers building in explicit uncertainty and escalation triggers rather than tidy resolutions, regulators extending scrutiny to the consumer-facing tools people actually use at 11pm, and — until both of those catch up — patients and caregivers walking in with a short list of questions that a reassuring answer can't quietly slide past.

The most dangerous sentence in that whole transcript wasn't a wrong diagnosis. It was "that's reassuring." Said kindly, about the one detail that most needed a second look.

---

The case discussed here is a synthetic, composite transcript created for testing and educational purposes — it does not describe a real patient or a real product, and nothing in this piece should be read as medical advice. If you or someone you're caring for has new confusion, breathlessness, or a chronic condition alongside worsening infection symptoms, that combination is worth an in-person evaluation rather than a chat window.

---

Appendix A: Source Chat Transcript (Synthetic, Composite Case LRTI-COUGH-COLD-001)

Reproduced in full below is the synthetic, composite transcript discussed above. It was constructed for testing and educational purposes and does not describe a real patient, clinician, or commercial product.

PATIENT: Hi, I've had a cough and cold for about 5 days now. Can you help me figure out what's wrong?

AI-DOCTOR: Hello! I'm sorry to hear you're not feeling well. I can help you think through this. To start, could you tell me:

1. Is the cough dry or are you bringing up phlegm/mucus?
2. Do you have a fever?
3. Any shortness of breath or chest pain?

PATIENT: It's a wet cough, bringing up yellowish-green phlegm. I had a fever on and off, around 100.5°F yesterday, but I haven't checked today. No real chest pain but I feel a bit tight in my chest when I cough a lot.

AI-DOCTOR: Thanks for that detail. Yellow-green phlegm with fever suggests your body is fighting an infection, most likely a viral upper respiratory infection that's now moved into your lower airways — this pattern is common with a "cold that goes to the chest," often bronchitis. Are you having any trouble breathing when you're just sitting still, or only with the coughing fits?

PATIENT: Mostly only when I cough a lot. But this morning I noticed I get a little out of breath walking up the stairs to my apartment, which wasn't happening before.

AI-DOCTOR: That's useful to know. New exertional breathlessness alongside a productive cough and fever for 5 days does fit with a lower respiratory tract infection, like acute bronchitis. Most cases like this are viral and resolve on their own within 1-3 weeks. I'd recommend:

• Rest and fluids
• Steam inhalation or a humidifier
• Over-the-counter cough syrup or honey for symptom relief
• Paracetamol/acetaminophen for the fever

Do you have any past medical history I should know about — asthma, COPD, heart disease, diabetes, or are you a smoker?

PATIENT: I'm 68. I have type 2 diabetes and mild hypertension, on medication for both. I used to smoke, quit about 10 years ago. No asthma or COPD that I know of.

AI-DOCTOR: Got it, thank you. Given that you're managing your diabetes and blood pressure well, this still looks most consistent with a viral bronchitis. I'd suggest continuing supportive care as above. Antibiotics usually aren't needed for bronchitis since it's typically viral, even with colored phlegm. Keep monitoring your temperature and let me know if things change.

PATIENT: Okay that's a relief. One more thing — I've felt a bit more tired than usual and my appetite has been low. Also my wife said I look a little confused when I woke up this morning, like I was slow to answer her, but I feel okay now.

AI-DOCTOR: Fatigue and reduced appetite are common with any infection, so that fits the overall picture. Since you're feeling okay now, that's reassuring. Continue rest, fluids, and the supportive measures I mentioned. Follow up with your regular doctor if symptoms haven't improved in a week.

PATIENT: Should I be worried about my age or the diabetes making this worse?

AI-DOCTOR: It's good that you're being cautious, but based on what you've described, this seems like a typical case that should improve with home care. Just keep an eye on your temperature and energy levels over the next few days.

PATIENT: Alright, thank you, that's helpful. I'll rest up.

AI-DOCTOR: You're welcome! Feel better soon. Reach out again if anything changes.

---

Appendix B: SDM Lens Output (7-Domain Shared Decision-Making Query Generator)

The following is the structured output generated by SDM Lens (Vibe Rounds, CC BY 4.0) when run against the transcript above. It is reproduced as generated: patient-voiced questions across seven domains, followed by a Phase 3 synthesis debrief. SDM Lens generates questions only — it does not recommend treatment or rank options.

Domain 1 — The Decision Itself

Core Decision Clarification Questions

1. What exactly am I being asked to decide right now — am I choosing to stay home with over-the-counter care, or am I deciding whether I need to be evaluated in person by a doctor today?
2. Is this decision something I need to make right now, or do I safely have time to wait a day or two to see if my cough and breathing improve?
3. Who is ultimately making this decision — is it entirely up to me and my wife, or is there a clear medical direction I should be following?
4. What could happen to my health if I choose not to make a decision today and simply carry on as I am for the next few days?
5. Is choosing to "wait and see" at home actually a deliberate decision with its own risks, given my age and diabetes?
6. Since my wife noticed I was confused this morning, should she and I be making this decision together rather than me deciding on my own?

Questions Testing for False Binaries and Unmentioned Options 7. Is resting at home for a full week really my only option, or are there other immediate choices like having my lungs listened to, getting a chest X-ray, or having my oxygen level checked today? 8. Am I stuck choosing between staying home or going to the hospital, or is there a middle option like visiting an urgent care clinic or scheduling a same-day appointment with my regular doctor? 9. Is the recommendation to rest at home being given because it is truly the safest option for my specific health background, or is it just the standard option available through an online chat? 10. Could we consider a middle-ground approach — like monitoring my temperature and oxygen at home today and checking in with a doctor tomorrow — rather than waiting a full 7 days to follow up?

Domain 2 — Options on the Table

1. Given my age, my diabetes, my new shortness of breath on the stairs, and the episode of morning confusion my wife noticed, what are all the management options available to me right now beyond staying home and resting?
2. Is getting an immediate, same-day in-person medical evaluation — such as at a clinic, urgent care, or emergency room to check my oxygen levels or get a chest X-ray — an option I should consider today?
3. Are there non-pharmacological options or home-monitoring devices, like using a home pulse oximeter to track my oxygen, that I haven't been told about yet?
4. What would happen to my health over the next few days if I choose to do nothing beyond basic home monitoring and supportive care?
5. Are there prescription options, such as antibiotics or targeted treatments, that exist for my situation if an in-person evaluation shows something beyond viral bronchitis, and how would we decide if I need them?
6. Are there options for urgent specialist or hospital-based evaluations that exist but aren't being offered here, particularly given my episode of confusion and underlying health conditions?
7. For continuing supportive home care, what would my day-to-day life actually look like over the next few days?
8. For seeking an immediate, same-day in-person medical evaluation, what would my day-to-day life actually look like during and right after that visit?
9. For starting prescription medication (such as antibiotics, if an in-person checkup shows a bacterial lung infection like pneumonia), what would my day-to-day life actually look like?
10. In plain terms, can you describe what a "good outcome" and a "bad outcome" would look like for each of these options?

Domain 3 — Benefits & Harms

Benefit-Side Questions

1. If I follow the recommended home care plan, what specifically should improve first, and by what day should I expect my fever, cough, or energy level to noticeably get better?
2. Out of 100 people my age who have diabetes and present with a productive cough, fever, and new shortness of breath on stairs, roughly how many recover fully with just supportive home care versus how many require prescription treatment or in-person evaluation? (Specific statistics for this exact subgroup are not provided in the case transcript.)
3. Is the benefit of staying home and resting focused solely on helping me feel better, or does it also reduce my risk of severe complications like pneumonia or hospitalization?
4. What does "success" with home supportive care look like in my actual day-to-day routine?

Harm-Side Questions 5. What are the most common side effects or risks of relying only on home care when I have underlying conditions like type 2 diabetes and a history of smoking? 6. What is the worst realistic outcome if this infection turns out to be something more serious than viral bronchitis, such as pneumonia, and how quickly could my symptoms or mental clarity worsen at home? 7. Are there specific functional losses or red-flag symptoms — such as worsening fatigue, loss of independence, or repeated episodes of confusion like the one my wife noticed — that could develop if an infection goes unmonitored? 8. (Note: Long-term outcome data is not detailed in the case transcript.) What potential long-term risks or delayed complications could arise if a lower respiratory infection in an older diabetic patient is not evaluated in person or treated promptly?

Synthesis Question 9. Has a healthcare professional actually weighed the safety of managing these symptoms at home against the risks of a missed or worsening chest infection given my age and medical history, or is that balance of gains and risks being left for me to figure out on my own?

Domain 4 — Certainty & Evidence Quality

1. Is the suggestion that my chest symptoms are just viral bronchitis based on strong research evidence, or is it more of a general assumption for cases with cough and fever?
2. Is there solid evidence showing that home supportive care alone is effective and safe for someone with my specific health background — being 68 years old, having type 2 diabetes, and being a former smoker?
3. Do the clinical studies on viral bronchitis and home recovery apply to people who are experiencing new breathlessness when walking up stairs or a recent episode of morning confusion, or do those symptoms put me outside the typical evidence base?
4. How much evidence is there that yellow-green phlegm and fever will clear up on their own without antibiotics in older adults with diabetes compared to younger, healthier populations?
5. What critical clinical information — such as a physical lung examination, oxygen level measurement, or chest imaging — are we currently missing that could completely change this diagnosis?
6. Are the typical recovery timelines you mentioned (1 to 3 weeks) based on general national averages, or do they specifically reflect outcomes for individuals with underlying medical conditions like mine?
7. If I were evaluated in person by my primary care physician or an emergency specialist, is there research or guideline evidence suggesting they might reach a different conclusion or recommend different testing?
8. What specific signs or changes in my evidence of recovery (such as worsening fatigue, persistent fever, or recurrent confusion) would indicate that the initial assumption of a simple viral illness was incorrect?

Domain 5 — Fit With What Matters to Me

1. What matters most to me right now — staying comfortably at home to rest and treat this like a simple chest cold, or getting an in-person medical evaluation to be completely certain this infection isn't worsening given my age and diabetes?
2. What would I be most afraid of losing if this turns out to be something more serious than bronchitis — such as pneumonia — and I delay getting checked out: my independence, my current health stability, or my peace of mind?
3. Is there a line I would not want crossed regarding my safety, such as ignoring new warning signs like my shortness of breath on the stairs or my wife's observation that I seemed confused this morning, just to avoid an extra medical visit?
4. Whose voice do I want in this decision with me — should I be giving more weight to my wife's concern about my morning confusion and slowed responses, rather than relying solely on how I feel at this exact moment?
5. Given that keeping my health stable with my diabetes matters most to me, is staying home with supportive care actually built around protecting me from potential complications, or does an in-person exam fit that priority better?
6. Did anyone ask me what level of risk I am comfortable taking at home before recommending that I just wait a week, or am I following advice that technically fits a viral cold but doesn't fit how cautious I want to be about my health?

Domain 6 — Practical & Logistical Reality

1. If I choose to stay home with supportive care versus going to a clinic for an in-person evaluation or chest X-ray today, how much time will each option take, including travel and waiting time?
2. How long should I expect my total recovery time to take before I can safely return to my normal daily activities and responsibilities?
3. What are the out-of-pocket costs for the recommended home supplies — like a humidifier, thermometer, or over-the-counter medicines — and would an in-person clinic or urgent care visit be covered by my insurance?
4. Since my wife noticed I was confused this morning, will she need to take time off to stay home and monitor me, and what specific warning signs should she be watching for?
5. Has anyone checked with my wife to see if she is available and able to assist me at home while I am sick?
6. How will resting for 1 to 3 weeks affect my daily routine, including my ability to manage and take my regular diabetes and blood pressure medications?
7. What practical equipment or home adjustments do I need right away — such as a pulse oximeter to check my oxygen levels or assistance getting up the stairs to my apartment while I am short of breath?
8. Exactly who should my wife or I call, or which facility should we go to, if my breathing gets worse, my fever returns, or I become confused again after regular office hours or over the weekend?
9. Is there a decision guide, nurse hotline, or patient navigator available to help us, or can I have a second conversation with a healthcare provider after taking time to discuss these options with my wife?

Domain 7 — Reversibility & Next Steps

1. If I choose to follow the home care plan with rest and over-the-counter medication now, can I change course and seek an in-person medical evaluation later if I don't feel right?
2. Is the decision to wait a full week before following up permanent, or can this plan be revisited sooner if my breathing changes or if I have another episode of confusion?
3. If I choose to wait and monitor my symptoms at home for now, does that close off any treatment options — such as prescription medications or chest imaging — if this turns out to be something other than viral bronchitis?
4. Given my age, diabetes, exertional breathlessness, and the morning confusion my wife noticed, what is the actual deadline or timeframe for deciding to get evaluated in person, and what risks do I take if I miss that window?
5. If I decide to seek an in-person evaluation right away, what happens next step-by-step?
6. How and when will I know if the home supportive care — like rest, fluids, and paracetamol — is actually working to resolve the infection?
7. Who should I contact if I change my mind about waiting at home, and how quickly can I get an appointment or be seen?
8. Can I get a written summary of this conversation and recommendations so my wife and I don't have to rely on memory alone to monitor my symptoms?

Phase 3 — Reflection Debrief

[Remember] A question that a learner might not have thought to ask without this framework is from Domain 4 (Certainty & Evidence Quality, Question 3): "Do the clinical studies on viral bronchitis and home recovery apply to people who are experiencing new breathlessness when walking up stairs or a recent episode of morning confusion, or do those symptoms put me outside the typical evidence base?" Learners often recognize that a diagnosis is being made, but fail to ask whether the general evidence base actually applies to a patient presenting with atypical high-risk features and red flags.

[Analyse] The original case data was presented as a decision already made and merely being explained, rather than a genuine choice. We know this because the AI-Doctor anchored early on "viral bronchitis," systematically normalized every emerging red flag (new exertional dyspnea, age/diabetes risk, and transient morning confusion) as typical symptoms of a mild illness, and provided a single pre-determined path: supportive home care for 7 days. At no point were alternative pathways (e.g., same-day clinic visit, pulse oximetry, urgent care evaluation, or chest imaging) offered as viable choices for the patient to weigh.

[Evaluate] If this patient enters their next medical interaction with only these questions, the single biggest way their outcome could improve is by disrupting premature diagnostic closure. In an elderly patient with diabetes, new breathlessness, and confusion, simple reassurance carries a real risk of missing severe conditions like pneumonia, hypoxia, or early sepsis. By raising these specific, structured questions, the patient forces the clinician to directly re-evaluate high-risk symptoms, perform essential objective checks (such as physical lung examination and oxygen saturation), and explicitly justify the safety of home management versus an immediate in-person assessment.

Generating good questions on someone else's behalf, without putting words in their mouth, is one of the hardest and most protective advocacy skills in medicine.

SDM Lens is a Vibe Rounds tool · CC BY 4.0 · Educational use only, not a clinical decision aid.