TRV-2026-1266Version 2 · Revised

Saved · see the current record

Why this version exists

Copy cleanup: removed remarks about truncated source text.

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-1266
version: 2
kind: revised
reason: Copy cleanup: removed remarks about truncated source text.
timestamp: 2026-11-04T09:00:00.847090Z
status: published
lens: g_space
sector: health
headline: Predictive Value of the Albumin-Bilirubin Score for All-Cause Mortality in Individuals with Stroke: Machine Learning Prediction Models with SHAP-Based Interpretation
dek: Background The albumin-bilirubin (ALBI) score, an objective liver function and prognostic indicator, has shown predictive value in various diseases, but its long-term prognostic significance in stroke survivors remains unclear. Objective To evaluate the ALBI score's predictive value for all-cause mortality (ACM) in individuals with stroke. Methods Data from the National Health and Nutrition Examination Survey (1999-2018) were analyzed. The Boruta algorithm selected key variables associated with ACM. Kaplan-Meier…
gain_title: In 1,838 stroke survivors, machine learning models incorporating the albumin-bilirubin score predicted all-cause mortality and enabled risk stratification for individualized management.
problem_title: (none)
trace_subject: (none)
gain_reading: In 1,838 stroke survivors, machine learning models incorporating the albumin-bilirubin score predicted all-cause mortality and enabled risk stratification for individualized management.
gain_evidence: In stroke survivors, the ALBI score independently predicts ACM and may aid risk stratification and individualized management. | Among 1,838 stroke survivors (median follow-up: 78 months)
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers evaluated the albumin-bilirubin score as a predictor of all-cause mortality in 1,838 stroke survivors from NHANES 1999-2018, with 78 months median follow-up. They selected variables with Boruta, tested associations with Kaplan-Meier and Cox models, and built five machine learning models with 10-fold cross-validation assessed by C-index, Brier score, time-dependent AUC, and calibration, interpreting the best model with SHAP.
limitation: 
tag: Evidence-backed gain
key_points: Study analyzed NHANES 1999-2018 data for 1,838 stroke survivors with median follow-up of 78 months. | Boruta algorithm selected variables including age, sex, cardiovascular disease, lymphocyte count, uric acid, and creatinine alongside ALBI. | Five ML models were built with 10-fold cross-validation and evaluated by C-index, integrated Brier score, time-dependent AUC, and calibration curves. | SHapley Additive exPlanations (SHAP) was used to interpret the best-performing model.
rundown: The analysis used National Health and Nutrition Examination Survey data from 1999-2018 and applied the Boruta algorithm to select predictors including marital status, body mass index, aspartate/alanine aminotransferase, polyunsaturated fatty acids, and basophil percentage.

Associations were examined with Kaplan-Meier curves, Cox regression, and restricted cubic splines to assess nonlinearity between ALBI and mortality risk, with log-rank testing showing survival differences across quartiles.
sources:
- peer_reviewed | Journal of Stroke and Cerebrovascular Diseases | https://doi.org/10.1016/j.jstrokecerebrovasdis.2026.108759 | 2026-10-01
prev: 73435b6d82151db6c59ca5424065ce0fe79e5415c8caf19e5d049782d393fcbf
SHA-256 hash
66c080c9058e2545e50155225b9283ef878109f66ad0005042d0bb228b21452c
Previous version’s hash
73435b6d82151db6c59ca5424065ce0fe79e5415c8caf19e5d049782d393fcbf
Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1266 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.