TRV-2026-2078Version 1 · Certified

Written 2026-10-21 06:54:25 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2078
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-21T06:54:25.758637Z
status: published
lens: g_space
sector: health
headline: Performance of artificial intelligence-based coronary CT angiography-derived fractional flow reserve across cohorts with different prevalence of obstructive coronary artery disease
dek: 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…
gain_title: 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%).
problem_title: (none)
trace_subject: (none)
gain_reading: 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%).
gain_evidence: CT-FFR AI demonstrated higher per-vessel diagnostic accuracy (63%) compared with CCTA using ≥50% and ≥70% stenosis thresholds (52% and 57%, respectively
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers tested a deep learning tool called CT-FFR AI (CorEx, SPIMED-AI) that estimates fractional flow reserve from coronary CT angiography images. They checked it against invasive FFR measurements in two groups: 208 patients in the PACIFIC-1 study and 202 patients from routine care who had a CCTA lesion of at least 70% stenosis.

In the study cohort, the AI model performed about as well as stenosis-based CCTA reads, while in the real-world cohort it was clearly more accurate. This suggests that the tool's value depends on how common obstructive disease is and on the spread of stenosis severity in the vessels being assessed, so results from one setting may not carry over to another.
limitation: 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.
tag: Evidence-backed gain
key_points: In PACIFIC-1 (612 vessels), per-vessel accuracy was 77% for CT-FFR AI versus 76% for a 50% stenosis threshold and 74% for a 70% threshold, with no significant difference. | In the real-world cohort (325 vessels), CT-FFR AI reached 63% accuracy versus 52% and 57% for the 50% and 70% CCTA thresholds. | The study's added-value measure beyond CCTA was 7.9% (P = 0.256) and 17.7% (P = 0.012) in PACIFIC-1, versus 23.2% in the real-world cohort. | The authors conclude CT-FFR AI may outperform anatomic assessment alone, depending on disease prevalence.
rundown: The two cohorts differed in design. PACIFIC-1 patients had invasive FFR in all major coronary vessels regardless of CCTA findings. The real-world cohort included only patients with at least one CCTA-defined lesion of 70% or more stenosis who went on to invasive angiography with FFR.

The evaluation used an intention-to-diagnose approach, comparing the AI model with CCTA at 50% and 70% stenosis cutoffs, with invasive FFR as the reference standard.

Background context: CCTA gives accurate anatomical assessment of stenosis but has limited ability to determine lesion-specific ischemia, which is the gap the AI-derived FFR is meant to address.
sources:
- peer_reviewed | Journal of Cardiovascular Computed Tomography | https://doi.org/10.1016/j.jcct.2026.10.003 | 2026-10-19
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
6db2b8217520d8d6f328ebf5abcca697d5ef37ef5c9f400eb11842debe60f478
previous
0000000000000000000000000000000000000000000000000000000000000000
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.