TRV-2026-2312Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2312 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-29T18:34:52.531264Z status: published lens: g_space sector: health headline: Diagnostic Accuracy of Artificial Intelligence for Detecting ST-Elevation Myocardial Infarction on 12-Lead Electrocardiograms: A Systematic Review and Meta-Analysis dek: Artificial intelligence (AI) may improve electrocardiographic detection of ST-elevation myocardial infarction (STEMI), but available studies address distinct diagnostic questions. We systematically reviewed studies evaluating AI-based STEMI detection from 12-lead electrocardiograms and separately synthesized AI performance against a clinical reference standard, AI and clinician performance against a clinical reference, and AI agreement with physician electrocardiogram (ECG) interpretation. PubMed, Embase, Web of… gain_title: Across 8 studies comparing both against a clinical reference, AI had higher sensitivity for STEMI than clinicians (0.91 versus 0.78) at equal specificity of 0.91. problem_title: (none) trace_subject: (none) gain_reading: Across 8 studies comparing both against a clinical reference, AI had higher sensitivity for STEMI than clinicians (0.91 versus 0.78) at equal specificity of 0.91. gain_evidence: sensitivity of 0.91 (0.86-0.94) for AI versus 0.78 (0.69-0.85) for clinicians | specificity of 0.91 (0.82-0.96) for both problem_reading: (none) problem_evidence: (none) quick_read: Researchers pooled 26 studies covering 539,876 electrocardiograms to see how well AI identifies ST-elevation myocardial infarction, a serious type of heart attack, from standard 12-lead tracings. They searched six databases covering January 2010 to March 10, 2025, and analysed three separate questions rather than one combined result. Faster and more sensitive ECG reading could matter for a condition where timely recognition affects treatment. However, the evidence is split across different comparison types, and the abstract reports only retrospective accuracy figures, so it does not show whether using AI changes patient outcomes in practice. limitation: The authors note that available studies address distinct diagnostic questions, so results were synthesised separately; the comparisons with clinicians rest on only 8 studies and confidence intervals for some estimates are wide. tag: Evidence-backed gain key_points: Twenty studies compared AI with a clinical reference standard: pooled sensitivity 0.95, specificity 0.95, AUC 0.98. | In 8 studies with both AI and clinicians, AI sensitivity was 0.91 versus 0.78 for clinicians, with specificity 0.91 for both. | In 7 studies using physician ECG interpretation as the comparator, AI sensitivity was 0.85 and specificity 0.99. | Sensitivity analyses excluding case-control designs and influential studies gave similar findings. rundown: The review searched PubMed, Embase, Web of Science, Scopus, Cochrane Library and ClinicalTrials.gov, and used bivariate random-effects models to pool sensitivity, specificity and summary AUC. It deliberately synthesised three diagnostic questions separately because the studies were not answering the same one. Against a clinical reference, the positive likelihood ratio was 19.2 and the negative likelihood ratio 0.05. In the clinician comparison, AUCs were 0.95 for AI and 0.90 for clinicians. Results held when restricting to deep learning models or raw waveform ECGs. sources: - peer_reviewed | Cardiology in Review | https://doi.org/10.1097/crd.0000000000001524 | 2026-10-29 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- bfad664e7951db5e910d95e60b12d9c2c077257a3cf0c0708ad2a04b706343ed
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2312 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.
ace