z-logo
Premium
Chromosome 5q subtelomeric deletion syndrome
Author(s) -
Rauch Anita,
Dörr HelmuthGünther
Publication year - 2007
Publication title -
american journal of medical genetics part c: seminars in medical genetics
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.419
H-Index - 101
eISSN - 1552-4876
pISSN - 1552-4868
DOI - 10.1002/ajmg.c.30151
Subject(s) - haploinsufficiency , subtelomere , sotos syndrome , microcephaly , hypotonia , biology , genetics , breakpoint , speech delay , gene duplication , phenotype , locus (genetics) , chromosome , gene
The pure 3.5 Mb subtelomeric deletion syndrome is very rare but causes a recognizable phenotype characterized by prenatal lymphedema with increased nuchal translucency, pronounced muscular hypotonia in infancy, borderline intelligence, postnatal short stature with delayed bone age due to growth hormone deficiency, and multiple minor anomalies including mildly bell‐shaped chest, minor congenital heart defects, and a distinct facial gestalt. Terminal deletions including the adjacent ∼2 Mb NSD1 ‐locus show a compound phenotype with overlap to Sotos syndrome. Larger terminal deletions including also chromosomal bands 5q35.1 and 5q35.2 cause a more severe phenotype with normal body length, significant congenital heart defect, microcephaly, profound developmental retardation or early death due to respiratory failure. Heart defects in the latter are explained by haploinsufficiency of the NKX2.5 gene at 5q35.1. The deletion breakpoint of the 3.5 Mb subtelomeric microdeletion maps to a low copy repeat which is identical to the distal copy of two highly similar regions flanking the recurrent interstitial NSD1 microdeletion. As meiotic mispairing between these low copy repeats seem to be much more likely than a terminal aberration, these neighborhood may prevent occurrence of the subtelomeric deletion syndrome, which could explain the rareness of the latter. © 2007 Wiley‐Liss, Inc.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here