Reasoning Through Headache

Headache is common enough to feel familiar and broad enough to punish shortcuts.

Most headaches encountered in ambulatory practice are primary headache disorders or other nonemergent causes. A smaller group reflects secondary disease that may require urgent evaluation. The reasoning task is therefore to recognize the common patterns without becoming casual about the uncommon dangerous ones.

That balance makes headache an excellent chief complaint for learning clinical reasoning.

Begin with the clinical question

Before naming a headache type, decide what problem you are trying to solve.

Is this a recurrent pattern in a stable patient?

Is this a new headache?

Is the headache changing in frequency, intensity, or character?

Are there neurologic findings?

Is the patient pregnant or postpartum?

Is there fever, immune compromise, trauma, malignancy, anticoagulation, or another context that changes risk?

Is the onset unusual enough to raise concern for a secondary process?

The answer determines how much confidence you can place in pattern recognition.

Use time course before symptom adjectives

Learners often focus on whether the pain is throbbing, stabbing, pressure-like, or unilateral.

Those features can help, but time course often does more diagnostic work.

Ask:

• When did the headache begin?
• How quickly did it reach maximum intensity?
• Is this the first episode or part of a recurring pattern?
• How long does each episode last?
• How often does it occur?
• Has the pattern changed?
• Does anything reliably trigger or relieve it?

A recurrent stereotyped pattern over months or years carries a different implication from a first severe headache that reached maximum intensity rapidly.

Time course belongs in the problem representation.

Separate primary headache patterns from secondary warning signs

Primary headache disorders include migraine, tension-type headache, and trigeminal autonomic cephalalgias such as cluster headache.

These diagnoses are made from the clinical pattern after the history and examination do not suggest a more concerning secondary process.

Secondary headache can arise from many causes, including vascular, infectious, inflammatory, pressure-related, traumatic, medication-related, toxic, or structural conditions.

You do not need to memorize every secondary cause at once.

You do need a disciplined way to recognize when the case no longer behaves like a routine primary headache.

Treat red flags as decision modifiers

Useful headache red flags include features such as:

• Sudden or rapidly peaking severe onset
• New focal neurologic deficit
• Altered mental status
• Fever or systemic illness in the appropriate context
• Papilledema
• New headache during pregnancy or postpartum
• New headache in a patient with malignancy or significant immune compromise
• A major change in an established headache pattern
• Headache triggered by exertion, coughing, or Valsalva in the appropriate context
• New headache following significant trauma

The presence of a warning feature should change your reasoning.

It may alter the urgency, the examination, the testing threshold, or the need for escalation.

A warning feature is not a diagnosis by itself.

The question is what serious process it raises concern for and what decision changes because of it.

Make the neurologic examination part of the reasoning

A focused neurologic examination helps distinguish an uncomplicated primary headache pattern from presentations that require broader evaluation.

Mental status, cranial nerves, motor function, sensation, coordination, gait when appropriate, visual findings, and funduscopic assessment can all matter depending on the presentation.

The examination should answer questions created by the history.

If the headache is accompanied by diplopia, the cranial nerve examination becomes especially relevant.

If the patient describes weakness or numbness, confirm whether a focal deficit is present.

If increased intracranial pressure is a concern, papilledema becomes important.

The examination is not a checklist detached from the differential.

It tests the model.

Recognize migraine as a pattern

Migraine often produces episodic headache with associated features such as nausea, photophobia, phonophobia, or activity-related worsening. Some patients experience aura.

The exact presentation varies.

A learner should know the pattern while avoiding the assumption that every migraine contains every classic feature.

The more important question is whether the patient’s recurrent history, associated symptoms, examination, and lack of concerning secondary features form a coherent primary-headache illness script.

This is where pattern recognition becomes useful.

Recognize cluster headache as a distinct illness script

Cluster headache is a useful example of why illness scripts matter.

The typical pattern includes severe unilateral orbital, supraorbital, or temporal pain with ipsilateral autonomic features such as tearing, conjunctival injection, rhinorrhea, or nasal congestion. Attacks are relatively brief compared with many migraines and tend to recur in clusters over a period of time.

Patients are often restless during attacks.

That combination is more useful than remembering one isolated symptom.

A unilateral headache with tearing is not automatically cluster headache.

The full pattern needs to fit.

Do not let one familiar feature close the case

Headache vignettes frequently contain recognizable words.

Photophobia may pull you toward migraine.

Tearing may pull you toward cluster headache.

Neck discomfort may pull you toward a musculoskeletal explanation.

The familiar feature should open an illness script.

It should not end the reasoning.

Ask what else should be present if your explanation is correct.

This is where the DDQX Diagnostic Prediction Loop helps.

Observation → Prediction → Verification → Adjustment

You observe the current pattern.

You predict what else should fit.

You compare that prediction with the rest of the case.

You adjust if the evidence disagrees.

Apply the 5P Approach™ to Clinical Reasoning

Prioritize

Identify the time course, severity, neurologic findings, systemic context, pregnancy status when relevant, trauma, medication context, and any meaningful warning features.

Paraphrase

Compress the case.

For example:

“Thirty-year-old with recurrent unilateral pulsating headaches lasting several hours with nausea and photophobia, normal neurologic examination, and no change in pattern.”

That problem representation is easier to reason from than a long symptom list.

Prognose

Predict what family of diagnosis should fit and what type of next step is appropriate.

If the pattern is consistent with a stable primary headache and the examination is reassuring, the expected next step differs from a new rapidly peaking headache with a focal deficit.

Pick

Choose the diagnosis, test, or management step that matches the clinical sequence.

Post-Mortem

Ask what change would have made the case more concerning.

What if the headache were new?

What if the patient were postpartum?

What if there were papilledema?

What if the pain reached maximum intensity immediately?

This builds flexible illness scripts.

Use testing to answer a specific concern

Imaging and other testing should follow the clinical question.

A patient with a stable recurrent primary-headache pattern and reassuring examination is different from a patient with a new high-risk presentation.

Emergency headache evaluation may require focused pathways for conditions such as subarachnoid hemorrhage or other secondary causes when the history and examination raise concern.

The useful habit is to ask what diagnosis you are trying to identify or exclude and why the test result would change what happens next.

Testing without a question creates noise.

Reassess when the pattern changes

A known headache disorder does not make every future headache the same.

Patients with migraine can develop other illnesses.

A patient with a familiar diagnosis still deserves reassessment when the pattern changes meaningfully.

Ask whether the current episode resembles the prior illness script.

If the answer is no, rebuild the problem representation rather than forcing the old label onto the new case.

Learn headache by comparison

Compare several cases directly.

One recurrent migraine pattern.

One cluster-headache pattern.

One new headache with fever and meningismus.

One new headache with focal neurologic findings.

One sudden severe headache.

One postpartum headache.

Ask which feature changed the urgency and which feature changed the leading diagnosis.

That comparison teaches more than memorizing six separate lists.

The learning target

Headache reasoning depends on calibrated attention.

Recognize common primary patterns efficiently.

Slow down when the time course, examination, context, or trajectory does not fit.

Use red flags to change decisions rather than merely decorate the differential.

Then keep the model open to revision.

Next step: Use the DDQX chief-complaint framework and the 5P Approach™ to Clinical Reasoning to compare headache cases by changing one high-value feature at a time.