Case Summary: A 69-year-old South Asian woman with decompensated liver cirrhosis, ascites, and severe diarrhoea. The clinical paradox at the centre of this case: would stopping the diarrhoea raise ammonia levels dangerously?
These documents apply the VibeRounds framework — a structured, Socratic AI paradigm — to a complex real-world clinical case. They simultaneously serve two audiences:
Critical documentation failures in this case — including missing medication lists and absent ascitic fluid lab results — are treated not as minor oversights but as patient safety hazards.
| Need | How the Documents Address It |
|---|---|
| Validation | The husband’s question about diarrhoea and ammonia is recognised as a sophisticated clinical insight, not a layperson’s worry |
| Plain-language explanation | Complex terms like ascites and hepatic encephalopathy are translated into lay language |
| Safety guidance | Specific red flags (confusion, dark urine, blood vomiting) are listed with clear “if-then” action steps |
| Structured advocacy | Exact questions for the family to ask doctors are provided (e.g. “Was the ascitic fluid sent for a cell count?”) |
| Holistic care | Social prescriptions — fall prevention, home modifications, nutritional support — are included alongside medical management |
| Learning Objective | How the Documents Address It |
|---|---|
| Clinical paradoxes | The bidirectional diarrhoea–ammonia relationship is explained mechanistically |
| Documentation gaps | The case illustrates how an undocumented ascitic tap result creates a “diagnostic void” |
| Diagnostic anchoring | Students are taught to investigate atypical features (lymphadenopathy, pneumothorax) rather than attribute everything to cirrhosis |
| Illness script matching | Students compare the patient’s features against the classical decompensated cirrhosis script to identify mismatches |
| Communication skills | Structured frameworks (e.g. SPIKES) for goals-of-care conversations are included |
| System failure recognition | A decade of falls is reframed as a preventable system-level failure, not bad luck |
This is the central clinical puzzle of the case. Diarrhoea has a bidirectional relationship with ammonia in liver disease:
Diarrhoea as Treatment: Lactulose — the standard drug for hepatic encephalopathy — works by causing diarrhoea, which flushes ammonia out of the gut before it can be absorbed into the bloodstream.
Diarrhoea as Danger: At 15–16 stools per day, diarrhoea causes:
Clinical Decision Required: Is the diarrhoea therapeutic (lactulose working) or pathological (causing a crisis)? The answer changes management completely.
The documents identify two categories of failure:
Procedural Gaps
Systemic Gaps
Lymphadenopathy (swollen lymph nodes) is not a typical feature of cirrhosis. Its presence should trigger a parallel diagnostic workup:
The documents explicitly teach students to resist “dominant diagnostic frame” thinking — the assumption that cirrhosis explains every finding. Atypical features are flags, not footnotes.
Over ten years, this patient experienced recurrent falls and fractures. The documents reframe this history as a preventable system-level failure, involving:
The lesson: recurrent events in the same patient are signals of a system failure, not personal misfortune.
These documents operate simultaneously at multiple cognitive levels:
| Level | Estimated Intuitive Time | Core Cognitive Task |
|---|---|---|
| MBBS Student | Weeks to a semester | Understanding mechanisms (how lactulose works, what ascites is) |
| MBBS Doctor | 2–3 days | Identifying documentation gaps; retrospective data recovery |
| MD Specialist | 4–8 hours | Ruling out atypical diagnoses; polypharmacy audit; MELD/Child-Pugh scoring |
| DM Sub-Specialist | 1–2 hours | Resolving the ammonia paradox; fluid management precision |
| PhD / Systems Designer | Years of experience | Identifying system-level failures; designing the protocol itself |
Important distinction: These timings reflect intuitive cognitive work — the mental effort to reach the insight. They do not include the time required to formally document, structure, and present the analysis as a multi-module report.
The RPD model describes how expert clinicians make fast, accurate decisions in time-critical situations — not by running through all possibilities, but by recognising familiar patterns and mentally simulating the most effective response.
For this patient, the RPD sequence is:
The RPD model is embedded as Module 20 of the VibeRounds protocol. It is what allows a senior clinician to act correctly in the first hour of a crisis, even when lab results are still pending.
Yes — and the protocol is designed explicitly to support this.
When you prompt an LLM to apply Module 20 (RPD), it shifts from “slow” academic summarisation to “fast” pattern-driven clinical reasoning. You can use an LLM in two modes and compare the outputs:
| Mode | Prompt Instruction | Output Type |
|---|---|---|
| Fast (RPD) | “Apply Module 20: RPD model to this case” | Emergency priorities; immediate action plan |
| Slow (Full Analysis) | “Run the full 20-module VibeRounds analysis” | Deep diagnostic exploration; atypical feature investigation |
Comparing both outputs produces a best synthesis — one that balances speed with diagnostic completeness.
The 6-stage pipeline forces an LLM to make its reasoning visible:
This prevents “black box” outputs where the LLM reaches a conclusion without showing its reasoning chain.
The documents function as a structured possibilities map — a clinical checklist that an expert can review and annotate as:
This is particularly powerful at the “diagnostic void” points — where the documents explicitly flag that a decision cannot be made until missing data (like the ascitic fluid result) is retrieved.
| Resource | Limitation |
|---|---|
| Clinical records | Documented what happened, not what it meant |
| Medical textbooks | Described ideal illness scripts; poor guidance on atypical presentations |
| Caregiver interaction | Treated as a communication task, not a clinical data source |
| AI outputs | Black-box conclusions without traceable reasoning |
| Dimension | Old Approach | VibeRounds Approach |
|---|---|---|
| Symptom documentation | “Patient has diarrhoea” | Diarrhoea mapped as a causal network with bidirectional risk |
| Recurrent events | Treated episodically | Identified as a decade-long system failure requiring a case coordinator |
| AI reasoning | Opaque output | 6-stage explainability pipeline with human annotation layer |
| Discharge planning | Written for doctors | Advocate Debrief translates findings into caregiver safety language |
| Caregiver input | Managed or dismissed | Recognised as a high-value clinical data source |
The core gap: the distance between managing a disease and advocating for a human being.
The following questions emerged during the educational analysis and reflect the layered complexity of the case:
Mechanistic
Diagnostic
Systems
Advocacy
These documents represent a transition in clinical knowledge architecture — from fragmented records to integrated reasoning frameworks. They serve as:
The VibeRounds Master Case Analysis Protocol v1.0 (June 2026) encodes expert clinical intuition into a transparent, annotatable, multi-level educational structure — accessible to an MBBS student, useful to a DM specialist, and extensible for AI integration.
| *Framework: VibeRounds Master Case Analysis Protocol v1.0 | Dr. Avinash Kumar Gupta | June 2026* |
| *Case Type: Decompensated Liver Cirrhosis with Multisystem Complexity | CARE-format reportable* |