RDF/XMLNTriplesTurtleShow queryShare
SubjectPredicateObject
http://purl.uniprot.org/citations/14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/14504198http://www.w3.org/2000/01/rdf-schema#comment"Genetic polymorphism in HPC2/ELAC2 was recently associated with risk of sporadic prostate cancer. To determine the contribution of two HPC2/ELAC2 missense variants (Ser217Leu and Ala541Thr) to the risk of developing prostate cancer, we conducted a population-based case-control study of middle-aged men (40-64 years). Cases (n=591) were ascertained from the Seattle-Puget Sound Surveillance, Epidemiology, and End Results Cancer Registry and Controls (n=538) from the same general population were identified through random-digit dialing. Subjects were residents of King County, Washington, and were frequency matched on age. Cases (32%) had a slightly higher frequency of the Leu217 variant compared with controls (29%), but there were no differences in the frequency of the Thr541 allele (4%). When considering joint genotypes, white men homozygous for the Leu217 variant on an Ala541/Ala541 background had an increased risk of prostate cancer [odds ratio (OR)=1.84; 95% confidence interval (CI), 1.11-3.06]. Different risk profiles were also observed when cases were stratified by disease aggressiveness. Men with at least one Leu217 allele had an elevated risk (OR=1.34; 95% CI, 1.02-1.76) of less aggressive prostate cancer (localized stage and Gleason score < or = 7), with a stronger association among men with two Leu217 alleles (OR=1.73; 95% CI, 1.08-2.77). The Ala541Thr polymorphism was not associated with risk, and neither variant was associated with more aggressive prostate cancer phenotypes. We estimate that the Ser217Leu genotype may account for approximately 14% of less aggressive prostate cancer cases and 9% of all sporadic cases in the general United States population of white men xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/author"Feng Z."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/author"Ostrander E.A."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/author"Iwasaki L."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/author"Shu J."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/author"Stanford J.L."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/author"Noonan E.A."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/author"Sabacan L.P."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/date"2003"xsd:gYear
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/name"Cancer Epidemiol Biomarkers Prev"xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/pages"876-881"xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/title"Association of HPC2/ELAC2 polymorphisms with risk of prostate cancer in a population-based study."xsd:string
http://purl.uniprot.org/citations/14504198http://purl.uniprot.org/core/volume"12"xsd:string
http://purl.uniprot.org/citations/14504198http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/14504198
http://purl.uniprot.org/citations/14504198http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/14504198
http://purl.uniprot.org/uniprot/#_B3KSU9-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_B3KT00-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_A0A0S2Z5J8-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_A0A0S2Z5M8-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_B4E365-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_B4DT15-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_G5E9D5-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_Q9HAS7-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198
http://purl.uniprot.org/uniprot/#_Q9BQ52-mappedCitation-14504198http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/14504198