Send to:

Choose Destination
See comment in PubMed Commons below
Gene. 2000 Aug 8;253(2):171-8.

Genomic organization and chromosome localization of the newly identified human heparanase gene.

Author information

  • 1Discovery Research, Tsukuba Research Institute, Novartis Pharma K.K., Okubo 8, Ibaraki 300-2611, Tsukuba, Japan.


Heparanase (HPSE), which we have recently isolated, is an endo-beta-D-glucuronidase capable of cleaving heparan sulfate and has been implicated in inflammation and tumor angiogenesis and metastasis. In this report, the genomic organization and chromosome localization of the human heparanase gene is described. Polymerase chain reaction, subcloning and DNA sequencing analysis of a bacterial artificial chromosome (BAC) clone revealed that the 3.7 kb human heparanase cDNA is spread over about 50 kb and contains 14 exons and 13 introns. The heparanase gene is expressed as two mRNA species containing the same open reading frame, HPSE 1a (5 kb) (GenBank Data Library under accession number: AF155510); and HPSE 1b (1.7 kb) (GenBank Data Library under accession number: AF144325), generated by alternative splicing. The HPSE 1a-form contains all 14 exons, whereas in the HPSE 1b-form the first and fourteenth exons (5'- and 3'-untranslated region) have been spliced out. All splice sites conform to the GT-AG rule, except for the splice donor site of intron 13 (which is GA instead of GT), and the splice acceptor of intron 13 (which is GG instead of AG). Fluorescence in situ hybridization and radiation hybrid mapping suggest that the heparanase gene is located on human chromosome 4q22. This report regarding the structure of the human heparanase gene will aid in understanding the genetic contribution of this gene to normal physiology as well as to disease states. A possible involvement of heparanase in neuronal degeneration is discussed.

[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

How to join PubMed Commons

    Supplemental Content

    Full text links

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