60/100

Moderate evidence

Published recordHealthGeneral

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

Truvace record
TRV-2026-1221raw data (JSON)
Version
v3Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
1aa319bc05c0…check it

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…

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

Sources

1 on file
  1. Renal Failuredoi:10.1080/0886022x.2026.2698148
    Peer-reviewed2026-09-27

Cite this record

v3

Truvace Impact Record TRV-2026-1221, v3: “Machine learning-based nomogram for acute kidney injury after liver transplantation.” Truvace, 2026-11-05. /record/TRV-2026-1221 (accessed on the day you copy it). sha256 1aa319bc05c0e013…

Change history

3 versions

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

  1. Revisedv31aa319bc05c0…

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

  2. Revisedv251a75364504c…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain activity_only, problem absent).

  3. Publishedv15d9a62a303ed…

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