Moderate evidence
Published recordHealthGeneral
More
Predictive Value of the Albumin-Bilirubin Score for All-Cause Mortality in Individuals with Stroke: Machine Learning Prediction Models with SHAP-Based Interpretation
- Truvace record
- TRV-2026-1266raw data (JSON)
- Version
- v3Revised
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- c2a325a2aa7e…check it
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…
The gain
In 1,838 stroke survivors, machine learning models incorporating the albumin-bilirubin score predicted all-cause mortality and enabled risk stratification for individualized management.
Sources
1 on file- Journal of Stroke and Cerebrovascular Diseasesdoi:10.1016/j.jstrokecerebrovasdis.2026.108759
Cite this record
v3Truvace Impact Record TRV-2026-1266, v3: “Predictive Value of the Albumin-Bilirubin Score for All-Cause Mortality in Individuals with Stroke: Machine Learning Prediction Models with SHAP-Based Interpretation.” Truvace, 2026-11-04. /record/TRV-2026-1266 (accessed on the day you copy it). sha256 c2a325a2aa7e7783…
Change history
3 versionsEvery change made to this record since it was first published, and why.
Quality review: filed as context; not counted as a gain or a problem. Peer-reviewed study building machine learning models to predict all-cause mortality in 1,838 stroke survivors, with rep
Copy cleanup: removed remarks about truncated source text.
Certified into the record
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.
ace