Differential Diagnosis

Why it matters

You have one observation — a symptom, a pattern, a thing that is plainly wrong — and several explanations that could each account for it. The pull is to grab the first explanation that fits and stop. Differential diagnosis is the discipline that refuses that shortcut: it makes you write out the whole list of candidate explanations before committing to any one, then narrow the list with the specific pieces of evidence that tell the candidates apart — weighing each by how common it is and by how dangerous it would be to miss.

For example: a patient arrives with chest pain. The candidates are not equal. Heartburn and a pulled chest muscle are common; a heart attack and an aortic tear are rarer but lethal. A lazy read lands on heartburn because heartburn is common and the pain is mild — and occasionally kills the patient whose mild pain was a heart attack. The differential forces both questions at once: what is most likely (base rates) and what would I most regret missing (the can’t-miss diagnoses). So the clinician orders the one test — an ECG, a specific blood marker — that separates the harmless common cause from the deadly rare one, and only then narrows. The skill is not guessing the answer; it is building the list and then knowing which single observation collapses it.

What it reveals. The full slate of plausible explanations for one observation, ranked by likelihood and pruned by the evidence that actually discriminates between them — so the leading candidate is the one that survived the alternatives, not just the first that came to mind.
How it changes the read. You stop asking “what could this be?” and start asking “which competing explanation does the evidence rule out, and what single observation would settle the rest?”
When to foreground it. A concrete symptom or pattern with a small set of rival explanations — two to five — where you want a fast, honest narrowing rather than an exhaustive proof, and where you can name the evidence that tells the candidates apart.
What you’d miss without it. The lethal-but-unlikely candidate you never wrote down — and the fact that your confident first answer was never tested against the explanation that predicts the exact same symptom.
Where it misleads. Pushed too fast it closes early — locks onto the vivid or the familiar before the discriminating test is run — and a light apparatus can drop a candidate that deserved to stay alive; where stakes are high or evidence is deliberately hidden, the fuller competing-hypotheses discipline is the right tool.

Realtime examples

See real, dated analyses where this mode narrowed a set of competing explanations down to the most likely one → Differential Diagnosis on Main Street Independent

How to invoke it in Ora

You have a symptom or pattern and a handful of explanations that could each account for it — ideally two to five — and you want a quick, honest narrowing rather than an exhaustive proof.

State the observation concretely, list the candidates, and ask:

“Differential diagnosis — which of these is most likely? [observation, stated precisely] Candidate explanations: [your short list].”

The phrase differential diagnosis, together with a named symptom and a small slate of candidate explanations, is what routes you here. Bring the observation in specific terms — “intermittent 502 errors, but only on Tuesday mornings, database CPU normal” beats “the site is flaky” — and bring the candidates as an actual list, because the mode’s whole job is to tell those explanations apart. If you have only one explanation there is no differential to make; if you have many more than five, the mode will point you to the fuller competing-hypotheses treatment.

Two boundaries worth knowing. If the stakes are high enough that prematurely dropping a candidate is dangerous — adversarial settings, security-critical calls, situations where evidence may be concealed — the heavier competing-hypotheses mode, with its strict disconfirmation discipline, is the right tool. And if the real question is not “which explanation” but “how should my probability shift as new evidence arrives over time,” that is conditional-probability reasoning and routes to the Bayesian hypothesis network. This mode gives you a fast, calibrated narrowing; it does not run the full matrix or the probability math.

How it works

The method comes straight from the bedside, where a physician meets an ambiguous symptom and cannot afford either to dither or to guess. A patient presents with a cough that has lasted three weeks. The cough is the presenting symptom — the fixed thing every explanation has to account for. The first move is not to name the most likely cause; it is to generate the whole list, the “differential”: a lingering viral infection, asthma, acid reflux, a side effect of a blood-pressure drug, pneumonia, tuberculosis, lung cancer. That list is the entire point. The discipline is to write down candidates you do not believe before you commit to the one you do, because the explanation you never named is the one that gets missed.

