TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0798Certified recordPeer-reviewed

Validation of artificial intelligence-assisted CBCT analysis for predicting inferior alveolar nerve proximity to impacted mandibular third molars: a diagnostic accuracy study

This study aimed to evaluate the diagnostic accuracy of an artificial intelligence (AI)-assisted cone-beam computed tomography (CBCT) analysis system for predicting the spatial proximity of the inferior alveolar nerve (IAN) to impacted mandibular third molars (M3M), using expert radiologist assessment as the reference standard. A retrospective diagnostic accuracy study was conducted on an internal institutional cohort of 312 patients (mean age 28.21 ± 6.62 years; January 2021-December 2024). A deep learning syst…

Health · G Space — documented gain · certified 2026-08-17 · v1 · article view · machine-readable

Current reading — gain

An AI system using modified U-Net segmentation automatically classified inferior alveolar nerve proximity to impacted mandibular third molars on CBCT with 90.1% accuracy and reduced analysis time from ~189 seconds to ~4.8 seconds compared to expert radiologists.

What this doesn’t fix

Reference standard was radiographic expert assessment rather than intraoperative findings, and authors state prospective multicenter validation with surgical outcomes is needed before clinical deployment.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0798, v1: “Validation of artificial intelligence-assisted CBCT analysis for predicting inferior alveolar nerve proximity to impacted mandibular third molars: a diagnostic accuracy study.” Truvace, 2026-08-17. /record/TRV-2026-0798 (accessed at citation time). sha256 b99b1ee9ffcb25ab

Calibration history

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

  1. Certifiedv1b99b1ee9ffcb

    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-0798 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.