87/100

High evidence

ProblemPublished recordHealthProblem Space

Cardiovascular Classification in Middle-Aged and Elderly CKD Patients: A Machine Learning Approach in China and the United States

Truvace record
TRV-2026-1220raw data (JSON)
Version
v7Sources changed
First published
Evidence type
Observational study
Sources
5 sourcesPeer-reviewed
sha256
3f96530d5fd8…check it

Background Cardiovascular disease (CVD) drives mortality in chronic kidney disease (CKD) patients. Conventional risk tools underperform in CKD, and few machine learning (ML) models undergo cross-national validation. We developed interpretable ML models for classifying CVD amongst Chinese and US middle-aged and elderly CKD patients. Methods We conducted retrospective cross-sectional analyses using two nationally representative cohorts: NHANES (2011-2016, US) and CHARLS (Wave 1 and 3, China). A total of 1057 CKD p…

The problem

In a study of kidney patients in the US and China, models built to classify heart disease performed worse when tested on the other country's patients, and key risk factors differed: age in the US, hypertension in China.

What this doesn’t fix

Models showed reduced discriminative performance when deployed across countries, indicating limited cross-population transportability and supporting need for population-calibrated models.

Sources

5 on file
  1. Peer-reviewed2026-09-27
  2. Scientific Reportsdoi:10.1038/s41598-025-18443-7
    Peer-reviewed2025-09-25
  3. Annals of Internal Medicinedoi:10.7326/annals-24-01926
    Peer-reviewed2025-03-10
  4. Frontiers in Digital Healthdoi:10.3389/fdgth.2023.1193467
    Peer-reviewed2023-07-28
  5. Peer-reviewed2021-03-11

Cite this record

v7

Truvace Impact Record TRV-2026-1220, v7: “Cardiovascular Classification in Middle-Aged and Elderly CKD Patients: A Machine Learning Approach in China and the United States.” Truvace, 2026-11-09. /record/TRV-2026-1220 (accessed on the day you copy it). sha256 3f96530d5fd81782…

Change history

7 versions

Every change made to this record since it was first published, and why.

  1. Sources changedv73f96530d5fd8…

    Source set updated

  2. Sources changedv60e29994c2f42…

    Source set updated

  3. Sources changedv553e0708bcbe3…

    Source set updated

  4. Sources changedv499afd9e1ccf2…

    Source set updated

  5. Revisedv31273c733c7b7…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  6. Revisedv217ffa4c5a518…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes; refiled trace to p_space (gain activity_only, problem outcome).

  7. Publishedv1c3b3351e1f37…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

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