68/100

Moderate evidence

GainPublished recordHealthGood Space

Artificial intelligence-enhanced electrocardiography for detection and prediction of dilated cardiomyopathy

Truvace record
TRV-2026-2934raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
6bd5f8583894…check it

Background and aims A major challenge in dilated cardiomyopathy (DCM) care is the identification and management of individuals at risk before disease manifestation. An artificial intelligence (AI) model applied to electrocardiography (ECG) was developed to detect and predict the echocardiographic DCM phenotype (left ventricular dilatation with systolic dysfunction) and was evaluated for its ability to stratify the risk of incident DCM in familial cohorts. Methods A deep learning model was trained to detect the e…

The gain

In a multi-cohort study, an AI model reading ECGs diagnosed the dilated cardiomyopathy phenotype with AUCs of .87-.97 and predicted future disease about as well as echocardiography (C-index .80-.87 versus .80-.90).

What this doesn’t fix

Positive predictive values in the familial cohorts were only 42.4% and 39.4%, so many people flagged high-risk did not develop disease; the tool's strength is ruling out short- to mid-term disease.

Sources

1 on file
  1. European Heart Journaldoi:10.1093/eurheartj/ehag917
    Peer-reviewed2026-11-13

Cite this record

v1

Truvace Impact Record TRV-2026-2934, v1: “Artificial intelligence-enhanced electrocardiography for detection and prediction of dilated cardiomyopathy.” Truvace, 2026-11-15. /record/TRV-2026-2934 (accessed on the day you copy it). sha256 6bd5f858389418f4…

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. Publishedv16bd5f8583894…

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