TRV-2026-2056Certified recordPeer-reviewed

Development of a machine learning-based risk warning model for potentially inappropriate medication use among older patients in a hematology service

IntroductionOlder hematology patients often have multiple comorbidities and receive complex medication therapies; this can increase the risk of potentially inappropriate medication (PIM) use. A machine learning model could potentially serve as an automated screening and warning tool to facilitate the identification of PIM and support timely medication review in these patients. The aim of this study is to develop machine learning-based model that provide warnings regarding PIMs use in elderly patients hospitalize…

Health · Good Space — documented gain · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

A logistic regression model trained on 190 older hematology inpatients identified potentially inappropriate medication use with 0.91 AUC, suggesting a usable early-warning screen for pharmacists and physicians.

What this doesn’t fix

The work is a retrospective pilot study of 190 patients from one university hospital in Türkiye, so it does not show whether the model works prospectively or improves clinical outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2056, v1: “Development of a machine learning-based risk warning model for potentially inappropriate medication use among older patients in a hematology service.” Truvace, 2026-10-21. /record/TRV-2026-2056 (accessed at citation time). sha256 2b194af7669f2b57…

Calibration history

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

  1. Certifiedv12b194af7669f…

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