Show Summary Details
Page of

MSX1, Hypodontia, Orofacial Clefting, and the Witkop Syndrome 

MSX1, Hypodontia, Orofacial Clefting, and the Witkop Syndrome
Chapter:
MSX1, Hypodontia, Orofacial Clefting, and the Witkop Syndrome
Author(s):

Marie-José H. Van Den Boogaard

and Hans-Kristian Ploos Van Amstel

DOI:
10.1093/med/9780199934522.003.0096
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: 04 March 2021

MSX1, a homeobox protein, is crucial for facial and tooth development. MSX1 mutations are reported in patients with selective tooth agenesis (OMIM 106600), patients with Witkop syndrome (tooth–and nail syndrome, OMIM 189500) as well as in nonsyndromic orofacial clefting (OMIM 608874). MSX1 mutations often lead to a large number of congenital missing teeth in which the maxillary and mandibular second premolars, the maxillary first premolar and the third molars are most frequently absent. Significant shape differences of the teeth were reported in a family with a MSX1 mutation associated with different types of clefting in combination with tooth agenesis; the incisors were found to have a more square appearance. Several association studies in different populations and the identification of several MSX1 mutation in patients with isolated orofacial clefting support the role of MSX1 in the etiology of non-syndromic clefting.

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.