Early anterior crossbite correction through posterior bite opening: a 3D superimposition prospective cohort study

Objectives To assess the effectiveness, clinical performance, and potential adverse effects of early anterior crossbite correction through opening of the bite. Subjects and methods The sample consisted of 16 consecutive patients (8.0 ± 0.9, range: 6.2-9.3 years) with dental anterior crossbite in the mixed dentition who were treated through posterior bite opening. Patients were prospectively followed until a minimum of 6 months post-treatment and there were no drop-outs. Results In 14 patients (87.5 per cent), the anterior crossbite was corrected. Results remained stable without any retention regime. Active treatment of the successfully treated cases lasted 2.5 months (range: 0.6-8.9). Crossbite correction of central incisors was achieved by a 2.05 mm (range: 0.97-5.45) forward movement and 9.25° (range: 2.32-14.52°) buccal inclination of the crowns (P < 0.05). The antagonists showed spontaneous adaptation of their position in the opposite direction (P < 0.05). No important adverse effects were recorded. Limitations This was a non-comparative controlled study, on a limited sample. Conclusions Bite opening is a promising, simple, and non-compliance approach for early dental anterior crossbite correction. The technique of 3D superimposition and analysis of digital models used here, allowed precise evaluation of single tooth movement in all three planes of space

D6.9 INTEGRATION OF RESULTS: POLICYCLOUD COMPLETE ENVIRONMENT M36

This deliverable has been released in December 2022, at M36 of the project, and its main objective is to specify the final integration results between the PolicyCLOUD components. This deliverable will follow the methodology of D6.2 and D6.8 that were respectively submitted in M12 (December 2020) and M24 (December 2021) which have two main pillars: Define common practices for integration and validation of the outcomes of the project Detail the cloud environment the project will make use of to demonstrate the results Regarding the former, GitLab will be the base code repository for the project, where the project already owns an organizational account. Over GitLab [1], the trunk-based development branching policy has been applied, as we considered it the most suitable policy given the project characteristics. Also, GitLab’s issue reporting tool has been adopted, as it is fully integrated with GitLab’s features. The test bed to support the demonstrators has been deployed over EGI’s (EGI) infrastructure where flexibility is one of the critical features. This deliverable abstractly incorporates all the changes and implementations that WP2, WP3, WP4 and WP5 had made during the second year of the project. More details about the components and the actual implementation can be found in the related WP deliverables [7] [8] [9]. In detail, the schemas of the data have been finalized so the standard version that we defined initiated the data import to the repository of PolicyCLOUD. Moreover, the infrastructure (IaaS) and the platform deployment (PaaS/ Serverless) have been restructured and reshaped based on the latest needs of the components. EGI deployed the new flavour of PolicyCLOUD to the Openstack Infrastructure and IBM made the proper changes to the Openwhisk middleware for the serverless and other services. The related WP deliverables highlight detailed information and instructions for each component change that in total orchestrate the PolicyCLOUD engine.This deliverable is submitted to the EC, not yet approved