TRV-2026-1221Certified recordPeer-reviewed

Machine learning-based nomogram for acute kidney injury after liver transplantation

Acute kidney injury (AKI) after liver transplantation (LT) is a frequent complication associated with adverse outcomes, yet practical early postoperative prediction tools remain limited. This retrospective study developed and internally validated an interpretable model for AKI after LT using perioperative variables available by the time of the first urgent postoperative blood test, generally obtained within 1 h after surgery. Adult LT recipients treated from June 2023 to January 2026 were screened. AKI was defin…

Health · Good Space — documented gain · certified 2026-09-30 · v1 · article view · machine-readable

Current reading — gain

An interpretable machine learning nomogram using eGFR, anhepatic phase time, postoperative log D-dimer and ALT available within 1 hour after liver transplantation predicted AKI with AUC 0.861 in training and 0.761 in validation, with SVM reaching 0.846, to enable early identification for intensified renal monitoring.

What this doesn’t fix

Model was internally validated only and requires external multicenter validation before routine clinical use, limiting generalizability beyond the single-center retrospective cohort of 127 patients.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1221, v1: “Machine learning-based nomogram for acute kidney injury after liver transplantation.” Truvace, 2026-09-30. /record/TRV-2026-1221 (accessed at citation time). sha256 5d9a62a303edb27d…

Calibration history

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

  1. Certifiedv15d9a62a303ed…

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