Moderate evidence
Published recordHealthGood Space
More
Vascular risk prediction in migraine: A multimodality risk score based on artificial intelligence-electrocardiogram output, echocardiogram, and detailed migraine characteristics
- Truvace record
- TRV-2026-3016raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 2bf8aab2f367…check it
AimPatients with migraine, especially those with aura, have a higher risk of stroke and other vascular events. However, the underlying mechanisms are complex, multifactorial, and may require integration of multimodal data for comprehensive characterization. We have conducted prior analyses on how artificial intelligence (AI)-enabled electrocardiogram (ECG), specifically the atrial fibrillation prediction model and age estimation model output, echocardiogram parameters, and detailed migraine characteristics separ…
The gain
In a Mayo Clinic retrospective study of 297 migraine patients, those scoring 15 or higher on a risk score combining AI-ECG output, echocardiogram and migraine features had a hazard ratio of 3.83 for stroke, heart attack, clot or death versus lower scorers.
What this doesn’t fix
The authors describe this as a pilot, proof-of-concept evaluation in 297 patients, and say external validation and real-world clinical assessment are still necessary.
Sources
1 on file- Cephalalgiadoi:10.1177/03331024261505811
Cite this record
v1Truvace Impact Record TRV-2026-3016, v1: “Vascular risk prediction in migraine: A multimodality risk score based on artificial intelligence-electrocardiogram output, echocardiogram, and detailed migraine characteristics.” Truvace, 2026-11-18. /record/TRV-2026-3016 (accessed on the day you copy it). sha256 2bf8aab2f3672b5d…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3016 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.
ace