TruaceTracing the truth around AIMonday, July 20, 2026
TRV-2026-0331Certified recordPeer-reviewed

Sex differences in CT-FFR of myocardial bridging with or without atherosclerosis: an AI-based quantitative study

Background: Myocardial bridging (MB) is a prevalent coronary anomaly with potential links to major adverse cardiac events. While computed tomography-derived fractional flow reserve (FFRCT) offers a non-invasive functional assessment, current evidence predominantly treats MB as a homogeneous entity, overlooking potential sex differences in hemodynamic impact. Existing studies often fail to distinguish between isolated MB and MB with concomitant atherosclerosis, and rarely employ sex-stratified analyses. This stud…

Health · The Trace — both readings · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — gain

An AI-based platform for CT-derived fractional flow reserve enabled noninvasive, sex-stratified quantification of hemodynamic impact in LAD myocardial bridging, showing distinct distal flow patterns and supporting risk stratification.

Current reading — problem

In patients with LAD myocardial bridging, longer bridging length increased risk of abnormal FFRCT, with a larger effect in females, and females with isolated bridging had more pronounced distal hemodynamic compromise.

What this doesn’t fix

Retrospective cohort limited to LAD-MB patients and findings described as preliminary, limiting generalizability beyond this anatomy and design.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0331, v1: “Sex differences in CT-FFR of myocardial bridging with or without atherosclerosis: an AI-based quantitative study.” Truvace, 2026-07-20. /record/TRV-2026-0331 (accessed at citation time). sha256 1918293dc0b9efcf

Calibration history

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

  1. Certifiedv11918293dc0b9

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