63/100

Moderate evidence

GainPublished recordHealthGood Space

Fully Automated, Explainable AI Analysis of Coronary CTA Improves Prediction of Major Cardiovascular Events

Truvace record
TRV-2026-3087raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
f163b0e702b9…check it

Coronary artery disease (CAD) remains a major global cause of morbidity and mortality. Coronary computed tomography angiography (CCTA) is central to noninvasive diagnosis and risk assessment, yet current workflows are labor-intensive and depend on semiquantitative scoring systems that do not fully leverage prognostic information in CCTA. The objectives of the study were to develop and validate a fully automated, explainable artificial intelligence (AI) system (AI-automated coronary analysis [ACA]) for comprehens…

The gain

In a retrospective study of 1,702 patients, a fully automated AI analysis of coronary CT scans predicted major cardiovascular events with an AUC of 0.81, versus 0.76 for the Agatston calcium score and 0.67 for demographic risk markers.

What this doesn’t fix

Prognostic performance was comparable to AI-CADRADS and only modestly higher than the Agatston score, and the study was a retrospective cohort rather than a prospective trial.

Sources

1 on file
  1. JACC: Advancesdoi:10.1016/j.jacadv.2026.103461
    Peer-reviewed2026-11-19

Cite this record

v1

Truvace Impact Record TRV-2026-3087, v1: “Fully Automated, Explainable AI Analysis of Coronary CTA Improves Prediction of Major Cardiovascular Events.” Truvace, 2026-11-21. /record/TRV-2026-3087 (accessed on the day you copy it). sha256 f163b0e702b98918…

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

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