60/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Diagnostic performance of ChatGPT in adnexal mass classification: A comparative study with frozen section and final histopathology

Truvace record
TRV-2026-2915raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
af6a8681864e…check it

Objective To evaluate the diagnostic performance of ChatGPT in classifying adnexal masses as benign, borderline, or malignant, and to compare its performance with intraoperative frozen-section analysis, using final histopathology as the reference standard. Materials and methods This retrospective, observational, comparative study included 259 patients who underwent surgery for ovarian masses between January 2021 and July 2025. Preoperative clinical data, laboratory parameters, and ultrasonographic findings were…

The problem

In a retrospective study of 259 ovarian surgery patients, ChatGPT's positive predictive value for malignancy was 56.3% versus 100% for frozen section, with specificity of 92.5% versus 100%, so it produced many more false positives.

What this doesn’t fix

The study was retrospective and observational, and ChatGPT was run on structured clinical inputs without prompt optimization, so results may not reflect optimized or prospective use.

Sources

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

Cite this record

v1

Truvace Impact Record TRV-2026-2915, v1: “Diagnostic performance of ChatGPT in adnexal mass classification: A comparative study with frozen section and final histopathology.” Truvace, 2026-11-14. /record/TRV-2026-2915 (accessed on the day you copy it). sha256 af6a8681864e1015…

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

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