TRV-2026-1453Certified recordPeer-reviewed

Comparative Evaluation of Large Language Models in the Recognition of Postoperative Complications Following Aesthetic Surgery

Background: Large language models (LLMs) are increasingly being explored as supportive tools in postoperative patient communication. However, their ability to recognize and appropriately manage postoperative surgical complications remains unclear. This study comparatively evaluated ChatGPT, Gemini, and Claude in postoperative complication assessment following aesthetic surgical procedures. Methods: Thirty standardized postoperative clinical scenarios representing low-, moderate-, and high-risk complications were…

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

Current reading — gain

In 30 standardized aesthetic-surgery scenarios, three LLMs showed moderate-to-high ability to recognize common postoperative complications, with diagnostic accuracy means near 3.6 to 4.0 on a 5-point scale.

Current reading — problem

Performance varied in clinically urgent scenarios: Gemini recommended appropriate emergency referral in only 76.7% of high-risk evaluations, and it had the most critical management errors.

What this doesn’t fix

The study used 30 standardized scenarios rather than real patient interactions, and the authors note variability became more apparent in clinically urgent cases, so the tools cannot replace physician assessment.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1453, v1: “Comparative Evaluation of Large Language Models in the Recognition of Postoperative Complications Following Aesthetic Surgery.” Truvace, 2026-10-15. /record/TRV-2026-1453 (accessed at citation time). sha256 94587b081c504eb4…

Calibration history

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

  1. Certifiedv194587b081c50…

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