TRV-2026-2056Version 1 · Certified

Written 2026-10-21 01:08:59 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2056
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-21T01:08:59.113998Z
status: published
lens: g_space
sector: health
headline: Development of a machine learning-based risk warning model for potentially inappropriate medication use among older patients in a hematology service
dek: 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…
gain_title: 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.
problem_title: (none)
trace_subject: (none)
gain_reading: 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.
gain_evidence: The logistic regression model demonstrated the highest performance with 0.87 accuracy, 0.83 recall, 0.86 F1 score, and 0.91 AUC. | can be considered a reliable early warning mechanism for clinical pharmacists and physicians
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built and compared seven classification algorithms to predict which hospitalized patients over 65 in a university hospital hematology service in Türkiye were receiving potentially inappropriate medications. Inappropriate use was defined using the 2023 Beers Criteria, and the data covered admissions from 2018 to 2020.

Older hematology patients often have several conditions and complex drug regimens, so automated screening could help prompt timely medication review. Because the work is a small retrospective pilot at a single center, it shows technical promise but not yet proof of effects on patient care.
limitation: 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.
tag: Evidence-backed gain
key_points: The study was retrospective and covered patients over 65 admitted to a hematology service between 2018 and 2020. | It included 190 patients, and 45.8% of them had potentially inappropriate medication use. | Seven classification algorithms were compared using accuracy, precision, recall, F1 score, ROC curve, AUC, and Brier score. | Logistic regression performed best, with 0.87 accuracy, 0.83 recall, 0.86 F1 score, and 0.91 AUC.
rundown: The model was designed as a patient-based automated screening tool to support clinical pharmacists and physicians. Its target is the identification of potentially inappropriate medication use so that medication review can happen sooner.

Methodologically, the team used Python version 3.12.7 and stratified 5-fold cross-validation to estimate performance. Potentially inappropriate medications were labeled according to the American Geriatrics Society's 2023 Beers Criteria.

Nearly half of the cohort, 45.8%, had at least one potentially inappropriate medication, which indicates the issue is common in this population and the screening need is substantial.
sources:
- peer_reviewed | Journal of Oncology Pharmacy Practice | https://doi.org/10.1177/10781552261499304 | 2026-10-19
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
2b194af7669f2b5702d45b2136a6b3c3198ed6b2db67c1db4c2dde6a8ef76bf5
previous
0000000000000000000000000000000000000000000000000000000000000000
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.