Format

Send to

Choose Destination
See comment in PubMed Commons below
Genes Dev. 2004 Nov 1;18(21):2614-26. Epub 2004 Oct 15.

Alveolar rhabdomyosarcomas in conditional Pax3:Fkhr mice: cooperativity of Ink4a/ARF and Trp53 loss of function.

Author information

  • 1Division of Pediatric Hematology-Oncology and Department of Pediatrics, University of Utah, Salt Lake City, Utah 84112, USA.

Abstract

Alveolar rhabdomyosarcoma is an aggressive childhood muscle cancer for which outcomes are poor when the disease is advanced. Although well-developed mouse models exist for embryonal and pleomorphic rhabdomyosarcomas, neither a spontaneous nor a transgenic mouse model of alveolar rhabdomyosarcoma has yet been reported. We report the first mouse model of alveolar rhabdomyosarcoma using a conditional Pax3:Fkhr knock-in allele whose activation in late embryogenesis and postnatally is targeted to terminally differentiating Myf6-expressing skeletal muscle. In these mice, alveolar rhabdomyosarcomas occur but at low frequency, and Fkhr haploinsufficiency does not appear to accelerate tumorigenesis. However, Pax3:Fkhr homozygosity with accompanying Ink4a/ARF or Trp53 pathway disruption, by means of conditional Trp53 or Ink4a/ARF loss of function, substantially increases the frequencies of tumor formation. These results of successful tumor generation postnatally from a target pool of differentiating myofibers are in sharp contrast to the birth defects and lack of tumors for mice with prenatal and postnatal satellite cell triggering of Pax3:Fkhr. Furthermore, these murine alveolar rhabdomyosarcomas have an immunohistochemical profile similar to human alveolar rhabdomyosarcoma, suggesting that this conditional mouse model will be relevant to study of the disease and will be useful for preclinical therapeutic testing.

[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 HighWire Icon for PubMed Central
    Loading ...
    Write to the Help Desk