CLINICAL REASONING IN PRACTICE
A Highbar Clinical Education Series. Practical mentorship insights for better patient care.
By Dr. Robert Dattilo, Residency Director
When a Good Response Sends You the Wrong Way
One of the easiest traps in clinical practice is assuming that the thing which changes symptoms is automatically the thing we need to treat.
Picture a familiar case. A patient comes in with shoulder pain and hurts with active elevation. You assist the scapula, reposition the shoulder blade, or cue better control, and the movement suddenly feels better to them. That matters. It tells you something real. But it does not automatically mean scapular control is the primary problem.
What actually happened is narrower than it feels. Scapular positioning changed this patient’s symptoms in that moment. That is useful. It tells us the system is modifiable, and it may give us a way to reduce symptoms, improve motion, or create a better entry point for loading. What it does not tell us is what should lead the plan. That distinction is where clinical reasoning lives.
A Finding Can Matter Without Being the Driver
A finding can be meaningful without being the primary driver. A test can change symptoms without identifying the real treatment priority. A movement modification can help a patient feel better without being the thing that ultimately restores their capacity.
This is where clinicians get pulled off track. We find something that changes pain, and we chase it. The shoulder feels better with scapular assist, so the whole plan gets built around scapular control. The hip feels better after soft tissue work, so we assume the soft tissue was the main issue. The low back moves better after a mobilization, so we decide mobility must have been the driver.
Sometimes that read is right. Sometimes it is not. The better question is not: “Did this change symptoms?” It is:
“What does this response actually tell me?”
Back to the Shoulder
Say that patient has pain with repetitive overhead activity, posterior shoulder tenderness, symptoms that show up with volume, and a pattern that eases once they warm up. There may be a load tolerance or cuff capacity issue sitting underneath the whole presentation.
Now the scapular assist improves their painful elevation. That does not rule out cuff involvement. It may actually support it. The assist could be helping them move through the painful range with less demand on irritated or underprepared tissue. In that case the scapular finding is still important, but it looks more like a modifier than the main driver.
The mistake would be treating the scapula as the whole problem while never rebuilding the patient’s tolerance to the demand that created the issue in the first place. That is the difference between treating a finding and treating the case.
What Kind of Finding Is This?
Good clinical reasoning asks what a finding actually represents. Is it the primary driver, a contributing factor, a compensation, a symptom modifier, or simply the easiest thing to observe? Those are not the same thing, and treating them as if they were is how plans drift.
A symptom modification test still earns its place. It can improve buy-in, reduce threat, guide treatment selection, and help you find an entry point into care. It just does not remove the need to reason. If the patient’s real limitation is that they cannot tolerate repeated overhead loading, then eventually the plan has to address repeated overhead loading. Mobility work may help. Manual therapy may help. Scapular cueing may help. But if the patient never builds the capacity to handle the task they are trying to return to, the plan is incomplete.
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 honest. They stop us from confusing short-term symptom change with long-term clinical progress.
A Clue, Not a Conclusion
A helpful treatment response is a clue, not a conclusion. That may be the most important line in this whole piece.
When a patient improves with a test, cue, mobilization, or modification, pay attention to it. Do not dismiss it, and do not over-interpret it either. The response gives you information. It does not hand you the full answer.
The goal is not to collect as many positive findings as possible. The goal is to decide which finding should lead the plan today, which findings support the plan, and which ones simply need to be monitored. That is a different level of thinking, and it makes treatment more efficient. Instead of trying to fix every impairment, you are asking a sharper set of questions. What is the most defensible thing to prioritize right now? What marker tells me if 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 one question: did I find the driver, or did I find a way to temporarily modify the presentation? Both are useful. They should not always lead to the same plan.
