Moderate evidence
Published recordHealthGood Space
More
Integrative Single-Cell Transcriptomics, Multi-Omics Analyses, and Computational Pharmacology Reveal Macrophage Heterogeneity and the Putative THBS1-CD36 Axis in Coronary Atherosclerosis
- Truvace record
- TRV-2026-1245raw data (JSON)
- Version
- v3Revised
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- da1f2e591b02…check it
Coronary atherosclerosis (CA) is characterized by profound macrophage heterogeneity that drives plaque progression and vulnerability, yet the precise subpopulations and their niche-specific functions remain incompletely defined. Here, we constructed a single-cell transcriptomic atlas of human CA using dataset GSE131778 and identified six distinct macrophage subpopulations. Among these, the THBS1+ macrophage subset emerged as a terminally differentiated, hypoxia-adaptive population with elevated TGF-β signaling a…
The gain
Machine-learning models built on a macrophage gene signature separated acute coronary syndrome from stable disease and ruptured from stable plaques, reaching AUC 0.9333 in an independent cohort, in computer analysis only.
What this doesn’t fix
Findings remain computational predictions requiring further experimental validation, with THBS1-CD36 interaction and SMS121-CD36 binding presented as candidates for future investigation.
Sources
1 on file- Chemical Biology & Drug Designdoi:10.1111/cbdd.70399
Cite this record
v3Truvace Impact Record TRV-2026-1245, v3: “Integrative Single-Cell Transcriptomics, Multi-Omics Analyses, and Computational Pharmacology Reveal Macrophage Heterogeneity and the Putative THBS1-CD36 Axis in Coronary Atherosclerosis.” Truvace, 2026-11-05. /record/TRV-2026-1245 (accessed on the day you copy it). sha256 da1f2e591b0244d0…
Change history
3 versionsEvery change made to this record since it was first published, and why.
Voice pass: plainer wording and study attribution; no facts or figures changed.
Editorial pass: sharper headline; gain/problem restated as concrete outcomes.
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-1245 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