TruaceTracing the truth around AIMonday, September 14, 2026
TRV-2026-1082Certified recordPeer-reviewed

Augmented and mixed reality as auxiliary tools in dental procedures and their integration with artificial intelligence: a scoping review

Objectives To map and synthesize the scientific evidence regarding the use of Augmented Reality (AR) and Mixed Reality (MR) as auxiliary tools in dental procedures, and to examine the extent to which Artificial Intelligence (AI) has been integrated into these workflows. Data A scoping review was conducted in accordance with the PRISMA-ScR guidelines and the Joanna Briggs Institute (JBI) recommendations. The study selection and data extraction processes were carried out by two independent reviewers, with disagree…

Health · G Space — documented gain · certified 2026-09-14 · v1 · article view · machine-readable

Current reading — gain

In implant dentistry, MR-based dynamic navigation achieved sub-millimetric entry deviation and outperformed freehand technique, with up to 72% angular accuracy improvement for inexperienced operators and more conservative tissue removal in endodontic and prosthetic tasks.

What this doesn’t fix

Findings reflect technical feasibility rather than established clinical effectiveness due to predominance of in vitro and proof-of-concept designs, requiring multicenter randomized trials before adoption.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1082, v1: “Augmented and mixed reality as auxiliary tools in dental procedures and their integration with artificial intelligence: a scoping review.” Truvace, 2026-09-14. /record/TRV-2026-1082 (accessed at citation time). sha256 3b2d8f6287f200f1

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv13b2d8f6287f2

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1082 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.