Show Summary Details
Page of

TBX22, X-linked Cleft Palate, and Ankyloglossia 

TBX22, X-linked Cleft Palate, and Ankyloglossia
Chapter:
TBX22, X-linked Cleft Palate, and Ankyloglossia
Author(s):

Erwin Pauws

and Philip Stanier

DOI:
10.1093/med/9780199934522.003.0122
Page of

PRINTED FROM OXFORD MEDICINE ONLINE (www.oxfordmedicine.com). © Oxford University Press, 2021. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Medicine Online for personal use (for details see Privacy Policy and Legal Notice).

date: 28 February 2021

Orofacial clefts affecting the lip and/or palate are among the most common birth defects worldwide (1/700 live births) and are understood to result from a wide variety of genetic and environmental causes. There are several commonly applied distinctions that classify orofacial clefts, namely cleft lip with or without cleft palate (CL/P) and cleft palate alone (CP), which are both further subdivided as syndromic or non-syndromic. X-linked cleft palate and ankyloglossia (CPX; MIM303400) was originally recognized in several large families of native North American and Icelandic origin (Lowry, 1970; Bjornsson et al., 1989) and was studied as a clear, although potentially rare Mendelian trait. Subsequently, mutations in the gene encoding the T-box transcription factor TBX22 were found to underlie CPX (Braybrook et al, 2001). Further studies indicate that approximately 4-8% of cleft palate patients harbour TBX22 mutations, where ankyloglossia is an occasional but not obligatory additional feature.

Access to the complete content on Oxford Medicine Online requires a subscription or purchase. Public users are able to search the site and view the abstracts for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.