60/100

Moderate evidence

Published recordHealthGeneral

Imaging subtypes reveal distinct biological substrates and disability profiles in multiple sclerosis

Truvace record
TRV-2026-1187raw data (JSON)
Version
v3Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
cecb87556bc4…check it

Multiple sclerosis is characterized by marked biological heterogeneity that is only partly captured by conventional clinical phenotypes and age-at-onset categories. MRI can detect focal lesions, diffuse microstructural damage and atrophy, but these measures are usually considered separately. We therefore aimed to use Subtype and Stage Inference (SuStaIn), an unsupervised machine learning framework, to identify biologically meaningful MRI subtypes of multiple sclerosis and determine their associations with disabi…

The gain

Within each MRI subtype, advancing SuStaIn stage was associated with worse cognitive performance, showing the ML staging captures cognitive decline, though cognition and genetic risk did not differ across subtypes.

Sources

1 on file
  1. Braindoi:10.1093/brain/awag320
    Peer-reviewed2026-09-23

Cite this record

v3

Truvace Impact Record TRV-2026-1187, v3: “Imaging subtypes reveal distinct biological substrates and disability profiles in multiple sclerosis.” Truvace, 2026-11-04. /record/TRV-2026-1187 (accessed on the day you copy it). sha256 cecb87556bc44fba…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3cecb87556bc4…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain unsupported, problem absent).

  2. Revisedv230499eea2922…

    Direction audit: filed as a problem but describes a gain.

  3. Publishedv130ac2f2e9b06…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1187 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.