Brain
Resting-State fMRI: When Task Mapping Fails
Fellowship-level neuroradiology teaching by E. Brooke Schrickel, MD. Open this topic in the interactive reading room →
Core clinical idea
Resting-state fMRI exists to rescue the presurgical eloquent-cortex map when task fMRI fails — and it fails often, in exactly the patients you most need to map. Its job is the same as task fMRI's: locate motor/language cortex relative to tumor, including when mass effect has displaced it.
Bottom line
Resting-state fMRI is the eloquent-cortex map that survives when task fMRI can't — know when to reach for it and how to read a network shoved by tumor.
Core workstation questions
- Did task fMRI actually succeed, or is it noisy/non-cooperative — should resting-state be added?
- Where does eloquent cortex sit relative to the tumor, and which surgical approach spares it?
- Is anatomic distortion severe enough that landmark-based seeding is unreliable — was the normal hemisphere used to anchor the network?
- Do the resting-state, task, and clinical/intraoperative pictures agree, or is there discordance to flag?
- Can this patient actually perform a task — if not, is resting-state the better functional map here?
- Which network is this seed/component, and is it eloquent for the planned resection?
- Is this an anticorrelation (expected network structure) or true artifact?
- Is the patient too sedated to trust the networks?
What changes reporting / management
- Deliverable is eloquent-cortex location relative to tumor plus the safe approach (e.g., anteriorly displaced motor strip favors a parietal approach) — state the displacement, not just 'activation present.'
- Invoke resting-state when patients can't/won't cooperate, when task fMRI failed, on acute/overnight/weekend cases, when multiple networks are needed, or when electrocortical stimulation is too risky.
- Read it as a presurgical adjunct corroborating task fMRI and electrocortical stimulation, not a standalone diagnosis.
- When task fMRI is degraded or impossible (sedated, pediatric, aphasic, paretic patient), offer resting-state as the salvage functional map for eloquent-network localization.
- Read correlated time courses as same-network connectivity and anticorrelation as expected inter-network structure, not artifact.
- Localize the planning-relevant networks (somatomotor, visual, language); identify the default mode network from a posterior cingulate seed.
Practical traps
- Trusting landmark-based seed placement on the tumor-distorted hemisphere instead of anchoring on the normal side.
- Treating a single clean-looking network map as definitive and letting it overrule a discordant clinical picture.
- Mistaking the default mode network (a demonstration network) for the clinically actionable motor/visual/language networks.
- Misreading anticorrelation between networks as artifact when it is real network structure.
- Treating a resting-state network as a labeled cognitive function without confirming which network it is.
- Trusting networks under heavy sedation, which is the main thing that suppresses them.
Teaching pearls
- Resting-state is the rescue map for patients who can't do the task.
- Report the displaced eloquent cortex and the safe approach, not just 'activation.'
- On the tumor side, anchor on the normal hemisphere — distorted-side landmarks lie.
- Adjunct, not arbiter: a clean network map doesn't overrule a discordant clinical picture.
- Same BOLD sequence as task fMRI — the difference is no task and slow spontaneous fluctuations.
- Its killer app is the uncooperative patient: sedated, pediatric, aphasic, paretic.
- Resting-state gives connectivity, not a labeled cognitive assignment — you still have to know the network.
- Anticorrelation between networks is real signal, not artifact.
Source lectures
- Clinical Applications of Resting State fMRI
- Resting State fMRI
Educational material for radiology residents and neuroradiology fellows. Nothing here drives individual patient care, and it contains no patient data.