TRV-2026-1891Certified recordPeer-reviewed

Predicting the Risk of Unplanned Hospital Encounters in Hemodialysis Patients: A Comparison Between Clinicians and a Machine Learning Prediction Algorithm

Rationale & objective: Dialysis patients have a higher risk of hospitalization than the age-matched general population. Unplanned hospital encounters (UHEs), including emergency department visits and hospitalizations, may be preventable but are difficult to anticipate. We aimed to stratify dialysis patients' risk of UHE, using a machine learning (ML)-based prediction model. Study design: We created an ML-based prediction model to stratify hemodialysis (HD) patients' risk of UHE in the subsequent 7 and 30 day…

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

Current reading — problem

For 7-day predictions the model was less precise than clinicians, so it produced proportionally more false alarms, and whether it reduces hospital encounters is not yet shown.

What this doesn’t fix

The model was developed only in hemodialysis patients at a single center, which limits external validation, and its effect on reducing unplanned encounters has not yet been tested.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1891, v1: “Predicting the Risk of Unplanned Hospital Encounters in Hemodialysis Patients: A Comparison Between Clinicians and a Machine Learning Prediction Algorithm.” Truvace, 2026-10-19. /record/TRV-2026-1891 (accessed at citation time). sha256 2c98139e50dd0901…

Calibration history

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

  1. Certifiedv12c98139e50dd…

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