TRV-2026-2093Certified recordPeer-reviewed

Toward Explainable AI for Acute Kidney Injury Prediction in the ICU: Transparent Development, Internal Validation, and Robustness Auditing of Machine Learning Models

Background/Objectives: Acute kidney injury (AKI) is common in critical care, yet predictive artificial intelligence studies often differ in outcome definitions, validation, calibration, and interpretability. We developed and internally validated machine learning models for newly observed serum-creatinine-defined AKI after a fixed 24 h ICU landmark and then audited how stable the selected model was to clinically important observation and timing choices. Methods: Using MIMIC-IV v3.1, we retained one first ICU stay…

Health · Problem Space — documented harm · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — problem

The model's outcome ascertainment depended on observation, so many eligible patients had indeterminate outcomes and calibration and threshold performance shifted under stricter observation rules.

What this doesn’t fix

The study provides no external validation, patient-level explanation validation, or evidence of clinical benefit, and its outcome ascertainment depended on observation, leaving many patients with indeterminate outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2093, v1: “Toward Explainable AI for Acute Kidney Injury Prediction in the ICU: Transparent Development, Internal Validation, and Robustness Auditing of Machine Learning Models.” Truvace, 2026-10-21. /record/TRV-2026-2093 (accessed at citation time). sha256 ef756d84fc1bf148…

Calibration history

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

  1. Certifiedv1ef756d84fc1b…

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