A Multi-omics Study of Circulating Phospholipid Markers of Blood Pressure
Bibliographic record
Abstract
Abstract Background High-throughput techniques allow us to measure a wide-range of phospholipids which can provide insight into the mechanisms of hypertension. We aimed to conduct an in depth multi-omics study of various phospholipids with systolic blood pressure (SBP) and diastolic blood pressure (DBP).Methods The associations of blood pressure and 151 plasma phospholipids measured by electrospray ionization tandem mass spectrometry were performed by linear regression in five European cohorts (n = 2,786 in discovery and n = 1,185 in replication). We further explored the blood pressure-related phospholipids in Erasmus Rucphen Family (ERF) study by associating them with multiple cardiometabolic traits (linear regression) and predicting incident hypertension (Cox regression). Mendelian Randomization (MR) and phenome-wide association study (pheWAS) were also explored to further investigate these association results.Results We identified six phosphatidylethanolamines (PE 38:3, PE 38:4, PE 38:6, PE 40:4, PE 40:5 and PE 40:6) and two phosphatidylcholines (PC 32:1 and PC 40:5) which together predicted incident hypertension with an area under the curve (AUC) of 0.61. The identified eight phospholipids are strongly associated with triglycerides, obesity related traits (e.g. waist, waist hip ratio, total fat percentage, body mass index, lipid-lowering medication, and leptin), diabetes related traits (e.g. glucose, insulin resistance and insulin) and prevalent type 2 diabetes. The genetic determinants of these phospholipids also associated with many lipoproteins, heart rate, pulse rate and blood cell counts. No significant association was identified by bi-directional MR approach.Conclusion We identified eight blood pressure-related circulating phospholipids that have a predictive value for incident hypertension. Our cross-omics analyses show that phospholipid metabolites in the circulation may yield insight into blood pressure regulation and raise a number of testable hypothesis for future research.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".