Format

Send to:

Choose Destination
See comment in PubMed Commons below
Brain Dev. 2006 Aug;28(7):440-6. Epub 2006 Mar 22.

Mutational analysis of TSC1 and TSC2 in Korean patients with tuberous sclerosis complex.

Author information

  • 1Department of Pediatrics, Borame Hospital affiliated to Seoul National University Hospital, 395 shindaebang-2-dong, Dongjak-gu, 156-707 Seoul, South Korea. jieunchoi6647@hanmail.net

Abstract

Tuberous sclerosis complex (TSC) is an autosomal dominant disorder characterized by a broad phenotypic spectrum that includes seizures, mental retardation, renal dysfunction and dermatological abnormalities. TSC is caused by mutations affecting either of the tumor-suppressor genes TSC1 and TSC2. At least 495 mutations of TSC1 and TSC2 have been reported. Twenty-two males and 22 females who were diagnosed with TSC at the Seoul National University Children's Hospital between 1982 and 2002 were enrolled in the study. Forty-four patients were from different families and included nine familial cases and 35 sporadic cases. Denaturing high performance liquid chromatography and DNA sequencing analysis of TSC1 and TSC2 revealed 13 types of mutations (30%). One novel mutation of TSC1 and nine novel mutations of TSC2 were identified. The TSC1 mutation and one of the nine TSC2 mutations were missense mutations and seven of the nine TSC2 mutations caused truncation of proteins. One novel single nucleotide substitution was identified at the consensus splicing donor site of exon 39 (c.5,069-1G>A). This mutation is predicted to cause a splicing error. Of the TSC2 mutation loci, the correlation with cardiac rhabdomyoma was more significant when the mutation was in the C-terminal part of tuberin than the N-terminal part. This is the first extensive mutational analysis of TSC1 and TSC2 in Korean TSC patients.

PMID:
16554133
[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