Then the clinician narrows — not by piling up evidence that fits the favorite, but by hunting for discriminating findings, the observations that point toward one candidate and away from another. The same fact can rule a candidate in or out: a normal chest X-ray largely rules out pneumonia and a tumor; a cough that vanishes when a particular pill is stopped implicates the drug; night sweats and weight loss pull tuberculosis and cancer up the list. Each discriminating finding collapses part of the differential. Evidence that every candidate predicts equally — the patient feels tired — is nearly worthless here, because it separates nothing. The good test is the one whose result you cannot already predict, the one that will send the list one way or the other.

The narrowing runs on two axes at once, and holding both is the craft. The first is probability: which candidates are common in this kind of patient, and which are rare. Medicine has an aphorism for it — when you hear hoofbeats, think horses, not zebras. Most three-week coughs are the dull common things, and a method that chases the exotic on every case wastes everyone’s time and money. But probability alone is a trap, because the second axis is danger: some candidates are unlikely yet lethal if missed — the “can’t-miss” diagnoses. So the rule is not simply “bet on the horse.” It is: think horses and still rule out the lethal zebra. You do not have to believe the patient has cancer to order the one test that excludes it; you order it precisely because the cost of missing it dwarfs its low odds. A differential that ranked only by likelihood would quietly drop the rare killer. A good one keeps it on the list until a discriminating finding clears it.

None of this is special to medicine; medicine just refined it first. Any time a system fails and several causes could explain the same symptom, the same three moves apply. An online service throws errors only on Tuesday mornings: list the candidates — a weekly cron job, a batch data load colliding with traffic, a routing quirk at the network edge, a customer’s scheduled scrape, a cold-start stampede when the system scales up — then find the discriminating observation. Does the error track a specific job’s start time? Does it survive when that job is paused? Weigh the common cause (a routine job spike) against the costly-but-unlikely one (a silent data corruption), and order the cheap check that tells them apart before you commit. The presenting symptom, the full candidate list, the discriminating findings, the twin ranking by likelihood and by cost-of-being-wrong — that is differential diagnosis, whether the patient is a person or a server.

Framework & implementation

This section uses Ora’s own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.

Pipeline execution

Differential Diagnosis is an atomic mode in the hypothesis-evaluation territory — a single evaluative pass, not a composite of sub-analyses. It is the depth-light member of the territory: the medical-tradition sibling of full Analysis of Competing Hypotheses, running the same operation (weighing candidate explanations against observed evidence) with a looser apparatus and a faster pass. It runs at Gear 4, Ora’s most thorough setting: a Depth analyst and a Breadth analyst work the symptom in parallel and then critique each other (cross-adversarial evaluation) before a consolidator integrates the result — the breadth pass guards against an incomplete candidate list, the depth pass against a sloppy discriminating-evidence read.

The pass does five things in order. It locks the observation — the symptom or pattern being explained, stated precisely enough that the candidate explanations have a fixed target. It generates the candidate hypotheses — typically two to five; fewer than two and there is no differential to make, more than five and the mode recommends routing to the fuller competing-hypotheses matrix. It applies base-rate reasoning — which candidates are common in the relevant reference class and which are rare, narrowing the field by prior probability before evidence is weighed (the horses-not-zebras move). It weighs the evidence against each candidate with attention to discriminating evidence specifically — the findings that point toward one candidate and away from another — rather than confirmatory evidence broadly. Finally it produces a ranked output naming the most likely explanation, the runner-up, and the conditions under which the ranking would change.

The load-bearing discipline is the base-rate / evidence-update balance, and it shows up directly in the mode’s reasoning lenses. Base-rate neglect is the corrective that keeps a vivid rare candidate from being over-weighted on thin evidence (and, read the other way, keeps the lethal zebra on the list rather than dismissed for being unlikely); anchoring is the corrective against premature closure on the first-considered diagnosis. Together they enforce the rule that the prior decides which candidates are worth taking seriously and the discriminating evidence decides among the survivors.

Output contract

