TRV-2026-1132Certified recordPeer-reviewed

Development and validation of a machine learning clinicogenomic model to improve prognostic stratification in ER-positive/HER2-negative early breast cancer

Background Several gene expression signatures (GESs) are used for risk stratification in estrogen receptor-positive/human epidermal growth factor receptor 2-negative (ER-positive/HER2-negative) early breast cancer. Recent integrative approaches combine tumour proliferation, estrogen receptor signalling, immune activity, and clinicopathologic features, yielding gains in prognostic accuracy. We therefore developed a machine-learning-based clinicogenomic prognostic model integrating a research-grade implementation…

Health · Good Space — documented gain · certified 2026-09-18 · v2 · article view · machine-readable

Current reading — gain

In three external retrospective datasets, an AI model combining gene scores and clinical features identified low-risk groups 33.8% to 111.8% larger than the standalone 21-gene score while keeping similar or higher survival estimates.

What this doesn’t fix

Findings are based on retrospective analysis of microarray and RNA-sequencing data using a research-grade implementation of the 21-gene recurrence score, not prospective clinical deployment

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1132, v2: “Development and validation of a machine learning clinicogenomic model to improve prognostic stratification in ER-positive/HER2-negative early breast cancer.” Truvace, 2026-11-04. /record/TRV-2026-1132 (accessed at citation time). sha256 0ce1c069443a8360…

Calibration history

Every change to this record since certification, in the open.

  1. Revisedv20ce1c069443a…

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

  2. Certifiedv1f6733a1526cc…

    Certified into the record

Verify this record
How to verify without trusting this page

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