z-logo
open-access-imgOpen Access
Lack of association between the cyclooxygenase 2 -765G>C polymorphism and prostate cancer risk: a meta-analysis
Author(s) -
YuQi Feng,
Yu Li,
Xiao Wd,
Wang Gx,
Li Yo
Publication year - 2015
Publication title -
genetics and molecular research
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.356
H-Index - 48
ISSN - 1676-5680
DOI - 10.4238/2015.october.28.1
Subject(s) - meta analysis , odds ratio , confidence interval , cochrane library , cyclooxygenase , medicine , prostate cancer , genetic model , publication bias , bioinformatics , oncology , gene , biology , cancer , genetics , enzyme , biochemistry
The aim of this study was to investigate the association between the cyclooxygenase 2 (COX2) -765G>C (rs20417) polymorphism and prostate cancer (PC) risk using meta-analysis. A systematic literature search was performed using the PubMed, Embase, Cochrane Library, and Google Scholar databases by using the terms "cyclooxygenase-2/COX-2/PTGs2", "polymorphism" or "variation", and "prostate" and "cancer" or "carcinoma" to identify relevant articles up to June 14, 2014. Crude odds ratios (ORs) with 95% confidence intervals (CIs) were assessed for PC risk associated with COX2 -765G>C polymorphism using fixed- and random-effect models. We identified a total of nine publications, including 5952 cases and 5078 controls, to investigate the effect of COX2 -765G>C on PC risk, and found no significant association in any genetic model tested (CC vs GG: OR = 0.993, 95%CI = 0.923-1.068; GC+CC vs GG: OR = 1.041, 95%CI = 0.931-1.103; CC vs GC+GG: OR = 0.858, 95%CI = 0.689-1.067; CC vs GG: OR = 0.871, 95%CI = 0.689-1.086; GC vs GG: OR = 1.032, 95%CI = 0.945-1.127). Power analysis and tests for publication bias ensured the reliability of our results. This meta-analysis suggested that the functional COX2 -765G>C polymorphism, located in the COX2 gene promoter, is unlikely to be associated with PC risk. However, additional larger, well-designed studies are still required to reach a conclusive result on this issue.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here