68/100

Moderate evidence

GainPublished recordHealthGood Space

A Clinically Weighted Transformer-Based Deep Learning Model for Automated FLIP Panometry v2.0 Interpretation

Truvace record
TRV-2026-3084raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
8ccb1b775c6a…check it

Functional lumen imaging probe (FLIP) Panometry evaluates esophageal motility by measuring contractile responses and esophagogastric junction opening, but interpretation requires expertise and varies between readers. We aimed to develop a transformer-based deep learning model for automated FLIP Panometry v2.0 interpretation, incorporating a clinically weighted cost matrix that penalizes clinically consequential errors. 984 adults who underwent FLIP Panometry and high-resolution manometry (HRM) were included. Exp…

The gain

In a single-center study of 984 adults, a transformer model matched expert readings of FLIP Panometry esophageal tests in 83.5% of six-category test cases and 94% of normal versus not-normal calls, with 97% sensitivity.

What this doesn’t fix

The cohort was selected and drawn from a single center, and the authors state that external validation is required before clinical use.

Sources

1 on file
  1. Clinical Gastroenterology and Hepatologydoi:10.1016/j.cgh.2026.10.036
    Peer-reviewed2026-11-19

Cite this record

v1

Truvace Impact Record TRV-2026-3084, v1: “A Clinically Weighted Transformer-Based Deep Learning Model for Automated FLIP Panometry v2.0 Interpretation.” Truvace, 2026-11-21. /record/TRV-2026-3084 (accessed on the day you copy it). sha256 8ccb1b775c6af3bb…

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

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