TRV-2026-2080Certified recordPeer-reviewed

Imaging-derived coronary fractional flow reserve: advances in physics-based, machine learning, and physics-informed methods

Purpose of Review Imaging-derived fractional flow reserve (FFR) is rapidly evolving beyond conventional computational fluid dynamics (CFD)-based pipelines toward machine learning (ML), deep learning (DL), and physics-informed approaches that enable fast, wire-free, and scalable functional assessment of coronary artery stenosis. This review synthesizes recent advances in computed tomography (CT)-and angiography-based FFR measurement, with particular emphasis on emerging physics-informed neural networks and neural…

Science · The Trace — both readings · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

ML, deep learning and physics-informed models can predict coronary pressure and FFR quickly and automatically from imaging, offering wire-free, scalable functional assessment of artery narrowing.

Current reading — problem

Machine learning FFR models can perform inconsistently across hospitals and are sensitive to domain shift, differing acquisition protocols and image quality, with interpretability challenges.

What this doesn’t fix

The source is a narrative review rather than a new trial, and it states that physics-informed methods only 'may' offer better robustness, with prospective multi-center validation still needed.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2080, v1: “Imaging-derived coronary fractional flow reserve: advances in physics-based, machine learning, and physics-informed methods.” Truvace, 2026-10-21. /record/TRV-2026-2080 (accessed at citation time). sha256 542784a4434a7b53…

Calibration history

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

  1. Certifiedv1542784a4434a…

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