60/100

Moderate evidence

ProblemPublished recordHealthProblem Space

An application of random forest regression for predicting healthcare costs using administrative databases

Truvace record
TRV-2026-1163raw data (JSON)
Version
v4Revised
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
dfa962353f8b…check it

Background Accurate healthcare cost predictions are essential for health economic decision-making. We propose a bottom-up approach that aggregates individual-level predictions to estimate expenditures for specific population segments without relying on a priori segmentation. Methods This retrospective population-based study used administrative healthcare data (2011-2023) from the Health Protection Agency of Bergamo (Italy). We traced 5-year healthcare resource utilization to predict individual's healthcare costs…

The problem

In a retrospective study of Bergamo, Italy health data, random forest models predicting individual healthcare costs performed poorly and systematically underestimated high-cost users.

Sources

1 on file
  1. Peer-reviewed2026-09-21

Cite this record

v4

Truvace Impact Record TRV-2026-1163, v4: “An application of random forest regression for predicting healthcare costs using administrative databases.” Truvace, 2026-11-05. /record/TRV-2026-1163 (accessed on the day you copy it). sha256 dfa962353f8bd56b…

Change history

4 versions

Every change made to this record since it was first published, and why.

  1. Revisedv4dfa962353f8b…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv3ef806c86cdda…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  3. Revisedv2e760bd687a35…

    Direction audit: the problem line described the method, not an outcome; restated as the finding.

  4. Publishedv105b58d6aa255…

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