TRV-2026-1934Certified recordPeer-reviewed

Clinical significance of intraoperative dissection time and machine learning-based prediction in laparoscopic distal gastrectomy for gastric cancer

Background Establishing a clinically meaningful cutoff value for intraoperative dissection time and developing predictive models for this metric among patients with distal gastric cancer. Methods This retrospective multicenter study included 849 patients with distal gastric cancer who underwent laparoscopic distal gastrectomy between November 2020 and May 2025 at three tertiary centers. Using postoperative complications as the status variable, determine the optimal cutoff value for intraoperative dissection time…

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

Current reading — gain

Machine learning models identified patients likely to need long dissection time (over 133 minutes), a threshold linked to more postoperative complications, which may help preoperative risk evaluation.

What this doesn’t fix

The study is retrospective, and although prolonged dissection time was associated with worse survival in unadjusted analysis, it was not an independent prognostic factor after adjustment.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1934, v1: “Clinical significance of intraoperative dissection time and machine learning-based prediction in laparoscopic distal gastrectomy for gastric cancer.” Truvace, 2026-10-19. /record/TRV-2026-1934 (accessed at citation time). sha256 75c27af545167cc4…

Calibration history

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

  1. Certifiedv175c27af54516…

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