Moderate evidence
Published recordHealthGood Space
More
Retrieval-augmented generation models for predicting pathological upgrading in endoscopically resected gastric low-grade intraepithelial neoplasia: A dual-center evaluation
- Truvace record
- TRV-2026-3082raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- a6b35bae2659…check it
BACKGROUND Gastric low-grade intraepithelial neoplasia (LGIN) exhibits highly variable clinical outcomes. The discordance between histological findings from endoscopic forceps biopsy and endoscopic submucosal dissection (ESD) complicates the formulation of appropriate treatment strategies. AIM To evaluate a prediction framework using large language models (LLMs) enhanced with retrieval-augmented generation (RAG) for the pathological upgrading of gastric LGIN. METHODS We retrospectively enrolled 329 patients with…
The gain
In a retrospective study of 329 patients with 372 gastric lesions, AI language models given a literature knowledge base predicted which low-grade lesions were upgraded after removal with an AUC of 0.873, comparable to two experienced endoscopists.
What this doesn’t fix
The study was retrospective, and the authors say the models may support clinical decision-making only pending prospective validation.
Sources
1 on file- World Journal of Gastroenterologydoi:10.3748/wjg.122422
Cite this record
v1Truvace Impact Record TRV-2026-3082, v1: “Retrieval-augmented generation models for predicting pathological upgrading in endoscopically resected gastric low-grade intraepithelial neoplasia: A dual-center evaluation.” Truvace, 2026-11-20. /record/TRV-2026-3082 (accessed on the day you copy it). sha256 a6b35bae2659c6d1…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3082 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.
ace