When the Scan Comes Back Clean

For National Pain Awareness Week: a clean scan doesn't mean nothing is wrong. Why chronic pain and imaging don't always line up, and what functional assessment can measure that a scan can't.
Doctor reviewing an imaging scan with a patient

When the Scan Comes Back Clean

Posted by IMA Expert on Oct 5, 2026, 7:39:46 PM

For National Pain Awareness Week: a clean scan doesn't mean nothing is wrong. Why chronic pain and imaging don't always line up, and what functional assessment can measure that a scan can't.

 

The imaging is normal. The bloodwork is unremarkable. And the person in front of you is still describing pain that's kept them out of work for months.

 

It's National Pain Awareness Week - a good moment to say plainly what a lot of case managers already suspect: a clean scan doesn't mean nothing is wrong. According to the Canadian Pain Task Force, roughly 7.6 million Canadians - about one in five people - live with chronic pain. The Task Force describes chronic pain as "largely invisible," and notes that people living with it often feel disbelieved and stigmatized, in part because it frequently persists without an objective marker that shows up on a scan.

 

That's not a gap in the technology. It's a mismatch between what imaging is built to detect - structural damage - and what pain actually is, which is a lived, functional experience that doesn't always have a structural cause imaging can capture.

 

For a disability file, that mismatch creates a real risk: treating "the scan is clean" as equivalent to "there's no impairment." It's an understandable shortcut, and it's also frequently wrong.

 

This is where functional assessment does something imaging can't. Instead of asking whether there's a visible cause for the pain, it asks a different, more answerable question: what can this person actually do, sustain, and tolerate right now? Grip strength, standing tolerance, ability to sustain a task over a shift rather than a single attempt - these are measurable, even when the underlying cause of the pain isn't fully visible on a scan.

 

That doesn't mean every reported pain level gets taken at face value without scrutiny - a good functional assessment is built specifically to test consistency and effort, not just to record self-report. But it does mean the absence of an imaging finding isn't treated as proof the file should be resolved.

 

If you're managing a file where the imaging says one thing and the presentation says another, that gap is exactly what a functional assessment is designed to work through. We'd be glad to help you get a clearer answer than "the scan is clean" gives you.