Moderate evidence
Published recordHealthProblem Space
More
Performance of AI models in ECG interpretation and risk stratification for major adverse cardiac events in the emergency department
- Truvace record
- TRV-2026-3038raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 947de7a26699…check it
BackgroundArtificial intelligence (AI) may support electrocardiogram (ECG) interpretation and risk stratification in emergency departments, but its clinical utility remains uncertain.ObjectiveTo evaluate the performance of ChatGPT and Gemini in ECG interpretation and risk stratification for major adverse cardiac events (MACE).MethodsIn 89 prospective ED patients presenting with chest pain or palpitations, ECGs evaluated by AI models and emergency specialists were compared against cardiologist consensus. Cohen's…
The problem
In a prospective study of 89 emergency department patients with chest pain or palpitations, ChatGPT (κ = 0.386) and Gemini (κ = 0.224) agreed with cardiologists far less on ECG reads than emergency specialists did (κ = 0.689-0.874).
What this doesn’t fix
This was a single-center pilot cohort of 89 patients with an exploratory MACE analysis, so the findings are preliminary and need multi-center validation.
Sources
1 on file- Technology and Health Caredoi:10.1177/09287329261509123
Cite this record
v1Truvace Impact Record TRV-2026-3038, v1: “Performance of AI models in ECG interpretation and risk stratification for major adverse cardiac events in the emergency department.” Truvace, 2026-11-19. /record/TRV-2026-3038 (accessed on the day you copy it). sha256 947de7a26699dea5…
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-3038 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