Moderate evidence
Published recordHealthGood Space
More
Machine learning-based discrimination of metabolic dysfunction-associated steatotic liver disease: implications of tryptophan metabolites as potential biomarkers
- Truvace record
- TRV-2026-1223raw data (JSON)
- Version
- v2Revised
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 0f2689a831f7…check it
Objectives Early screening of individuals at high risk of metabolic dysfunction-associated steatotic liver disease (MASLD) facilitates timely intervention and may reduce the risk of progression to cirrhosis. This study aimed to develop a reliable and clinically practical model for MASLD discrimination. Methods A total of 179 individuals were recruited, including 80 healthy controls and 99 MASLD patients. Non-targeted and targeted metabolomics were performed to identify and validate candidate biomarkers associate…
The gain
In a 179-person study (80 healthy, 99 with fatty liver disease), a model combining kynurenine, neopterin and five routine lab tests separated patients from healthy people with AUC 0.926-0.972.
What this doesn’t fix
Model developed in a small single cohort of 179 individuals and authors note need for further validation and mechanistic exploration before clinical use.
Sources
1 on file- Clinica Chimica Actadoi:10.1016/j.cca.2026.122854
Cite this record
v2Truvace Impact Record TRV-2026-1223, v2: “Machine learning-based discrimination of metabolic dysfunction-associated steatotic liver disease: implications of tryptophan metabolites as potential biomarkers.” Truvace, 2026-11-04. /record/TRV-2026-1223 (accessed on the day you copy it). sha256 0f2689a831f79f81…
Change history
2 versionsEvery change made to this record since it was first published, and why.
Editorial pass: sharper headline; gain/problem restated as concrete outcomes.
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-1223 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