TruaceTracing the truth around AISaturday, September 12, 2026
TRV-2026-1047Certified recordPeer-reviewed

How Well Do AI Chatbots Understand Abnormal Anatomy: A Comparative Study Using Congenital Anomalies and Tumor Cases

Artificial Intelligence (AI) chatbots are becoming an efficient option to understand medical data and also help with clinical reasoning. There has been a recent progression in research of large language models and their ability to be used in the healthcare sector, such as radiological image analysis, and diagnostic support. There is however, little evidence supporting their ability to accurately understand abnormal anatomical conditions, such as congenital anomalies and tumor related changes in anatomy. To asses…

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

Current reading — gain

In a 20-case test of congenital anomalies and tumors, ChatGPT, Gemini and Copilot achieved 80-95% diagnostic accuracy with detailed anatomical descriptions, suggesting potential as supplementary radiological diagnostic support.

Current reading — problem

Chatbots sometimes confused similar congenital anomalies and provided less detailed anatomical descriptions in complex tumor cases, requiring caution and verification by qualified professionals before clinical use.

What this doesn’t fix

Study evaluated only 20 representative cases (10 congenital, 10 tumor) using standard questions and images, limiting generalizability to broader clinical practice and more complex presentations.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1047, v1: “How Well Do AI Chatbots Understand Abnormal Anatomy: A Comparative Study Using Congenital Anomalies and Tumor Cases.” Truvace, 2026-09-10. /record/TRV-2026-1047 (accessed at citation time). sha256 049e092348a4b987

Calibration history

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

  1. Certifiedv1049e092348a4

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