Home

Reminder

Don't repeat everything.
Learn to summarize common clinical patterns correctly.

The gap Most learners can list findings fluently. Very few can distill those findings into a clinical pattern. The gap between listing and summarizing is the gap between data collection and clinical thinking.
The principle Description is detailed. Summary is conceptual. Converting concrete details into a clinical pattern is the cognitive step that makes differential diagnosis possible.
The test If you cannot express the core clinical problem clearly and precisely in a brief summary, it may indicate that you have not yet fully understood how the findings fit together.
Pattern recognition

In this chapter, pattern recognition refers to the deliberate construction and naming of clinical patterns from findings. With experience, this process becomes faster and more intuitive.

Description: observation

Detailed

"Her right knee joint is swollen and painful. The joint is warm to touch and there is redness over it. She is limping and refuses to weight-bear."

→ Clinical
abstraction
Summary: thinking

Conceptual

"Unilateral monoarthritis involving a weight-bearing large joint."

The summary transforms a cluster of observations into a diagnostic category, opening the door to a focused differential.

Examples

Raw data → Summary → Diagnostic direction

01

Symptomatic Anemia

Raw data
  • Pallor
  • Fatigue and lethargy
  • Reduced activity tolerance
  • Low hemoglobin on FBC
Clinical summary

"Symptomatic anemia."

Diagnostic direction

"Symptomatic" is critical. It tells the clinician this is not an incidental finding. It demands a cause, and it shapes the management decision.

02

Thrombocytopenic Bleeding

Raw data
  • Petechiae over limbs
  • Mucosal bleeding (gums)
  • No fever, no organomegaly
  • Low platelet count on FBC
Clinical summary

"Thrombocytopenic mucocutaneous bleeding without systemic manifestation."

Diagnostic direction

The summary immediately suggests a platelet disorder, most likely ITP. Other causes such as dengue, leukemia, or aplastic anemia are still possible, but the absence of fever and organomegaly makes these less likely. This helps narrow the differential diagnosis and guide the next steps in management.

Levels of Thinking

Four levels: where are you, and where do you need to be?

1

Listing Findings

Reciting observations in the order they were gathered. No grouping, no interpretation, no direction. This is data collection, necessary but not yet clinical thinking.

"Pallor. Fatigue. Low hemoglobin. Petechiae. Mucosal bleeding. Low platelets. Abdominal distension."
2

Grouping Findings

Recognizing that findings belong together: that pallor, fatigue, and low Hb form a cluster, and that petechiae, mucosal bleeding, and low platelets form another. Grouping is the first act of pattern recognition.

"There is an anemia picture and a bleeding picture, and they are occurring together."
3

Naming the Pattern

Attaching a clinical label to the grouped findings. This is summarizing competency. The name should describe the clinical state, not assume the diagnosis.

"Pancytopenia with symptomatic anemia, recurrent infections and bleeding manifestation with no organomegaly or lymphadenopathy."
Target level for this note
4

Linking Pattern to Differential

Using the named pattern to generate a focused, ranked differential diagnosis. The pattern determines which diagnoses are plausible, and which are not. This is where Differential Diagnosis begins.

"Pancytopenia in a child: consider aplastic anemia first. Also consider severe infection, leukemia and infiltrative marrow disease."
Structure

What a good summary contains

A structured reference

Seven elements of a good clinical summary

1

Demographics

Always include

Age, sex, and relevant background. Age immediately activates disease probability: the same pattern means different things at different ages. Duration of illness belongs here too: acute vs. subacute vs. chronic reshapes the differential before any other feature is considered.

"A 7-year-old boy, previously well, with a 5-day history…"
2

Presenting Problem

Always include

The primary complaint and the system it implicates. This anchors the differential to the correct domain of medicine before any findings are presented. Multi-system involvement should be named here when it is part of the presenting picture.

"…presenting with acute pain and swelling of the right knee…"
3

Key Positive Findings

Selectively

The one or two findings that are diagnostically decisive, not a repetition of all positives. Only include what actively shapes the differential.

"…with fever, inability to weight-bear, and a warm, erythematous joint…"
4

