52/100

Moderate evidence

Published recordHealthGeneral

Comparison of the Cox Proportional Hazards Model and Random Survival Forest Algorithm for Predicting Patient-Specific Survival Probabilities in Clinical Trial Data

Truvace record
TRV-2026-1232raw data (JSON)
Version
v2Revised
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
e3ca6dfd5ca5…check it

The Cox proportional hazards model is often used to analyze data from randomized controlled trials (RCTs) with time-to-event outcomes. Random survival forest (RSF) is a machine-learning algorithm known for its high predictive performance. We conduct a comprehensive neutral comparison study to compare the performance of Cox regression and RSF in various simulation scenarios based on two reference datasets from RCTs. The motivation is to identify settings in which one method is preferable over the other when compa…

The gain

In simulated RCT time-to-event data, random survival forest retained predictive performance better when treatment-covariate interactions were present than when they were absent.

The problem

In the same RCT simulations, the standard log-rank splitting rule for random survival forest was outperformed by alternative rules in nonproportional hazards settings, limiting its predictive advantage.

What this doesn’t fix

Findings are based on simulation scenarios derived from only two RCT reference datasets, and conclusions based solely on C index may not generalize to other performance aspects.

Sources

1 on file
  1. Biometrical Journaldoi:10.1002/bimj.70171
    Peer-reviewed2026-10-01

Cite this record

v2

Truvace Impact Record TRV-2026-1232, v2: “Comparison of the Cox Proportional Hazards Model and Random Survival Forest Algorithm for Predicting Patient-Specific Survival Probabilities in Clinical Trial Data.” Truvace, 2026-10-26. /record/TRV-2026-1232 (accessed on the day you copy it). sha256 e3ca6dfd5ca53c80…

Change history

2 versions

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

  1. Revisedv2e3ca6dfd5ca5…

    Direction audit: the gain line stated no AI consequence and was removed; the problem line stated no AI consequence and was removed. Filed as context; not counted as a gain or a problem.

  2. Publishedv1f5df053353ee…

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