30/100

Emerging evidence

Published recordHealthGeneral

Artificial Intelligence in Endohepatology: Toward an Intelligent One-Stop Shop for Liver-Directed Endoscopy

Truvace record
TRV-2026-1138raw data (JSON)
Version
v3Revised
First published
Evidence type
Commentary, opinion, or narrative review
Sources
1 sourcePeer-reviewed
sha256
969bd1d69966…check it

Endohepatology (the implementation of contemporary advanced endoscopy in hepatology) has reached a point where endoscopic ultrasound (EUS)-guided liver biopsy, portal pressure gradient measurement, parenchymal elastography, and variceal screening and therapy can be integrated into a single procedural session of liver-directed endoscopy. Concurrently, artificial intelligence (AI) has revolutionized luminal endoscopy and is advancing rapidly across hepatology imaging, digital pathology, and outcome prediction, yet…

The problem

This narrative review maps this evolving convergence of AI and endohepatology across four functional pillars: intelligent hemodynamic assessment, virtual histology, precision tissue acquisition, and integrated risk stratification with therapeutic and decision support.

Sources

1 on file
  1. Peer-reviewed2026-09-18

Cite this record

v3

Truvace Impact Record TRV-2026-1138, v3: “Artificial Intelligence in Endohepatology: Toward an Intelligent One-Stop Shop for Liver-Directed Endoscopy.” Truvace, 2026-11-05. /record/TRV-2026-1138 (accessed on the day you copy it). sha256 969bd1d69966a0f1…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3969bd1d69966…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv2675ca14110cc…

    Direction audit: the problem line stated no AI consequence and was removed. Filed as context; not counted as a gain or a problem.

  3. Publishedv1d4f95c8b6bc4…

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