TRV-2026-1891Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1891 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-19T10:42:07.607822Z status: published lens: p_space sector: health headline: Predicting the Risk of Unplanned Hospital Encounters in Hemodialysis Patients: A Comparison Between Clinicians and a Machine Learning Prediction Algorithm dek: 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… gain_title: (none) problem_title: 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. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: 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. problem_evidence: Clinicians demonstrated a higher positive predictive value (PPV) for a UHE in the subsequent 7 days (0.14 for clinicians vs 0.07 for the ML model; P < 0.001) quick_read: Researchers built a machine learning model that uses demographic, clinical, and dialysis session data, updated weekly, to estimate which hemodialysis patients will have an emergency visit or hospitalization within 7 or 30 days. They then compared its predictions with those made by clinicians for a separate group of patients. The model caught many more future events than clinicians, particularly over 30 days, which could help target preventive attention. However, its 7-day precision was lower, and the authors say it remains unknown whether using the tool in care would actually reduce unplanned hospital encounters. limitation: 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. tag: Evidence-backed problem key_points: The model was developed using 627 maintenance hemodialysis patients treated at an academic hospital between October 2015 and April 2022. | A separate group of 285 patients was used to compare model predictions with clinician predictions. | At 7 days, sensitivity was 0.63 for the model versus 0.25 for clinicians, while PPV was 0.07 versus 0.14. | At 30 days, PPV was comparable (0.21 model, 0.25 clinicians; P = 0.54), but sensitivity was 0.73 versus 0.24. rundown: Dialysis patients are hospitalized more often than the age-matched general population, and unplanned hospital encounters, which include emergency department visits and hospitalizations, may be preventable but are hard to anticipate. The study aimed to stratify risk using predictors updated weekly. The comparison showed a trade-off. Clinicians were more precise for 7-day events, meaning a higher share of their flagged patients had an event, but they missed most events. The model found a much larger share of events at both horizons. The authors conclude that the model anticipates events with greater sensitivity than clinicians at comparable PPV, and that further research must determine whether integrating the tool into clinical care leads to fewer unplanned encounters. sources: - peer_reviewed | Kidney Medicine | https://doi.org/10.1016/j.xkme.2026.101500 | 2026-08-13 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 2c98139e50dd09014d6bab0d3249a12d35c62b71918af02d0e27f1acd657e92b
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
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.
ace