Format

Send to:

Choose Destination
See comment in PubMed Commons below
Biochem Biophys Res Commun. 2004 Dec 24;325(4):1312-7.

Identification and functional analysis of consensus androgen response elements in human prostate cancer cells.

Author information

  • 1Division of Gene Regulation and Signal Transduction, Research Center for Genomic Medicine, Saitama Medical School, 1397-1 Yamane, Hidaka-shi, Saitama 350-1241, Japan.

Abstract

Androgen receptor (AR) recognizes and binds to 15-bp palindromic androgen response element (ARE) sequences with high affinity in vitro, which consist of two hexameric half-sites arranged as inverted repeats with a 3-bp spacer. Although a few near-consensus ARE sequences have been actually identified in the transcriptional regulatory regions of androgen-responsive genes, it has been unclear whether the exact consensus sequences function as bona fide AREs in vivo. A genome-wide in silico screening of palindromic AREs identified 563 exact consensus sequences in the human genome. The distribution of perfect palindromic AREs among the chromosomes is basically consistent with the length of chromosomes. Using human prostate cancer cell line LNCaP treated with a synthetic androgen R1881 as a model, in vivo AR binding abilities of 21 consensus AREs were analyzed by chromatin immunoprecipitation. Of 21 genomic fragments containing perfect AREs in chromosome X, 8 fragments recruited more ARs (>4-fold enrichment) even compared with the proximal ARE region of prostate-specific antigen. A couple of proximal genes or putative transcripts in the vicinity of the perfect AREs were found to be androgen-responsive analyzed by quantitative RT-PCR. Our results suggest that some of perfect palindromic AREs could function as in vivo AR binding sites in the human genome and regulate gene transcription.

PMID:
15555570
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Elsevier Science
    Loading ...
    Write to the Help Desk