A client has just completed a block of treatment and rated the same three functional activities they scored at intake — before writing the discharge summary, you want to know whether that change is clinically meaningful or within normal measurement noise.
Change score = Average(follow-up scores) − Average(baseline scores)
Each activity is scored 0 (unable to perform) to 10 (able to perform at pre-injury/pre-condition level). The average change across activities is compared to the published minimal clinically important difference (MCID) of approximately 2 points per activity, or 3 points for the average score.
1 What this calculator does
Calculates a change score using the Patient-Specific Functional Scale (PSFS) — a widely used, individualised outcome measure where the client nominates their own meaningful activities and rates difficulty performing each on a 0-10 scale at baseline and follow-up. Compares the change against the published minimal clinically important difference (MCID) to help judge whether progress is clinically meaningful.
2 Formula & professional reasoning
Baseline average = mean(baseline activity scores)
Follow-up average = mean(follow-up activity scores)
Change score = Follow-up average - Baseline average
Unlike standardised condition-specific outcome measures, the PSFS lets each client nominate 2-5 activities that are personally meaningful and currently difficult (e.g. 'lifting my grandchild', 'walking to the letterbox'), then rates their ability to perform each from 0 (unable) to 10 (pre-condition level). This individualisation makes it broadly applicable across musculoskeletal, neurological and other rehabilitation contexts. The published MCID (minimal clinically important difference) of approximately 2 points change per individual activity, or roughly 3 points change in the average score, is the threshold above which a change is considered likely to reflect a real, clinically meaningful improvement rather than measurement variability alone.
3 Worked examples
⚠️ Illustrative example only — not clinical or professional instruction.
Baseline avg = (3+4)/2 = 3.5 | Follow-up avg = (7+6)/2 = 6.5 | Change = 6.5-3.5 = 3.0Baseline avg = (5+4+6)/3 = 5.0 | Follow-up avg = (6+5+7)/3 = 6.0 | Change = 6.0-5.0 = 1.0Baseline avg = (2+6+3)/3 = 3.67 | Follow-up avg = (8+5+4)/3 = 5.67 | Change = 5.67-3.67 = 2.04 Sanity check
5 Common errors
| Error | Cause | Consequence | Fix |
|---|---|---|---|
| Comparing different activities at baseline and follow-up | Client nominates new activities at follow-up rather than re-rating the original baseline activities | Change score no longer reflects genuine progress on the same functional goals — invalidates the comparison | Always re-rate the exact same client-nominated activities at follow-up as were scored at baseline |
| Treating any positive change as clinically meaningful | Reporting even a 0.5-1 point average improvement as clear evidence of successful treatment | Small changes can reflect normal day-to-day variability or measurement error rather than true improvement | Compare the change score against the published MCID (~2 pts/activity, ~3 pts average) before describing a change as clinically meaningful |
| Averaging away a clinically important single-activity result | Reporting only the average change when one specific activity showed a large change (positive or negative) that matters clinically | Important individual-activity information gets lost in an averaged summary figure | Report both the average change score and any notable individual-activity changes, especially large single-activity shifts |
| Using PSFS as the only outcome measure for a condition with a validated specific tool | Relying solely on PSFS when a condition-specific validated measure exists and is expected (e.g. by a funder or referrer) | May not meet documentation expectations for that specific condition or funding body | Use PSFS alongside, not instead of, any condition-specific validated outcome measure required by the clinical context or funding body |
6 Reference & regulatory links
7 Professional workflow
Common tools used alongside this one: