Journal article
Comparative analysis of the Mexico City Prospective Study and the UK Biobank identifies ancestry-specific effects on clonal hematopoiesis
- Abstract:
- The impact of genetic ancestry on the development of clonal hematopoiesis (CH) remains largely unexplored. Here, we compared CH in 136,401 participants from the Mexico City Prospective Study (MCPS) to 416,118 individuals from the UK Biobank (UKB) and observed CH to be significantly less common in MCPS compared to UKB (adjusted odds ratio = 0.59, 95% confidence interval (CI) = [0.57, 0.61], P = 7.31 × 10−185). Among MCPS participants, CH frequency was positively correlated with the percentage of European ancestry (adjusted beta = 0.84, 95% CI = [0.66, 1.03], P = 7.35 × 10−19). Genome-wide and exome-wide association analyses in MCPS identified ancestry-specific variants in the TCL1B locus with opposing effects on DNMT3A-CH versus non-DNMT3A-CH. Meta-analysis of MCPS and UKB identified five novel loci associated with CH, including polymorphisms at PARP11/CCND2, MEIS1 and MYCN. Our CH study, the largest in a non-European population to date, demonstrates the power of cross-ancestry comparisons to derive novel insights into CH pathogenesis.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Other, pdf, 142.1KB, Terms of use)
-
(Preview, Version of record, pdf, 5.2MB, Terms of use)
-
(Preview, Other, pdf, 3.1MB, Terms of use)
-
(Preview, Other, pdf, 10.7MB, Terms of use)
-
- Publisher copy:
- 10.1038/s41588-025-02085-6
Authors
- Publisher:
- Nature Research
- Journal:
- Nature Genetics More from this journal
- Volume:
- 57
- Issue:
- 3
- Pages:
- 572-582
- Publication date:
- 2025-02-13
- Acceptance date:
- 2025-01-09
- DOI:
- EISSN:
-
1546-1718
- ISSN:
-
1061-4036
- Language:
-
English
- Source identifiers:
-
2773683
- Deposit date:
-
2025-03-14
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
If you are the owner of this record, you can report an update to it here: Report update to this record