Brain dysconnectivity patterns associated with chronic back pain development.
Overview
- Department of Radiology, LMU University Hospital, LMU Medizin, Ludwig-Maximilians-Universität München,Munich, Germany
- Department of Neurosurgery, LMU University Hospital, LMU Medizin, Ludwig-Maximilians-Universität München,Munich, Germany
Abstract
Chronic back pain often emerges from a transitional period of subacute pain, yet no clinically applicable biomarker exists to identify which patients are at risk for chronification. Evidence suggests that this transition is driven not only by nociceptive input but by changes in brain networks involved in valuation, emotion regulation, and learning. Here, we used resting-state functional magnetic resonance imaging (rs-fMRI) and machine learning to explore whether dysconnectivity in these networks is associated with later development of chronic back pain. We analyzed functional connectivity in 46 patients with subacute back pain and 43 healthy controls from a publicly available longitudinal cohort, classifying patients one year later as either recovered or chronified based on pain outcomes. A data-driven model identified a set of six brain regions whose patterns of dysconnectivity distinguished the two patient trajectories with an area under the curve of 0.87. These regions encompass prefrontal, temporal, and somatosensory hubs implicated in reinforcement learning, avoidance behavior, and pain catastrophizing, suggesting a potential link between dysconnectivity patterns and psychological processes implicated in pain persistence. Based on these features, we introduced an exploratory rs-fMRI–based marker for pain chronification, suggesting potential prognostic relevance that requires independent validation before clinical stratification or targeted intervention can be considered.
Reproduced under the paper's license (CC BY), from the paper cited above.
Code
No file of the authors' code could be read here: it is described below, and read at its source.
openpain.org
Availability: 20 checks, the latest on 13 November 2026: unreachable at the last attempt
- 13 November 2026: unreachable at the last attempt
- 12 November 2026: unreachable at the last attempt
- 11 November 2026: unreachable at the last attempt
- 10 November 2026: unreachable at the last attempt
- 9 November 2026: unreachable at the last attempt
- 8 November 2026: unreachable at the last attempt
- 6 November 2026: unreachable at the last attempt
- 5 November 2026: unreachable at the last attempt
- 4 November 2026: unreachable at the last attempt
- 3 November 2026: unreachable at the last attempt
- 2 November 2026: unreachable at the last attempt
- 1 November 2026: unreachable at the last attempt
- 31 October 2026: unreachable at the last attempt
- 30 October 2026: unreachable at the last attempt
- 29 October 2026: unreachable at the last attempt
- 28 October 2026: unreachable at the last attempt
- 27 October 2026: unreachable at the last attempt
- 26 October 2026: unreachable at the last attempt
- 2 October 2026: unreachable at the last attempt
- 30 September 2026: unreachable at the last attempt
Code availability
Code is available on request.
Reproduced under the paper's license (CC BY), from the paper cited above.
Tracing map
Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.
What the map holds:
- 1 repository of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
- 0 scripts, each with its path and the digest of its content;
- no match between paragraphs and code yet;
- neither the text of the paper nor the code itself.
Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.
Data
No dataset and no data link were found in the paper.
Data availability
All data and code used in this study are publicly available via the OpenPain repository: https://
Reproduced under the paper's license (CC BY), from the paper cited above.
Versions
The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.
Version 1, 27 September 2026: the first record
Recorded: type, language, journal, volume, issue, pages, dates, 5 authors, 3 keywords, 1 funder, 95 references.
Cite
This paper
Wunderlich, S., Schulz, E., Ringel, F., Stoecklein, V. M., & Stoecklein, S. (2026). Brain dysconnectivity patterns associated with chronic back pain development. Brain informatics, 13(1), 39. https://
BibTeX
@article{wunderlich2026b
author = {Wunderlich, Stephan and Schulz, Enrico and Ringel, Florian and Stoecklein, Veit M. and Stoecklein, Sophia},
title = {{Brain dysconnectivity patterns associated with chronic back pain development}},
journal = {Brain informatics},
year = {2026},
month = aug,
volume = {13},
number = {1},
pages = {39},
publisher = {Springer},
issn = {2198-4018},
doi = {10.1186/
url = {https://
pmid = {42640485},
pmcid = {PMC13507019}
}
RIS
TY - JOUR
AU - Wunderlich, Stephan
AU - Schulz, Enrico
AU - Ringel, Florian
AU - Stoecklein, Veit M.
AU - Stoecklein, Sophia
TI - Brain dysconnectivity patterns associated with chronic back pain development
T2 - Brain informatics
J2 - Brain Inform
PY - 2026
DA - 2026/
VL - 13
IS - 1
SP - 39
SN - 2198-4018
PB - Springer
DO - 10.1186/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.1186/
"type": "article-journal",
"title": "Brain dysconnectivity patterns associated with chronic back pain development",
"container-title": "Brain informatics",
"author": [
{
"family": "Wunderlich",
"given": "Stephan"
},
{
"family": "Schulz",
"given": "Enrico"
},
{
"family": "Ringel",
"given": "Florian"
},
{
"family": "Stoecklein",
"given": "Veit M."
},
{
"family": "Stoecklein",
"given": "Sophia"
}
],
"container-title-short":
"volume": "13",
"issue": "1",
"page": "39",
"DOI": "10.1186/
"PMID": "42640485",
"PMCID": "PMC13507019",
"ISSN": "2198-4018",
"publisher": "Springer",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
8,
21
]
]
}
}
The tracing map gets a citation of its own once an author has validated it and it has a DOI.
Similar papers
The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.
- [1] doi:10.1162/imag.a.968
- Denoising strategies of functional connectivity MRI data in lesional and non-lesional brain diseases.Journal: Imaging neuroscience (Cambridge, Mass.)In common: fMRI, 6 references, author Enrico Schulz
- [2] doi:10.1097/j.pain.0000000000003335 [code]
- Beyond the chronic pain stage: default mode network perturbation depends on years lived with back pain.Journal: PainIn common: pain, fMRI, 8 references
- [3] doi:10.1038/s41598-023-35294-2
- Pain and the emotional brain: pain-related cortical processes are better reflected by affective evaluation than by cognitive evaluation.Journal: Scientific reportsIn common: pain, 3 references, author Enrico Schulz
- [4] doi:10.7554/elife.90634 [code]
- Statistical learning shapes pain perception and prediction independently of external cues.Journal: eLifeIn common: pain, 6 references
- [5] doi:10.1016/j.xcrm.2022.100677
- Corticostriatal circuits in the transition to chronic back pain: The predictive role of reward learning.Journal: Cell reports. MedicineIn common: pain, fMRI, 6 references
- [6] doi:10.1016/j.isci.2024.108954 [code]
- Adolescents' pain-related ontogeny shares a neural basis with adults' chronic pain in basothalamo-cortical organization.Journal: iScienceIn common: pain, 6 references
- [7] doi:10.1038/s41467-024-50103-8 [code]
- Placebo treatment affects brain systems related to affective and cognitive processes, but not nociceptive pain.Journal: Nature communicationsIn common: pain, 6 references
- [8] doi:10.1186/s12880-025-02009-0
- Precision connectivity in osteoarthritis pain with permutation and network analysis: a key step toward clinical application.Journal: BMC medical imagingIn common: pain, fMRI, clinical / translational, 4 references
- [9] doi:10.1038/s42003-024-06574-y [code]
- An externally validated resting-state brain connectivity signature of pain-related learning.Journal: Communications biologyIn common: pain, 5 references
- [10] doi:10.1117/1.nph.11.4.045015 [code]
- Explainable fNIRS-based pain decoding under pharmacological conditions via deep transfer learning approach.Journal: NeurophotonicsIn common: pain, 5 references
Contribute
The authors of this paper can claim it, correct its record and validate its tracing map, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to OSCR's own machine, which answers it; your account page follows them.
Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.
Claim this paper
Correct its record
Say what each link of this record is, remove the ones that are not the paper's, add the ones that are missing. The correction becomes a new version of the record, in its Versions section.
Validate its tracing map
You validate the map as this page shows it: 1 repository of the authors' code, each at its verified commit and with its license, 0 scripts, and 0 matches between paragraphs and code (see the Code and Map sections). It then receives a DOI on Zenodo, with you (your ORCID iD) and OSCR as its creators; the code itself is not deposited.
The map's fingerprint: sha256:49d57dd04df3a4b6…
Add the badge to the code's README
If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.
Markdown
<!-- oscr-badge:start -->
[](https://openscicode.org/badge/doi/10.1186/s40708-026-00328-8)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1186/s40708-026-00328-8.svg
:target: https://openscicode.org/badge/doi/10.1186/s40708-026-00328-8
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1186/s40708-026-00328-8"><img src="https://openscicode.org/badge/doi/10.1186/s40708-026-00328-8.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.
Request its removal
To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).
Discussion, reproductions, activity
Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.
Report a mismatch between the code and the paper · Report a code error (signed in)
Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.
Report a reproduction failure (signed in)
Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.
