68/100

Moderate evidence

GainPublished recordHealthGood Space

DIAGNOSTIC ACCURACY OF ARTIFICIAL INTELLIGENCEBASED SYSTEMS FOR DETECTION OF DENTAL CARIES COMPARED WITH CONVENTIONAL DIAGNOSTIC METHODS

Truvace record
TRV-2026-3047raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
5bb1e250c12d…check it

Objective: To evaluate the diagnostic accuracy of an artificial intelligence (AI)-based dental caries detection system compared with conventional clinical and radiographic diagnostic methods in patients presenting for routine dental examination. Methods: This comparative diagnostic accuracy study included 210 patients undergoing dental examination. Each participant received a standardized clinical examination followed by digital intraoral bitewing radiography when indicated. Dental caries were assessed using con…

The gain

In a 210-patient study at a Pakistani dental college, an AI caries detector had 91.5% sensitivity, versus 82.2% for dentists' clinical examination and 87.3% for their radiograph reading.

What this doesn’t fix

The authors list a modest sample size from one college and no assessment of long-term treatment outcomes, and say the AI should complement dentists until validated in larger multicentre studies.

Sources

1 on file
  1. Peer-reviewed2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3047, v1: “DIAGNOSTIC ACCURACY OF ARTIFICIAL INTELLIGENCEBASED SYSTEMS FOR DETECTION OF DENTAL CARIES COMPARED WITH CONVENTIONAL DIAGNOSTIC METHODS.” Truvace, 2026-11-19. /record/TRV-2026-3047 (accessed on the day you copy it). sha256 5bb1e250c12dd4f1…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv15bb1e250c12d…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3047 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.