Clinical reasoning and patient safety

Two modes of clinical thinking

Experienced clinicians switch between fast pattern recognition (“this looks like pneumonia”) and slow analytic thinking (“what else could cause fever and focal crackles?”). Students need both — and need to know when to slow down.

Building a defensible differential

A differential is a working tool, not a trivia list. Examiners reward clinicians who can explain why a diagnosis is likely and what would change their mind.

• Start from the presenting complaint, not a premature label
• Group causes by mechanism (vascular, infectious, inflammatory, traumatic, metabolic…)
• Rank by probability and by danger — not the same list
• Use one or two “must not miss” diagnoses per presentation
• State what history, exam, or tests would discriminate

Common reasoning errors

• Anchoring on the first plausible idea
• Premature closure before testing alternatives
• Availability bias after a memorable case
• Confirmation bias — seeking only supporting data
• Ignoring base rates in your population

Red flags and safety netting

Red flags are findings that should lower your threshold for serious disease or urgent action. They are complaint-specific — chest pain, headache, back pain, and abdominal pain each have their own can’t-miss lists.

Safety netting means telling the patient what to watch for and when to return — even when you think the diagnosis is benign.

Practising reasoning deliberately

Case-based simulation forces you to verbalise your thinking, request data, and update your plan — the same skills assessors watch in OSCE and ward rounds.

After each case, review what you missed, which alternative diagnoses you failed to consider, and which questions would have changed management.