Pertinent Negatives

When important

Deliberately stated absences that narrow the differential. Only include negatives that actively exclude a significant diagnosis.

"…in the absence of trauma, skin rash, or prior joint disease…"
5

Key Investigation Results

When available

Results that change the clinical picture, not a recitation of the full panel. Include only investigations that confirm, refine, or reframe the pattern.

"…with an elevated WBC and CRP, and joint aspirate pending…"
6

Named Pattern

The core

The conceptual label that replaces the list of findings. This is the heart of the summary and the hardest part to construct. The pattern describes the clinical state. It does not commit to a cause.

"…consistent with acute monoarthritis of a large weight-bearing joint, with systemic features of infection."
7

Clinical implication

When relevant

The immediate clinical priority (investigation, referral, or management) that follows from the named pattern. This step makes the summary actionable, not just descriptive. A summary without a next step is complete in form but incomplete in function.

"…requires urgent orthopedic review and joint aspiration."
Worked Example: all elements combined

"A 7-year-old boy, previously well, with a 5-day history of acute pain and swelling of the right knee, presenting with fever and inability to weight-bear, in the absence of trauma, skin rash, or prior joint disease, with an elevated WBC and CRP. This is consistent with acute monoarthritis of a large weight-bearing joint with systemic features of infection — septic arthritis is the leading diagnostic hypothesis, requiring urgent orthopedic review and joint aspiration."

Critical Distinction

Summary ≠ Diagnosis

Do not conflate these two steps

Pattern recognition comes before diagnostic conclusion

Summary: the pattern

Clinical abstraction

A description of the clinical state in conceptual terms. It captures what the findings add up to without committing to a cause. It opens the diagnostic question.

"Acute monoarthritis of a large weight-bearing joint with fever."
→ leads to
Hypothesis: the leading suspicion

Provisional attribution

The most likely cause for the pattern, proposed for testing rather than asserted as fact. It narrows the question and directs which investigations matter, but stays open to revision.

"Septic arthritis is the leading consideration."
→ confirmed as
Diagnosis: the conclusion

Final clinical judgment

The specific disease identified after weighing the evidence (history, examination, and investigations), with response to treatment informing diagnostic revision when the initial picture is uncertain. It closes the diagnostic question with a commitment.

"Septic arthritis due to Staphylococcus aureus."
Those who jump from data to diagnosis skip the summarizing and hypothesis-forming steps. This means their differential is formed on scattered impressions rather than a named pattern, making it less focused and more vulnerable to premature closure and anchoring bias.
What is the core clinical problem here?

After clerking a patient, particularly when preparing to present or formulate a management plan, ask yourself this question.
Reorganize before you present. The summary is the lens through which everything else is seen.

Common Errors

What poor summarizing looks like

Repeating the entire history instead of distilling the pattern A summary selects what matters: the key features that point toward or away from diagnostic possibilities. Length is not depth.
Jumping from data directly to diagnosis, skipping the summarizing step The summary is the bridge between raw data and clinical reasoning. Without it, you leap from information to conclusion without checking your logic.
Using vague labels that do not narrow the differential ("unwell child") "Unwell" describes nothing. Every sick child is unwell. A summary should narrow possibilities, not state the obvious.
Omitting severity from the summary when it is clinically relevant "Pneumonia" without severity is incomplete: the same diagnosis at different severities has different management and urgency.
Confusing summary with diagnosis, committing prematurely The summary says "this is what I have found." The diagnosis says "this is what I think it means." Do not collapse them.
Including too many details, losing the pattern in the noise A summary is pattern recognition, not data preservation. If everything is included, nothing is prioritized.
In short

A clinical summary is the disciplined act of selecting the most relevant findings that, when named as a pattern, open a focused differential , and its quality is an important indicator of whether the clinician has understood the case.

Key Takeaway
Listing findings is data collection.
Summarizing findings is clinical thinking.

The better your summary, the sharper your differential diagnosis.
Name the pattern. Then find the cause.

Details → Pattern → Differential Summary ≠ Diagnosis One summary: one pattern