60/100

Moderate evidence

Trace: a gain and a problemPublished recordHealthThe Trace

Regional correspondence between visual Fazekas ratings and AI-derived white matter hyperintensity burden in acute ischemic stroke: a retrospective cross-sectional study

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

Abstract Background Visual Fazekas ratings assess white matter hyperintensity (WMH) severity, whereas artificial intelligence (AI)-derived segmentation provides continuous measurements. We quantified regional and total visual–AI correspondence, inter-reader reliability, and high-burden concordance in acute ischemic stroke. Methods We included 361 patients with acute ischemic stroke undergoing T2-weighted fluid-attenuated inversion recovery (T2-FLAIR) magnetic resonance imaging (MRI). Two readers independently as…

57Gain side

How the two sides scoreClose call

55Problem side

The gain

In a retrospective study of 361 acute stroke patients, AI-measured white matter hyperintensity burden matched visual Fazekas high-burden classification in 326 patients (90.3%, κ = 0.781).

The problem

In the same 361-patient stroke MRI study, AI measurements correlated only moderately with visual ratings of deep white matter disease (ρ = 0.588), and agreement on high burden varied from κ 0.462 to 0.801 across thresholds.

A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.

What the scores mean

G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.

P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.

What this doesn’t fix

The AI high-burden cut-off was cohort-specific (the upper third, 1.20% of intracranial volume), and agreement changed when thresholds were varied, so the results depend on the thresholds chosen.

Sources

1 on file
  1. BMC Neurologydoi:10.1186/s12883-026-05594-x
    Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3052, v1: “Regional correspondence between visual Fazekas ratings and AI-derived white matter hyperintensity burden in acute ischemic stroke: a retrospective cross-sectional study.” Truvace, 2026-11-19. /record/TRV-2026-3052 (accessed on the day you copy it). sha256 c380704142ad3dbd…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1c380704142ad…

    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-3052 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.