How to Play a Diagnosis Game (and Learn From Every Clue)

Before naming a condition, create a problem representation: a compact sentence that preserves the features most likely to matter. Include the patient type or context, the time course, the main syndrome, and one or two defining findings. Leave out decorative details until they prove useful.

For example, “young adult with acute unilateral eye pain, photophobia, and a small irregular pupil” is more usable than repeating every sentence in the vignette. Compression forces you to decide which facts are signal and gives your memory a cleaner pattern to match.

List two or three diagnoses that could reasonably explain your summary. The goal is not to inventory every possible condition. A short differential gives you alternatives to compare and reduces the temptation to treat your first idea as settled.

If nothing comes to mind, switch from disease names to categories: infectious, inflammatory, medication-related, neurologic, mechanical, behavioral, or another framework appropriate to your field. Once you have a category, retrieve a few representative conditions within it.

Not every detail deserves equal weight. Look for a discriminating clue: a finding that is substantially more expected under one diagnosis than the others. Time course, laterality, a specific examination sign, a medication exposure, or the absence of an expected symptom can do more work than a long list of nonspecific complaints.

In a progressive-clue game, decide what information would most change your ranking before you reveal more. Then compare that expectation with the next clue. This turns each reveal into an update rather than another fact added to a pile.

Enter the diagnosis when one option explains the case better than its competitors. Before submitting, finish this sentence: “I am choosing X because A and B fit, while C makes Y less likely.” That ten-second explanation exposes weak pattern matching and makes a wrong answer easier to analyze.

Do not wait for absolute certainty. Educational cases are designed around the most likely answer from the provided evidence. The productive challenge is deciding when the case has crossed from plausible to sufficiently supported.

After the answer, compare your reasoning with the case. Did you lack the relevant fact, misread a clue, anchor on your first hypothesis, or know the answer but fail to retrieve it? Those are different problems and call for different follow-up.

Write one takeaway you could use in a future case. A useful note is comparative—“Unlike X, Y usually has…”—because diagnosis depends on separating neighbors. Then stop. A concise review preserves the daily habit and leaves deeper reading for the conditions that genuinely need it.