TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0688Certified recordPeer-reviewed

Machine learning-assisted prediction of 5-year mortality in chronic kidney disease: the KoreaN cohort study for Outcome in patients With Chronic Kidney Disease (KNOW-CKD)

Mortality prediction models for patients with non-dialysis chronic kidney disease (CKD) remain limited despite their clinical importance. While machine learning (ML) offers the potential to improve prediction accuracy, its "black-box" nature has hindered clinical adoption. This study aimed to develop and validate an interpretable ML model for predicting 5-year all-cause mortality in patients with non-dialysis CKD and to deploy it as a user-friendly web-based risk stratification tool. We analyzed 1,858 patients (…

Health · The Trace — both readings · certified 2026-08-08 · v1 · article view · machine-readable

Current reading — gain

A CatBoost model trained on 1,858 non-dialysis CKD patients predicted 5-year all-cause mortality with AUC 0.813, outperforming logistic regression, and a simplified 5-feature version maintained AUC 0.795 in external validation.

Current reading — problem

Machine learning's black-box nature has hindered clinical adoption of mortality prediction models for non-dialysis CKD despite their clinical importance.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0688, v1: “Machine learning-assisted prediction of 5-year mortality in chronic kidney disease: the KoreaN cohort study for Outcome in patients With Chronic Kidney Disease (KNOW-CKD).” Truvace, 2026-08-08. /record/TRV-2026-0688 (accessed at citation time). sha256 4591b50000d05bef

Calibration history

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

  1. Certifiedv14591b50000d0

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