Knowing the name of a muscle is different from knowing why it hurts. You can identify the supraspinatus on a chart, but in the clinic, a patient presents with a story, a set of limitations, and a problem that needs solving. This is where clinical reasoning begins. It's the process that bridges your anatomical knowledge with the complexities of a real person's condition.

Clinical reasoning is not guesswork; it is a structured, dynamic process. It allows you to move beyond simply labelling a painful part to understanding the underlying dysfunctions and contributing factors. To do this effectively, we use established models that guide our thinking and decision-making.

One of the most fundamental frameworks is the Patient/Client Management Model. It provides a roadmap for the entire patient encounter, ensuring a comprehensive and logical progression from initial contact to achieving functional goals. The model consists of five key elements.

This model provides the structure, but what cognitive processes drive the steps, especially the Evaluation? Clinicians use two main modes of thinking: fast and slow. The fast mode is pattern recognition, an intuitive process born from experience. You see a cluster of signs and symptoms that match a familiar clinical picture, like a classic Achilles tendinopathy. It's quick and often accurate.

The slow mode is analytical and deliberate. This is hypothetico-deductive reasoning. It involves forming a set of potential explanations (hypotheses) for the patient's problem and then systematically testing them. This is crucial for complex, unfamiliar, or atypical cases where patterns aren't obvious. Another approach, narrative reasoning, focuses on the patient's unique story, experiences, and context to understand their problem.

For a systematic, slow-thinking approach, the Hypothesis-Oriented Algorithm for Clinicians II (HOAC II) is an invaluable tool. It formalises the hypothetico-deductive process, guiding you from a list of patient-identified problems to a targeted intervention plan. The goal is to generate multiple hypotheses, not just one.

Imagine a patient reports difficulty lifting their arm overhead. Instead of just assuming 'shoulder impingement', you generate several hypotheses:

• Hypothesis 1: Rotator cuff tendinopathy is causing pain and weakness.
• Hypothesis 2: Poor scapular control is altering shoulder biomechanics.
• Hypothesis 3: Reduced thoracic spine extension is limiting the available range of motion.
• Hypothesis 4: Fear of movement (kinesiophobia) following a past injury is leading to protective muscle guarding.

Each hypothesis leads to a specific 'if-then' statement that guides your physical assessment: "If the patient has poor scapular control, then I should observe dyskinesis during arm elevation and find weakness in the serratus anterior."

To help refine these hypotheses, we use a profiling tool called the SINSS construct during the subjective examination. It's a mnemonic for characterising the patient's symptoms:

By applying the SINSS construct, you build a detailed picture of the patient's presentation. An 'irritable' condition might suggest an inflammatory component, while a 'stable', long-standing issue points towards chronic pain mechanisms. This information helps you prioritise your hypotheses and select the most appropriate physical tests, moving you efficiently from a broad list of possibilities to a specific, defensible clinical diagnosis and treatment plan.