z-logo
Premium
Oculoauriculofrontonasal syndrome: Case series revealing new bony nasal anomalies in an old syndrome
Author(s) -
Evans Kelly N.,
Gruss Joseph S.,
Khanna Paritosh C.,
Cunningham Michael L.,
Cox Timothy C.,
Hing Anne V.
Publication year - 2013
Publication title -
american journal of medical genetics part a
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.064
H-Index - 112
eISSN - 1552-4833
pISSN - 1552-4825
DOI - 10.1002/ajmg.a.35926
Subject(s) - neural crest , etiology , anatomy , medicine , maxilla , pathology , biology , genetics , embryo
Frontonasal Dysplasia (FND) and Oculo‐auriculo‐vertebral spectrum (OAVS) are two well‐recognized clinical entities. With features of both FND and OAVS, the term oculoauriculofrontonasal syndrome (OAFNS) was coined in 1981. The OAFNS phenotype combines elements of abnormal morphogenesis of the frontonasal and maxillary process (derived from forebrain neural crest) with abnormal development of the first and second branchial arches (derived from hindbrain neural crest). We present a case series of 33 children with OAFNS ascertained from a comprehensive review of the literature and report an additional retrospective series of eight patients displaying features consistent with OAFNS. Notably, in a subset of our cases, we have observed abnormalities in nasal ossification and bony structures of the maxilla that have not previously described in OAFNS and are not seen in either FND or OAVS. We present the phenotype and novel naso‐maxillary findings and explore potential etiologic and developmental pathways for OAFNS. We highlight the differences in phenotypic characteristics of OAFNS compared to OAVS and FND. These observations support the classification of OAFNS as a discrete syndrome. Further phenotypic refinements of OAFNS are needed to understand pathogenesis of this syndrome and the newly described nasal malformation may help identify the etiology. © 2013 Wiley Periodicals, Inc.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here