TRV-2026-1960Version 1 · Certified

Written 2026-10-20 01:10:10 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1960
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-20T01:10:10.564414Z
status: published
lens: g_space
sector: health
headline: Validation of an Electronic Health Record Model for Unplanned Readmission in Patients With Heart Failure
dek: Risk scores aim to predict 30-day heart failure (HF) readmissions. Current models, including Epic's Risk of Unplanned Readmission for a 30-Day Event, demonstrate modest to moderate discriminatory ability (area under the curve: 0.59-0.72). The goals of this study were to create an electronic health record (EHR)-automatable 30-day HF readmission risk calculator; to test the accuracy of Epic's model to predict 30-day HF readmission risk; and to compare the 2 models. To derive our EHR-automatable model using machine…
gain_title: A machine-learning risk calculator built from automatable EHR data predicted 30-day heart failure readmission about as well as Epic's commercial model, giving hospitals an independently derived alternative.
problem_title: (none)
trace_subject: (none)
gain_reading: A machine-learning risk calculator built from automatable EHR data predicted 30-day heart failure readmission about as well as Epic's commercial model, giving hospitals an independently derived alternative.
gain_evidence: the derived EHR risk score had a C-statistic of 0.76 (P = 0.41), suggesting comparable performance | the independently derived model provides a platform for future enhancement
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built an electronic health record model that uses machine learning to estimate which heart failure patients will be readmitted within 30 days. They based its design on a systematic review of earlier 30-day heart failure risk prediction models, then tested it against Epic's Risk of Unplanned Readmission model.

The result matters because risk scores help direct care resources to the patients who need them most. Both tools showed only moderate discrimination, so neither is a precise predictor, and the source says the new model mainly offers a base for later improvements.
limitation: Both models achieved only moderate discrimination, and the difference between them was not statistically significant, so the new model is not shown to be better.
tag: Evidence-backed gain
key_points: Prior readmission models, including Epic's, had reported area under the curve values of 0.59 to 0.72. | Epic's model scored a C-statistic of 0.74 in this evaluation. | The newly derived EHR-automatable score reached a C-statistic of 0.76, with a P value of 0.41 for the difference. | The authors suggest adding electrocardiogram-based artificial intelligence diagnostics in future versions.
rundown: The study had three goals: to create an EHR-automatable 30-day heart failure readmission risk calculator, to test the accuracy of Epic's model, and to compare the two. The new model was derived with machine learning after a systematic review of existing prediction models.

The comparison found 0.74 for Epic's model and 0.76 for the new one, a difference that was not statistically significant. The authors read this as comparable performance, and both models were described as having moderate discrimination.

The authors frame risk scores as a means of personalizing care and accelerating resources for those who need them most. They describe the independently derived model as a platform for enhancements such as ECG-based AI diagnostics.
sources:
- peer_reviewed | JACC: Case Reports | https://doi.org/10.1016/j.jaccas.2026.110618 | 2026-10-16
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
ed9b635793809d196d0c1f9915064ae4986da096660ca51afc4031a1cc26d7de
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1960 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.