TRV-2026-1223Certified recordPeer-reviewed

Machine learning-based discrimination of metabolic dysfunction-associated steatotic liver disease: implications of tryptophan metabolites as potential biomarkers

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…

Health · Good Space — documented gain · certified 2026-09-30 · v1 · article view · machine-readable

Current reading — gain

A Random Forest model combining two tryptophan metabolites (kynurenine and neopterin) with five routine clinical tests discriminated MASLD from healthy controls with high diagnostic performance.

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.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1223, v1: “Machine learning-based discrimination of metabolic dysfunction-associated steatotic liver disease: implications of tryptophan metabolites as potential biomarkers.” Truvace, 2026-09-30. /record/TRV-2026-1223 (accessed at citation time). sha256 06a542c931d650f4…

Calibration history

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

  1. Certifiedv106a542c931d6…

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