60/100

Moderate evidence

GainPublished recordHealthGood Space

A machine learning model for predicting hospitalist consult appropriateness among elective joint arthroplasty patients: A single-center experience with hospitalist comanagement screening

Truvace record
TRV-2026-3032raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
6f2600f93576…check it

Hospitalist comanagement improves outcomes for total joint arthroplasty (TJA) patients, but is a limited resource, and data on which patients are most likely to benefit are sparse. A total of 400 unique TJA patients and their post-operative trajectories were analyzed retrospectively to determine which patients warranted comanagement, defined by hospitalists making meaningful contributions to post-operative care. From this data, a random forest machine learning (ML) model was developed to predict hospitalist cons…

The gain

In a retrospective analysis of 400 joint replacement patients at one hospital, a random forest model identified 97.0% of patients who warranted hospitalist comanagement versus 91.8% for current physician-led screening, with specificity of 46.3% versus 37.8%.

What this doesn’t fix

Specificity stayed below 0.5 for both the model and current screening, so many patients who did not need comanagement would still be flagged, and the authors describe the model as performing only comparably to physician screening.

Sources

1 on file
  1. Journal of Hospital Medicinedoi:10.1002/jhm.70554
    Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3032, v1: “A machine learning model for predicting hospitalist consult appropriateness among elective joint arthroplasty patients: A single-center experience with hospitalist comanagement screening.” Truvace, 2026-11-18. /record/TRV-2026-3032 (accessed on the day you copy it). sha256 6f2600f93576b0cc…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv16f2600f93576…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3032 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.