TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0754Certified recordPeer-reviewed

Building Machine Learning Models Based on Oxidative Stress Index Score to Predict Survival of Locally Advanced Rectal Cancer Receiving Different Neoadjuvant Therapy Patterns

Background Liver enzyme biomarkers are known to contribute to the onset and progression of colorectal cancer. Objective To develop a novel oxidative stress index score integrating γ-glutamyl transferase and total bilirubin, evaluate its prognostic value in locally advanced rectal cancer patients receiving neoadjuvant therapy, and construct and validate machine learning-based survival prediction models incorporating oxidative stress index score. Design A novel liver enzyme indicator - oxidative stress index score…

Health · G Space — documented gain · certified 2026-08-14 · v1 · article view · machine-readable

Current reading — gain

Random survival forests models incorporating oxidative stress index score improved prediction of disease-free and overall survival for locally advanced rectal cancer patients receiving neoadjuvant therapy, outperforming conventional ypStage and enabling risk stratification.

What this doesn’t fix

Findings are constrained by retrospective single-center design and lack of external multi-center validation, limiting generalizability of the predictive models.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0754, v1: “Building Machine Learning Models Based on Oxidative Stress Index Score to Predict Survival of Locally Advanced Rectal Cancer Receiving Different Neoadjuvant Therapy Patterns.” Truvace, 2026-08-14. /record/TRV-2026-0754 (accessed at citation time). sha256 d3b083f2c7ddbcd7

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1d3b083f2c7dd

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