TRV-2026-1817Certified recordPeer-reviewed

A machine learning-derived aging index for risk stratification and mortality prediction in cardiovascular-kidney-metabolic syndrome: A retrospective cohort study

Background The cardiovascular‑kidney‑metabolic (CKM) syndrome shows substantial heterogeneity in progression, yet existing biological age indices are not tailored to CKM pathways. We developed an aging index (CKMAI) using machine learning and evaluated its predictive performance for mortality and high‑risk CKM status. Methods and findings We conducted a retrospective cohort study of 6,896 adults from the National Health and Nutrition Examination Survey (NHANES) 2005-2018, weighted for the US adult population. A…

Health · Good Space — documented gain · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

A machine-learning-derived CKM-specific aging index predicted all-cause and cardiovascular mortality and high-risk CKM status better than PhenoAge, KDM and the cardiometabolic index in a weighted US adult cohort.

What this doesn’t fix

The authors acknowledge a lack of validation in geographically independent cohorts with complete mortality follow-up; external validation was only preliminary, in a hospital-based Chinese cohort of 261 people.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1817, v1: “A machine learning-derived aging index for risk stratification and mortality prediction in cardiovascular-kidney-metabolic syndrome: A retrospective cohort study.” Truvace, 2026-10-18. /record/TRV-2026-1817 (accessed at citation time). sha256 cb21f280124b01c6…

Calibration history

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

  1. Certifiedv1cb21f280124b…

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