Answers are grounded in this paper and cite their sources.
PURPOSE: To evaluate the accuracy of complete-arch implant scans obtained using non-splinting and non-calibrated implant scan body (ISB) methods captured by an intraoral scanner (IOS) with 2 scanning patterns with and without artificial intelligence (AI)-based tools. MATERIALS AND METHODS: A patient with an edentulous maxillary arch and 4 implants was enrolled. Four groups were established according to scanning technique evaluated: non-splinting with PEEK or titanium ISBs, 2 non-calibrated ISBs methods. For each technique, the maxillary arch was scanned using an IOS, applying both a circumferential and an occlusal-buccal-lingual scanning pattern, with and without the use of the integrated AI-based tool of the selected IOS. A stone cast fabricated through the conventional splinted impression was verified and digitized with a laboratory scanner to serve as reference. Linear and angular discrepancies among the designed bars for reference and experimental scans were analyzed. RESULTS: Non-calibrated techniques demonstrated better linear trueness and better angular trueness and precision than non-splinting methods (p < 0.05). No significant differences were observed between the 2 non-calibrated ISB techniques (p > 0.05). The titanium ISBs of the non-splinting group resulted in better trueness and precision than the PEEK ISBs (p < 0.05). The AI-based tool had a significant effect on the accuracy of Dynamic Abutment non-calibrated ISB system (p < 0.05). No significant differences were found among the evaluated scanning patterns (p > 0.05). CONCLUSIONS: Implant scanning technique and AI-based tool of the IOS selected influenced the accuracy of the complete-arch implant scans; however, the scanning pattern did not affect the accuracy of the scanning process.
No takes yet. Share an insight, caveat, or question.
Tasopoulos et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: