TruaceTracing the truth around AISunday, September 20, 2026
TRV-2026-1149Certified recordPeer-reviewed

Artificial Intelligence in Cerebral Small Vessel Disease Imaging: A Study-Level Cross-Sectional Analysis of Validation Status and Clinical Applicability

Artificial intelligence (AI) is increasingly used in cerebral small vessel disease (CSVD) imaging, but the extent of validation and clinical applicability across the literature remains uncertain. We performed a study-level cross-sectional analysis using a frozen Web of Science Core Collection (WoSCC) cohort supplemented by PubMed and IEEE Xplore searches to assess database coverage and the stability of findings from the WoSCC cohort. After study-level reconciliation, 463 independent studies were included. White…

Health · P Space — documented harm · certified 2026-09-20 · v1 · article view · machine-readable

Current reading — problem

Artificial Intelligence in Cerebral Small Vessel Disease Imaging: A Study-Level Cross-Sectional Analysis of Validation Status and Clinical Applicability: White matter hyperintensity segmentation/quantification was the most common task (196/463, 42.3%), followed by cerebral microbleed detection/classification (82/463, 17.7%), perivascular space/lacune assessment (67/463, 14.5%), CSVD burden/risk modeling (62/463, 13.4%), and clinical outcome prediction (56/463, 12.1%).

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1149, v1: “Artificial Intelligence in Cerebral Small Vessel Disease Imaging: A Study-Level Cross-Sectional Analysis of Validation Status and Clinical Applicability.” Truvace, 2026-09-20. /record/TRV-2026-1149 (accessed at citation time). sha256 2ef54cf6b6f30e4d

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv12ef54cf6b6f3

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1149 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.