TruaceTracing the truth around AIMonday, August 31, 2026
TRV-2026-0938Certified recordPeer-reviewed

The Role of Artificial Intelligence Models in Predicting Post-Prosthetic Facial Esthetics in Edentulous Patients: Clinical and Anthropometric Comparative Study

Objectives Artificial intelligence (AI) is increasingly used in esthetic dentistry; however, its accuracy in predicting post-prosthetic facial outcomes in edentulous patients remains unclear. This study aimed to evaluate the ability of AI models to simulate post-denture facial esthetics compared with actual clinical outcomes. Materials and methods A prospective within-subject observational study was conducted on 14 completely edentulous patients receiving new complete dentures. Standardized facial photographs we…

Health · The Trace — both readings · certified 2026-08-31 · v1 · article view · machine-readable

Current reading — gain

AI models Gemini and FaceApp generated post-denture facial images rated as esthetically comparable to actual clinical outcomes by patients and experts.

Current reading — problem

AI simulations failed to accurately reproduce quantitative facial anthropometric changes after denture placement despite visual similarity.

What this doesn’t fix

Findings based on only 14 completely edentulous patients in a single within-subject observational design, limiting generalizability and statistical power.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0938, v1: “The Role of Artificial Intelligence Models in Predicting Post-Prosthetic Facial Esthetics in Edentulous Patients: Clinical and Anthropometric Comparative Study.” Truvace, 2026-08-31. /record/TRV-2026-0938 (accessed at citation time). sha256 aa12205efbb4426a

Calibration history

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

  1. Certifiedv1aa12205efbb4

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