CLINICAL REASONING IN PRACTICE

Practical mentorship insights for better patient care

A Highbar Clinical Education Series

You Might Be Treating the Wrong Thing

Why the test that changes symptoms does not always tell you what should lead the plan.

A symptom modification test can change a patient’s symptoms without automatically identifying the primary treatment target. Treat the response as one piece of evidence, then look for convergence across the history, examination, function, and reassessment before deciding what should lead the plan.

One of the easiest traps in clinical practice is assuming that the thing that changes symptoms is automatically the thing we need to treat.

A patient comes in with shoulder pain. They have pain with active elevation. You assist the scapula, reposition the shoulder blade, or cue better control, and suddenly the movement feels better.

That matters.

But it does not automatically mean scapular control is the primary problem.

What happened is narrower than it can feel. Scapular positioning changed the patient’s symptoms or movement in that moment. That is useful. It tells us the presentation is modifiable and may give us an entry point for loading.

What it does not automatically tell us is what should lead the plan.

That is where clinical reasoning matters.

A Finding Can Matter Without Leading the Plan

A finding can matter without being the primary treatment priority. A test can change symptoms without identifying the variable that deserves the most attention. A movement modification can help without being the thing that ultimately restores capacity.

This is where clinicians can get pulled off track. We find something that changes pain, and we chase it.

The shoulder feels better with scapular assist, so the plan gets built around scapular control. The hip feels better after soft tissue work, so we assume the soft tissue was the issue. The low back moves better after a mobilization, so we decide mobility was the driver.

Sometimes that interpretation is right.

Sometimes it is not.

The better question is not simply, “Did this change symptoms?”

The better question is, “What does this response actually tell me?”

The better question is, “What does this response actually tell me?”

Back to the Shoulder

Say that patient has pain with repetitive overhead activity, symptoms that show up with volume, and a pattern that improves once they warm up. There may be a load-tolerance or cuff-capacity issue underneath the presentation.

Now the scapular assist improves their painful elevation. That does not rule out cuff involvement. It may actually fit with the broader hypothesis.

The assist may help the patient move through the painful range with less demand on irritated or underprepared tissue. The scapular finding still matters, but it looks more like a symptom modifier than the primary priority.

The mistake would be treating the scapula as the whole problem while never rebuilding the patient’s tolerance to the demand that repeatedly brings on the symptoms.

That is the difference between treating a finding and treating the case.

That is the difference between treating a finding and treating the case.

What Role Does This Finding Actually Play?

Good clinical reasoning asks what role a finding actually deserves in the case. Is it:

• the primary treatment priority,
• a contributing factor,
• a compensation,
• a symptom modifier,
• or simply an observable finding that is easy to notice?

Those are different roles.

A symptom modification test can be extremely valuable. It can improve buy-in, reduce threat, and identify an entry point into care. But it does not remove the need to reason.

If the patient’s real limitation is tolerance to repeated overhead loading, the plan eventually has to address that demand. Mobility work, manual therapy, or scapular cueing may help. But if the patient never builds capacity for the task they need to return to, the plan is incomplete.

In mentoring clinicians, I often see a positive response become so compelling that it starts to organize the whole case. The response matters, but the job is to decide what role it deserves—not automatically promote it to the top of the plan.

So What Should Lead the Plan?

A single positive test rarely earns that distinction on its own. The stronger treatment priority is usually the one that makes the most sense when you look for convergence across the case.

Ask whether the history points in the same direction. Does the aggravating task expose the suspected limitation? Do other findings support the same hypothesis? And does addressing it improve the patient’s ability to tolerate the activity they actually care about?

In the shoulder example, repeated overhead volume reproduces symptoms and the patient appears limited by tolerance to that demand. Scapular assistance reduces symptoms during elevation, but it does not explain the entire presentation.

Taken together, the priority may be rebuilding capacity for repeated overhead loading, with scapular modification as one strategy for helping the patient get there.

Clinical reasoning is rarely about one test proving the answer. It is about building the most defensible working hypothesis, then testing it through treatment and reassessment.

A Useful Reasoning Sequence

1. Start with the response. What changed, and how meaningful was the change?
2. Build a working hypothesis. What might be limiting the patient or maintaining the problem?
3. Look for convergence. Do the history, task demands, examination, and response point in the same direction?
4. Choose the treatment priority. What is most defensible and most relevant to meaningful function right now?
5. Reassess. Did the plan improve the thing that actually matters to the patient?

Clinical Reasoning Vocabulary

These terms are useful only if we are clear about what they mean. They describe the role a finding plays in the current case—not a permanent label or a claim that we have proven causation.

Reassess the Thing That Actually Matters

This is why reassessment matters—and not only in the “Did pain change right now?” sense. That is one layer, and a useful one, but it is not the whole picture.

We also need to reassess whether the patient is moving toward the goal that matters. Are they:

• tolerating more load?
• recovering faster?
• less reactive the next day?
• gaining confidence with the task?
• becoming less dependent on us to feel better?
• able to do more of what brought them to therapy in the first place?

Those questions keep us from confusing short-term symptom change with long-term progress.

A Clue, Not a Conclusion

A helpful treatment response is a clue, not a conclusion.

A helpful treatment response is a clue, not a conclusion.

When a patient improves with a test, cue, mobilization, or modification, pay attention. Do not dismiss it, and do not over-interpret it. The response gives you information. It does not hand you the answer.

The goal is not to collect positive findings. It is to decide which finding should lead the plan, which ones support it, and which simply need monitoring.

Instead of trying to fix every impairment, ask:

• What is the most defensible thing to prioritize right now?
• What marker tells me whether I am on the right track?
• What response would make me continue, modify, or change course?

That is the clinical reasoning habit worth building.

So the next time a test or treatment changes a patient’s symptoms, pause before you chase it. Ask yourself:

Did I identify something that should lead the plan, or did I identify something that modifies the presentation?

Did I identify something that should lead the plan, or did I identify something that modifies the presentation?

Both can matter. The clinical reasoning is deciding what role each finding deserves—and then reassessing whether your decision actually moves the patient toward what matters.