TRV-2026-2078Certified recordPeer-reviewed

Performance of artificial intelligence-based coronary CT angiography-derived fractional flow reserve across cohorts with different prevalence of obstructive coronary artery disease

Background Coronary computed tomography angiography (CCTA) provides accurate anatomical assessment of coronary stenosis severity but has limited ability to determine lesion-specific ischemia as assessed by invasive fractional flow reserve (FFR). We aimed to evaluate the diagnostic performance of an artificial intelligence-based deep learning CCTA-derived FFR model (CT-FFR AI ) in cohorts undergoing CCTA and invasive FFR as part of a study protocol and a real-world cohort undergoing invasive FFR based on suspecte…

Health · Good Space — documented gain · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

In a real-world cohort of 202 patients, the AI CT-FFR model identified lesion-specific ischemia more accurately per vessel (63%) than CCTA stenosis thresholds of 50% (52%) or 70% (57%).

What this doesn’t fix

The authors state that diagnostic accuracy of the AI model depends on the prevalence of obstructive coronary artery disease and the range of stenosis severities in the vessels assessed, and it performed comparably to CCTA in the study cohort.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2078, v1: “Performance of artificial intelligence-based coronary CT angiography-derived fractional flow reserve across cohorts with different prevalence of obstructive coronary artery disease.” Truvace, 2026-10-21. /record/TRV-2026-2078 (accessed at citation time). sha256 6db2b8217520d8d6…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv16db2b8217520…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2078 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.