TRV-2026-1885Certified recordPeer-reviewed

Accuracy of transfer learning in predicting peri-implantitis onset from intraoral radiograph: A multi-center longitudinal retrospective study

Abstract Background The growing application of artificial intelligence in dentistry has opened new opportunities for predicting peri-implantitis (PI) using convolutional neural networks (CNNs). Transfer learning, where knowledge from a model pre-trained on a large dataset is adapted to a new, domain-specific task, may enhance performance, particularly when medical datasets are limited. This study evaluated the ability of several pre-trained CNN architectures applied to baseline 2D intraoral radiographs to predic…

Health · The Trace — both readings · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — gain

Non-hybrid feature extraction on pre-trained CNNs reached AUCs of 0.74 to 0.83 in predicting later peri-implantitis from a routine baseline radiograph, suggesting a possible aid to early risk stratification.

Current reading — problem

Fine-tuning strategies performed modestly or poorly on the same task, with AUCs generally between 0.42 and 0.69, and the authors say larger prospective studies are needed before clinical adoption.

What this doesn’t fix

The dataset is small, with 195 implants in 108 patients, the design is retrospective, and the authors state that larger prospective studies are needed before clinical adoption.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1885, v1: “Accuracy of transfer learning in predicting peri-implantitis onset from intraoral radiograph: A multi-center longitudinal retrospective study.” Truvace, 2026-10-19. /record/TRV-2026-1885 (accessed at citation time). sha256 d589e367d256dc2c…

Calibration history

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

  1. Certifiedv1d589e367d256…

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