The deliverable is a fixed set of sections, so the differential is auditable rather than a narrative: Candidate Hypotheses (each candidate stated, with its base rate in the relevant reference class), Evidence Observed (each piece of evidence and which candidates it bears on), Diagnosticity Per Hypothesis (a finding-by-candidate read marking each as discriminating-positive, consistent-with, inconsistent, or rules-out — the discriminating-findings work made explicit), Ranking with Reasoning (the candidates ordered, each with why it sits where it does, including the rare-but-retained “can’t-miss” candidates and the red flags that would promote them), Disconfirming Tests for Top Two (the cheapest observation that would confirm or break each leading candidate, with its cost and the evidence-shift each result implies), and Confidence per Ranking with an explicit evidence-sufficiency flag — the mode’s commitment to say, plainly, when the evidence is too thin to discriminate and to name the single observation that would settle it.

Origin and evidence

The method is the formalized version of what physicians have done at the bedside for two centuries — the clinical diagnostic reasoning taught in the bedside tradition of William Osler and carried into modern practice. Its contemporary backbone is evidence-based medicine: David Sackett and colleagues’ Evidence-based Medicine: How to Practice and Teach EBM (2000) supplied the discipline of weighing each candidate against the actual likelihood ratios of the available findings rather than impression — the rigor that turns a hunch-driven differential into a defensible one. The mode’s failure-mode awareness comes from the diagnostic-error research of Pat Croskerry, whose dual-process account of clinical reasoning — Clinical cognition and diagnostic error (2009) and A Universal Model of Diagnostic Reasoning (2009) — catalogued exactly how differentials go wrong: anchoring on the first diagnosis, premature closure, base-rate neglect for vivid rare conditions. The mode’s base-rate / evidence-update balance is a direct response to that catalogue.

Applications and common uses

Technical incident triage. A concrete fault — intermittent errors, latency spikes, a service degradation — with a short list of candidate causes, narrowed by the one cheap check that tells them apart.
Hardware and equipment troubleshooting. A misbehaving machine — a furnace short-cycling, a fan running constantly — where several mechanisms could produce the symptom and the diagnostic move is to find the discriminating observation.
Operational and business diagnosis. A drop in a metric, a recurring complaint pattern, a process that intermittently fails, with two-to-five plausible explanations and a need to act before an exhaustive study is feasible.
Everyday and personal problem-solving. Any ambiguous symptom — in a device, a pet’s behavior, a household system — where the disciplined list-then-narrow beats grabbing the first explanation that fits.
The actual clinical and veterinary differential. The native use the apparatus is borrowed from, applied to its home domain.

Failure modes and when not to use it

Premature closure. The signature error: locking onto the first plausible candidate and stopping before the discriminating test is run. The mode mitigates by forcing the full candidate list and the diagnosticity read, but the vulnerability is real and the user should treat a narrow lead as provisional.
Base-rate neglect — both directions. Over-weighting a vivid rare candidate on thin evidence, or dismissing the lethal zebra for being unlikely. The mode’s explicit base-rate step and its retention of can’t-miss candidates are the guard.
Light-apparatus elimination. Because the mode trades the strict disconfirmation-counting of full ACH for speed, it can drop a candidate that deserved to stay alive. That tradeoff is acceptable for low-stakes narrowing and wrong for high-stakes work — which is the next point.

When not to reach for it. When the real question is how a probability should update over time as new evidence arrives — conditional, network-structured reasoning — route to Bayesian Hypothesis Network. When the problem is a many-hypothesis intelligence or analytic question where prematurely eliminating a candidate is dangerous, or where evidence may be deliberately concealed, route to Analysis of Competing Hypotheses, which runs the strict disconfirmation matrix this mode deliberately skips. And when the task is not weighing rival explanations but tracing a single failure’s causal chain back to its origin, that is Root Cause Analysis, not a differential.

Analysis of Competing Hypotheses — the depth-thorough sibling in the same territory: when prematurely dropping a candidate is too dangerous, it runs the strict consistent/inconsistent disconfirmation matrix this mode skips for speed.
Bayesian Hypothesis Network — the depth-molecular sibling: when the question is how probabilities should update over time through a network of conditional dependencies, not a one-pass narrowing.
Root Cause Analysis — the cross-territory neighbor for when the task is tracing a single failure’s causal chain back to its origin, rather than weighing several rival explanations for one symptom.
Base Rate Neglect — the core lens this mode loads: the horses-not-zebras discipline that decides which candidates are even worth taking seriously, paired with the Anchoring corrective against closing on the first diagnosis.