TruaceTracing the truth around AIMonday, September 14, 2026
TRV-2026-1083Certified recordPeer-reviewed

Interpretable machine learning-enabled risk stratification for pulmonary arterial hypertension associated with unrepaired congenital heart disease: results from a national prospective registry

Background Standard pulmonary arterial hypertension (PAH) risk models may not fully apply to PAH associated with unrepaired congenital heart disease (PAH-CHD). We aimed to develop and internally validate an interpretable machine learning (ML)-based risk model for adults with unrepaired PAH-CHD, comparing it against the recent European Society of Cardiology (ESC) model. Methods Utilizing a nationwide prospective registry in China, we included adults with unrepaired PAH-CHD. Five survival models were trained and i…

Health · G Space — documented gain · certified 2026-09-14 · v1 · article view · machine-readable

Current reading — gain

Interpretable random survival forest model predicted all-cause mortality in adults with unrepaired PAH-CHD and stratified survival in both Eisenmenger and non-Eisenmenger subgroups where the ESC model did not.

What this doesn’t fix

Model was developed and internally validated only within a Chinese nationwide registry of adults with unrepaired PAH-CHD, without external validation reported.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1083, v1: “Interpretable machine learning-enabled risk stratification for pulmonary arterial hypertension associated with unrepaired congenital heart disease: results from a national prospective registry.” Truvace, 2026-09-14. /record/TRV-2026-1083 (accessed at citation time). sha256 e6d469a8d7b9ba58

Calibration history

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

  1. Certifiedv1e6d469a8d7b9

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