Format

Send to

Choose Destination
See comment in PubMed Commons below
Curr Opin Otolaryngol Head Neck Surg. 2008 Oct;16(5):441-4. doi: 10.1097/MOO.0b013e32830f4aa3.

KCNQ4 mutations associated with nonsyndromic progressive sensorineural hearing loss.

Author information

  • 1Center for Neuroscience and Department of Otolaryngology-Head and Neck Surgery, University of California Davis, Davis, California 95618, USA. lnie@ucdavis.edu

Abstract

PURPOSE OF REVIEW:

This article provides an update on the current progress in identification of KCNQ4 mutations responsible for DFNA2, a subtype of autosomal dominant nonsyndromic progressive hearing loss.

RECENT FINDINGS:

Hearing loss in pateints with DFNA2 usually start at high frequencies in their 20s and 30s, and then progress to more than 60 dB in less than 10 years, with middle and low frequencies often affected as well. To date, eight missense mutations and two deletions of the KCNQ4 gene have been identified in patients with DFNA2 with various clinical phenotypes. In general, missense mutations are associated with younger-onset and all-frequency hearing loss, whereas deletion mutations are underlying later-onset and pure high-frequency hearing loss. The etiology of DFNA2 remains largely unknown at this point, even though the degeneration of cochlear outer hair cells, caused by dysfunction of KCNQ4 channels, might be one of the underlying mechanisms.

SUMMARY:

During the last decade, significant progress has been made in identifying KCNQ4 mutations in patients with DFNA2. Elucidation of the pathogenic effect of these mutations will help to gain insights into the molecular mechanisms of hearing and hearing loss, which, in turn, will facilitate informative genetic counseling, early diagnosis, and even treatment of hearing loss.

[PubMed - indexed for MEDLINE]
Free PMC Article
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Lippincott Williams & Wilkins Icon for PubMed Central
    Loading ...
    Write to the Help Desk