TRV-2026-1571Certified recordPeer-reviewed

Comparative evaluation of ChatGPT and Gemini feedback in scenario-based clinical reasoning among medical interns

Objective: Artificial intelligence tools are increasingly used to provide individualized feedback in medical education. The aim of this study was to compare the quality of feedback generated by ChatGPT and Gemini during scenario-based clinical reasoning activities. Methods: A convergent mixed-methods study was conducted with 32 medical interns randomly assigned to ChatGPT (n=16) or Gemini (n=16). Following a virtual patient interview on iron deficiency anemia, artificial intelligence-generated feedback was evalu…

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

Current reading — gain

Both chatbots produced feedback that interns and medical education specialists rated as clear, supportive and educationally useful in a virtual iron deficiency anemia case.

Current reading — problem

Feedback from both chatbots lacked patient-centeredness and systematicity and sometimes included unrealistic statements, so it cannot replace expert supervision.

What this doesn’t fix

The study compared the tools in a single virtual scenario with 32 interns and found no significant differences, while both tools shared limits such as weak patient-centeredness and occasional unrealistic statements.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1571, v1: “Comparative evaluation of ChatGPT and Gemini feedback in scenario-based clinical reasoning among medical interns.” Truvace, 2026-10-16. /record/TRV-2026-1571 (accessed at citation time). sha256 69e7fabaa4469426…

Calibration history

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

  1. Certifiedv169e7fabaa446…

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