TRV-2026-1754Certified recordPeer-reviewed

Deep Learning-Based Detection of Sessile Serrated Lesions in Colonoscopy Images: Optimization of a YOLOv3 Framework With Mucus Cap Feature Enhancement for Sessile Serrated Lesion Detection

Background and aim Sessile serrated lesions (SSLs) are difficult to detect during colonoscopy via standard white-light imaging (WLI) because they are flat, have indistinct borders, and are often hidden by mucus caps. Although narrowband imaging (NBI) can help, its effectiveness is inconsistent. This study evaluated the feasibility of an artificial intelligence (AI)-assisted approach incorporating mucus cap features and both WLI and NBI for SSL detection and diagnosis. Methods This study developed an AI model for…

Health · Good Space — documented gain · certified 2026-10-17 · v1 · article view · machine-readable

Current reading — gain

Adding mucus cap screening to a YOLOv3-based model raised lesion-level detection of sessile serrated lesions from 77.4% to 95.0% in the study's colonoscopy images.

What this doesn’t fix

The authors state that prospective and multicenter studies are required before reliable clinical deployment, and describe the work as an incremental step toward generalizability.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1754, v1: “Deep Learning-Based Detection of Sessile Serrated Lesions in Colonoscopy Images: Optimization of a YOLOv3 Framework With Mucus Cap Feature Enhancement for Sessile Serrated Lesion Detection.” Truvace, 2026-10-17. /record/TRV-2026-1754 (accessed at citation time). sha256 2c04a105d8b02fd6…

Calibration history

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

  1. Certifiedv12c04a105d8b0…

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