BSPV4.13: Root Based Aligner Treatment is The ONLY Way To Properly Plan AN Aligner Treatment!

Поделиться
HTML-код
  • Опубликовано: 2 окт 2024
  • Root Based aligner planning eliminates midcourse refinement cases.
    If you are not using Root based aligner planning then you are just guessing and estimating the aligner plan, and that is the main cause for needing to modify and redo the aligner treatment while treating the patient.
    Let me explain Aligner treatment has generally been done based on model scans or intraoral scans only. This provides crown information but it does not provide information regarding the full anatomical structure of the teeth. The full anatomical structure of the teeth is needed in order to properly know how to move the teeth in the software so that it reflects the true biomechanical movement of the teeth.
    When only the crown information is available the software, and the user are guessing, okay lets say estimating as to how the real teeth with move. When the movement widget is applied to the tooth to translate, rotate, tip and torque it is all based on guesses. These guesses cause a discrepancy between how the teeth move in a digital plan vs how teeth actually move in the patient's mouth…resulting in a midcourse refinement.
    In BlueSkyPlan, we fully segment all the relevant anatomical data including the teeth with their actual roots and the jaws. This provides full information as to the true anatomical structure of the teeth…using the true volume of the teeth we improve the widget positioning so that the teeth movement in the software is sound biomechanically, reducing and eliminating cases that require midcourse refinement
    Anything short of complete segmentation of CT teeth to provide complete anatomical data when creating the aligner digital tooth setup is simply a situation where the aligner digital teeth setup and the teeth movements are being created simply based on an guess. Do it yourself in BSP or order via LabPronto
    *Improved widget placement based on CT data exists in version 4.13 of BSP and newer

Комментарии •