TRV-2026-2301Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2301 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-28T18:35:08.589924Z status: published lens: g_space sector: health headline: Predicting cardiovascular disease in peritoneal dialysis patients using glycated proteomics and machine learning: A prospective multicentre study dek: Background: Cardiovascular disease (CVD) is the leading cause of death among peritoneal dialysis (PD) patients, yet PD-specific biomarkers and prediction models remain limited. This study aimed to identify glycated peptide biomarkers associated with CVD in PD patients and develop a prediction model integrating glycated proteomics and clinical indicators using machine learning. Methods: In Phase I, a matched discovery cohort (48 PD patients with CVD and 48 without CVD) was used to identify glycated peptides by li… gain_title: A model combining two glycated peptides with six clinical indicators separated high- and low-risk dialysis patients and scored an AUC of 0.822 in an external cohort, outperforming three published risk models. problem_title: (none) trace_subject: (none) gain_reading: A model combining two glycated peptides with six clinical indicators separated high- and low-risk dialysis patients and scored an AUC of 0.822 in an external cohort, outperforming three published risk models. gain_evidence: The combined model achieved an area under the receiver operating characteristic curve (ROC-AUC) of 0.784 in the training set, 0.781 in the internal testing set, and 0.822 in the external validation cohort | The combined model also achieved higher ROC-AUCs than the published cardiovascular risk models. problem_reading: (none) problem_evidence: (none) quick_read: Researchers built a prediction tool for cardiovascular disease in people receiving peritoneal dialysis, a group in which heart disease is the leading cause of death. The tool combines two glycated peptide biomarkers found by mass spectrometry with six routine clinical measures, using elastic-net logistic regression. The model could allow earlier identification of high-risk dialysis patients and more targeted prevention. Its accuracy is moderate, with AUCs around 0.78 to 0.82, and the study does not show that acting on the predictions improves patient outcomes. limitation: The model's validation was limited to prediction accuracy in cohorts of 240 and 102 patients, and the text does not demonstrate that using it improves outcomes; the authors only say it may facilitate earlier stratification and prevention. tag: Evidence-backed gain key_points: The discovery phase compared 48 dialysis patients with cardiovascular disease against 48 without, and found 257 differentially abundant glycated peptides. | The final model kept two peptides plus phosphate, diabetes, total Kt/V, albumin, cardiac troponin T and glycated albumin. | AUC was 0.784 in training, 0.781 in internal testing and 0.822 in the external validation cohort. | High-risk patients, defined by a training-derived cutoff of 0.373, had higher 1-year cardiovascular disease incidence in both validation cohorts. rundown: The work ran in two phases. Phase I used a matched discovery cohort and liquid chromatography-tandem mass spectrometry to identify glycated peptides, with glmnet used to prioritise four candidate biomarkers. In Phase II, candidate biomarkers were quantified in a prospective internal derivation cohort of 240 patients and a multicentre external validation cohort of 102 patients. Features were selected with an F-test before elastic-net logistic regression was fitted. The authors compared the combined model with three published cardiovascular risk models and reported higher ROC-AUCs for their model. They conclude it may facilitate earlier risk stratification and targeted prevention. sources: - peer_reviewed | Clinical and Translational Medicine | https://doi.org/10.1002/ctm2.70889 | 2026-11-01 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- f21226f168963fe2bb804ec7ff83d4735548e8bbd329dc78c9dcd62d029a4dd3
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2301 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.
ace