70/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Full (total) pulpotomy versus non-surgical root canal treatment for irreversible pulpitis: a human-led umbrella review with AI-assisted appraisal

Truvace record
TRV-2026-3003raw data (JSON)
Version
v1Published
First published
Evidence type
Systematic review or meta-analysis
Sources
1 sourcePeer-reviewed
sha256
05b43c924358…check it

To evaluate systematic reviews and meta-analyses comparing vital pulp treatments (VPTs) with non-surgical root canal treatment (NSRCT) for irreversible pulpitis (IP) in permanent teeth, focusing on clinical/radiographic success and postoperative pain, and to compare AI (ChatGPT-4.1) with human reviewers for risk of bias (ROBIS) and methodological quality (AMSTAR-2). PubMed, Web of Science, Scopus, Cochrane Library, EBSCO and Google Scholar were searched from inception to January 2026 according to PRISMA 2020. Pr…

The problem

In an umbrella review of 12 systematic reviews on dental pulp treatment, ChatGPT-4.1 matched two human reviewers' overall AMSTAR-2 confidence rating only 66.7% of the time (κ = 0.529), so a third of ratings differed.

What this doesn’t fix

The certainty of the dental findings is limited by a small, overlapping primary evidence base of 11 unique studies, and no eligible reviews covered other vital pulp treatments.

Sources

1 on file
  1. Evidence-Based Dentistrydoi:10.1038/s41432-026-01247-7
    Peer-reviewed2026-11-16

Cite this record

v1

Truvace Impact Record TRV-2026-3003, v1: “Full (total) pulpotomy versus non-surgical root canal treatment for irreversible pulpitis: a human-led umbrella review with AI-assisted appraisal.” Truvace, 2026-11-17. /record/TRV-2026-3003 (accessed on the day you copy it). sha256 05b43c9243582d17…

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. Publishedv105b43c924358…

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