Whole-exome sequencing of over 4,100 men of African ancestry and prostate cancer risk.

HUMAN MOLECULAR GENETICS(2016)

Cited 24|Views30
No score
Abstract
Prostate cancer is the most common non-skin cancer in males, with a similar to 1.5-2-fold higher incidence in African American men when compared with whites. Epidemiologic evidence supports a large heritable contribution to prostate cancer, with over 100 susceptibility loci identified to date that can explain similar to 33% of the familial risk. To explore the contribution of both rare and common variation in coding regions to prostate cancer risk, we sequenced the exomes of 2165 prostate cancer cases and 2034 controls of African ancestry at a mean coverage of 10.1x. We identified 395 220 coding variants down to 0.05% frequency [57% non-synonymous (NS), 42% synonymous and 1% gain or loss of stop codon or splice site variant] in 16 751 genes with the strongest associations observed in SPARCL1 on 4q22.1 (rs13051, Ala49Asp, OR= 0.78, P = 1.8x10(-6)) and PTPRR on 12q15 (rs73341069, Val239Ile, OR= 1.62, P = 2.5x10(-5)). In gene-level testing, the two most significant genes were C1orf100 (P = 2.2x10(-4)) and GORAB (P = 2.3x10(-4)). We did not observe exome-wide significant associations (after correcting for multiple hypothesis testing) in single variant or gene-level testing in the overall case-control or case-case analyses of disease aggressiveness. In this first whole-exome sequencing study of prostate cancer, our findings do not provide strong support for the hypothesis that NS coding variants down to 0.5-1.0% frequency have large effects on prostate cancer risk in men of African ancestry. Higher-coverage sequencing efforts in larger samples will be needed to study rarer variants with smaller effect sizes associated with prostate cancer risk.
More
Translated text
Key words
prostate cancer risk,prostate cancer,whole-exome whole-exome,african ancestry
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined