70/100

Moderate evidence

GainPublished recordHealthGood Space

Deep learning for predicting high-grade dysplasia in colorectal polyps using white-light endoscopy

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

BACKGROUND Accurate identification of high-grade dysplasia (HGD) in colorectal polyps is important for optimizing endoscopic management and surveillance strategies. Although deep learning has shown potential for colorectal polyp characterization, the generalizability of white-light imaging (WLI)-based models across independent clinical settings remains insufficiently established. AIM To develop and externally validate a deep learning model based on routine WLI images for predicting HGD in colorectal polyps, to e…

The gain

In a retrospective study at three Chinese hospitals, an AI model flagged high-grade dysplasia in colorectal polyp photos with AUCs of 0.814 and 0.803 in two outside cohorts, matching senior endoscopists and beating junior ones on 149 images.

What this doesn’t fix

The outside cohorts held only 20 and 26 high-grade cases, and the retrospective study used one hand-picked static image per polyp at three tertiary Chinese hospitals, so the model has not been tested in live colonoscopy.

Sources

1 on file
  1. Peer-reviewed2027-01-21

Cite this record

v1

Truvace Impact Record TRV-2026-3091, v1: “Deep learning for predicting high-grade dysplasia in colorectal polyps using white-light endoscopy.” Truvace, 2026-11-22. /record/TRV-2026-3091 (accessed on the day you copy it). sha256 d9eb385e820e5430…

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

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