RDF/XMLNTriplesTurtleShow queryShare
SubjectPredicateObject
http://purl.uniprot.org/citations/19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/19536175http://www.w3.org/2000/01/rdf-schema#comment"Essential hypertension is a major cardiovascular risk factor and a large proportion of this risk is genetic. Identification of genomic regions consistently associated with hypertension has been difficult in association studies to date as this requires large sample sizes.We previously published a large genome-wide linkage scan in Americans of African (AA) and European (EA) descent in the GenNet Network of the Family Blood Pressure Program (FBPP). A highly significant linkage peak was identified on chr1q spanning a region of 100 cM. In this study, we genotyped 1569 SNPs under this linkage peak in 2379 individuals to identify whether common genetic variants were associated with blood pressure (BP) at this locus.Our analysis, using two different family-based association tests, provides suggestive evidence (P< or =2 x 10(-5)) for a collection of single nucleotide polymorphisms (SNPs) associated with BP. In EAs, using diastolic BP as a quantitative phenotype, three variants located in or near the GPA33, CD247, and F5 genes, emerge as our top hits; for systolic BP, variants in GPA33, CD247, and REN are our best findings. No variant in AAs came close to suggestive evidence after multiple-test corrections (P> or =8 x 10(-5)). In summary, we show that systematic follow-up of a linkage signal can help discover candidate variants for essential hypertension that require a follow-up in yet larger samples. The failure to identify common variants is either because of low statistical power or the existence of rare coding variants in specific families or both, which require additional studies to clarify."xsd:string
http://purl.uniprot.org/citations/19536175http://purl.org/dc/terms/identifier"doi:10.1038/ejhg.2009.94"xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/author"Chakravarti A."xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/author"Weder A."xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/author"Cooper R.S."xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/author"Ehret G.B."xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/author"O'Connor A.A."xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/date"2009"xsd:gYear
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/name"Eur J Hum Genet"xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/pages"1650-1657"xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/title"Follow-up of a major linkage peak on chromosome 1 reveals suggestive QTLs associated with essential hypertension: GenNet study."xsd:string
http://purl.uniprot.org/citations/19536175http://purl.uniprot.org/core/volume"17"xsd:string
http://purl.uniprot.org/citations/19536175http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/19536175
http://purl.uniprot.org/citations/19536175http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/19536175
http://purl.uniprot.org/uniprot/#_A0A087WZ88-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A024R8Y5-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A024R910-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A024R928-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A024R971-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A140VJP0-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A0H3WB26-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A0H3WB59-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A0H3WCW6-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175
http://purl.uniprot.org/uniprot/#_A0A0H3WCX1-mappedCitation-19536175http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/19536175