TRV-2026-1163Version 2 · Revised

Saved · see the current record

Why this version exists

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

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-1163
version: 2
kind: revised
reason: Direction audit: the problem line described the method, not an outcome; restated as the finding.
timestamp: 2026-10-26T06:38:40.820160Z
status: published
lens: p_space
sector: health
headline: An application of random forest regression for predicting healthcare costs using administrative databases
dek: 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…
gain_title: (none)
problem_title: Random forest cost predictions performed poorly at the individual level, systematically underestimating high-cost users.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: Random forest cost predictions performed poorly at the individual level, systematically underestimating high-cost users.
problem_evidence: (none)
quick_read: 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.

We traced 5-year healthcare resource utilization to predict individual's healthcare costs in the following year using random forest regression algorithms. Results At the individual-level, algorithms had a poor performance, systematically underestimating high-cost users.
limitation: 
tag: Evidence-backed problem
key_points: 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).
rundown: 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 in the following year using random forest regression algorithms.
sources:
- peer_reviewed | Expert Review of Pharmacoeconomics & Outcomes Research | https://doi.org/10.1080/14737167.2026.2738028 | 2026-09-21
prev: 05b58d6aa25520cb36a67ae9619caacdf5930e00f7ea82436aeca94e883c781f
SHA-256 hash
e760bd687a3545eab0e916209b553b303e01f621ab0546f629be66aaf683f2ab
Previous version’s hash
05b58d6aa25520cb36a67ae9619caacdf5930e00f7ea82436aeca94e883c781f
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.