TRV-2026-2138Version 1 · Certified

Written 2026-10-22 01:09:22 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2138
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-22T01:09:22.979960Z
status: published
lens: g_space
sector: health
headline: Development and External Validation of a Machine Learning-Derived Risk Stratification Score for Metastatic Castration-Resistant Prostate Cancer
dek: Purpose Metastatic castration-resistant prostate cancer (mCRPC) shows marked clinical heterogeneity and poor long-term survival, highlighting the need for simple and reliable risk stratification tools beyond the limited usability of existing complex prognostic models. In this study, we developed and validated PROGRESS (Prostate Cancer Global Risk Evaluation and Stratification Score), a simplified prognostic score derived through machine learning‑guided feature selection distilled into a simple laboratory-based t…
gain_title: A machine learning-guided process produced PROGRESS, a simple score built from PSA, ALP and AST that separated mCRPC patients into risk groups and held up in two independent data sets.
problem_title: (none)
trace_subject: (none)
gain_reading: A machine learning-guided process produced PROGRESS, a simple score built from PSA, ALP and AST that separated mCRPC patients into risk groups and held up in two independent data sets.
gain_evidence: Its consistent performance across independent data sets supports clinical utility
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers trained a model on baseline data from 2,035 patients with metastatic castration-resistant prostate cancer. They used unsupervised machine learning to find subgroups with different survival, then reduced the findings to a score called PROGRESS.

The score matters because it relies on cheap, routine blood tests rather than complex prognostic models, which could make risk assessment easier in practice. The authors say it still needs prospective real-world validation before its usefulness is established.
limitation: The authors state that prospective real-world validation is still needed, so clinical utility has not yet been demonstrated outside the retrospective data sets.
tag: Evidence-backed gain
key_points: The training set contained 2,035 patients with mCRPC, and external validation used two independent data sets totaling 1,239 patients. | Unsupervised modeling identified two risk subpopulations with significantly different overall survival, with a median of 27.4 versus 17.7 months in one comparison. | PROGRESS is composed of three independent predictors: PSA, ALP and AST. | The authors suggest uses in individual risk stratification, trial enrichment and early decision making.
rundown: The method embedded baseline patient data into synthetic representations, reduced them with UMAP, and clustered them with DBSCAN to discover subpopulations related to outcome. Feature contribution analysis then informed a multivariable model.

Performance was assessed with Kaplan-Meier and Cox regression for overall survival, and with ROC-AUC, AUC(t) and Harrell C-index for discrimination. The validation data sets covered different therapeutic settings.

The authors frame the tool as an alternative to existing prognostic models whose complexity limits their usability in mCRPC, a disease with marked clinical heterogeneity and poor long-term survival.
sources:
- peer_reviewed | JCO Clinical Cancer Informatics | https://doi.org/10.1200/cci-26-00054 | 2026-10-20
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
b1a71fa9dcb16de34b390774836f3348ad5110e2f1426d4d30d8bf59c2ea4f42
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2138 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.