TRV-2026-1918Certified recordPeer-reviewed

Three-dimensional anatomical classification and machine learning prediction of the P6a-right hepatic vein relationship: surgical implications for laparoscopic right anterior sectionectomy

Background The spatial relationship between the ventral branch of segment VI portal vein (P6a) and the right hepatic vein (RHV) significantly influences the anatomical complexity of the right hepatic fissure and the surgical outcomes of laparoscopic right anterior sectionectomy (LRAS). The ventral-P6a variant is often associated with higher surgical risks, yet preoperative prediction remains challenging. Methods This retrospective study included 100 patients who underwent triple-phase enhanced CT of the upper ab…

Lifestyle · Good Space — documented gain · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — gain

A logistic regression model using 3D CT anatomical measurements predicted whether the P6a portal branch lay ventral or dorsal to the right hepatic vein, offering a basis for preoperative risk assessment in laparoscopic right anterior sectionectomy.

What this doesn’t fix

The study was retrospective and included only 100 patients, and it assessed prediction of anatomical classification rather than demonstrating improved surgical outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1918, v1: “Three-dimensional anatomical classification and machine learning prediction of the P6a-right hepatic vein relationship: surgical implications for laparoscopic right anterior sectionectomy.” Truvace, 2026-10-19. /record/TRV-2026-1918 (accessed at citation time). sha256 659ab8edfb43616b…

Calibration history

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

  1. Certifiedv1659ab8edfb43…

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