Display Settings:

Format

Send to:

Choose Destination
Am J Orthod Dentofacial Orthop. 2009 Sep;136(3):367-74. doi: 10.1016/j.ajodo.2008.08.023.

Maxillary expansion in customized finite element method models.

Author information

  • 1Resident, Section of Orthodontics, School of Dentistry, University of California at Los Angeles, Los Angeles, USA.

Abstract

INTRODUCTION:

The aims of this study were to develop a method for constructing a 3-dimensional finite-element model (FEM) of the maxilla and to evaluate the effects of transverse expansion on the status of various midpalatal sutures.

METHODS:

A 3-dimensional FEM of the craniofacial complex was developed by using computed-tomography images and Bionix modeling software (version 3.0, CANTIBio, Suwon, Korea). To evaluate the differences between transverse expansion forces in the solid model (maxilla without a midpalatal suture), the fused model (maxilla with suture elements), and the patent model (maxilla without suture elements), transverse expansion forces of 100 g were applied bilaterally to the maxillary first premolars and the first molars.

RESULTS:

The fused model expressed a stress pattern similar to that of the solid model, except for the decreased first principal stress concentration in the incisive foramen area. The patent model, however, had a unique stress pattern, with the stress translated superiorly to the nasal area. The anterior nasal spine and the central incisors moved downward and backward in both solid and fused models but moved primarily downward with a slight backward movement of the anterior nasal spine in the patent model.

CONCLUSIONS:

Clinical observations of maxillary expansion can be explained by different suture statuses. This efficient and customized FEM model can be used to predict craniofacial responses to biomechanics in patients.

PMID:
19732671
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Elsevier Science
    Loading ...
    Write to the Help Desk