TRV-2026-1754Version 1 · Certified

Written 2026-10-17 22:02:51 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1754
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-17T22:02:51.337811Z
status: published
lens: g_space
sector: health
headline: 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
dek: 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…
gain_title: 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.
problem_title: (none)
trace_subject: (none)
gain_reading: 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.
gain_evidence: Lesion-level detection improved from 77.4% with the conventional model to 95.0% after incorporation of mucus cap screening
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built an AI model to find sessile serrated lesions, which are flat, indistinct and often covered by mucus, in colonoscopy images. They trained it on 1980 images collected between 2023 and 2025 and added mucus cap features to a standard detection framework.

The results suggest that targeting mucus caps can make AI detection of these easily missed lesions more reliable, but the evidence comes from images rather than live procedures. The authors call it an incremental step and say prospective, multicenter studies are needed before clinical deployment.
limitation: The authors state that prospective and multicenter studies are required before reliable clinical deployment, and describe the work as an incremental step toward generalizability.
tag: Evidence-backed gain
key_points: Image-level accuracy was 98.7%, with 100.0% sensitivity and 97.4% specificity. | Detection rates were 95.9% for lesions without a mucus cap and 98.4% for lesions with one. | For morphology-based typing, the white-light model reached 85.8% accuracy (AUC 0.89). | The narrowband imaging model performed better at typing, with 91.6% accuracy (AUC 0.94).
rundown: Sessile serrated lesions are hard to detect with standard white-light imaging because they are flat, have indistinct borders and are often hidden by mucus caps. Narrowband imaging can help, but the study describes its effectiveness as inconsistent.

The team evaluated an AI approach that uses both white-light and narrowband imaging and builds mucus cap features into the detection framework. Performance was measured by detection rate, accuracy and AUC.

The authors describe the work as real-world clinical evidence that supports AI models for these lesions and helps improve generalizability across clinical settings, while noting it is not a novel framework.
sources:
- peer_reviewed | Journal of Gastroenterology and Hepatology | https://doi.org/10.1111/jgh.70712 | 2026-10-07
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
2c04a105d8b02fd652ee341168158cd90d72f7f0c213e2512353285e9010a750
previous
0000000000000000000000000000000000000000000000000000000000000000
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.