Moderate evidence
Published recordScienceGood Space
More
Machine learning-based proteomics analysis identified 23 protein biomarkers for enhanced risk prediction of myocardial infarction in Chinese and Europeans
- Truvace record
- TRV-2026-3021raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- b542e89057c1…check it
Background Advances in proteomics assays enable measurement of thousands of plasma proteins, which could facilitate machine learning-based approaches to enhance risk prediction of disease. Methods We measured plasma levels of >9500 proteins among 4000 Chinese adults (1937 myocardial infarction [MI] cases and 2026 subcohort), using both Olink Explore (2923 proteins) and SomaScan (6597 proteins) platforms. Protein-based risk prediction models were constructed, using conventional and machine learning approaches, wi…
The gain
In a study of 4,000 Chinese adults, a machine-learning score built from 23 blood proteins raised heart attack risk prediction (C-statistic 0.846 to 0.864) beyond conventional risk factors alone.
What this doesn’t fix
The authors describe only the potential for small panel proteomics assays; no such assay was built or tested, and the UK Biobank validation had just 630 heart attack cases.
Sources
1 on file- GigaSciencedoi:10.1093/gigascience/giag102
Cite this record
v1Truvace Impact Record TRV-2026-3021, v1: “Machine learning-based proteomics analysis identified 23 protein biomarkers for enhanced risk prediction of myocardial infarction in Chinese and Europeans.” Truvace, 2026-11-18. /record/TRV-2026-3021 (accessed on the day you copy it). sha256 b542e89057c11a16…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3021 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.
ace