TRV-2026-2254Version 1 · Certified

Written 2026-10-25 18:34:46 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2254
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-25T18:34:46.003586Z
status: published
lens: trace
sector: health
headline: Quality, Transparency, and Readability of Artificial Intelligence Chatbots as Sources of Plagiocephaly Information: A Cross-Sectional Comparative Study
dek: Parents increasingly use artificial intelligence chatbots for information about plagiocephaly, but the quality and readability of their responses remain uncertain. This cross-sectional study compared 4 mainstream artificial intelligence chatbots using 37 high-frequency English queries identified through Google Trends for "plagiocephaly" worldwide over the previous 5 years. On August 18, 2026, the queries were submitted to ChatGPT 5.5, Gemini 3.5 Flash, Perplexity, and Copilot, generating 148 responses. Informati…
gain_title: Chatbots gave coherent, relatively complete plagiocephaly information, with a median Global Quality Scale score of 4.00 across all four models.
problem_title: Chatbot plagiocephaly answers were written above recommended reading levels and offered limited source transparency, with quality varying widely between models.
trace_subject: AI chatbot responses to parent queries about plagiocephaly
gain_reading: Chatbots gave coherent, relatively complete plagiocephaly information, with a median Global Quality Scale score of 4.00 across all four models.
gain_evidence: Artificial intelligence chatbots provided coherent, relatively complete plagiocephaly information
problem_reading: Chatbot plagiocephaly answers were written above recommended reading levels and offered limited source transparency, with quality varying widely between models.
problem_evidence: source transparency was limited, and readability was poor
quick_read: Researchers submitted 37 frequently searched plagiocephaly questions to four chatbots (ChatGPT 5.5, Gemini 3.5 Flash, Perplexity and Copilot) on August 18, 2026, producing 148 responses. They rated each response with DISCERN, EQIP, JAMA Benchmark and Global Quality Scale tools and with six readability indices.

Parents are turning to chatbots for health information, so uneven quality and text pitched at a high reading level could limit how useful and trustworthy the answers are in practice. The study tested only English queries at a single point in time, and the source does not say how well the findings would hold for other models, languages or later versions.
limitation: The study used only English queries submitted on a single date to four chatbot versions, so the findings reflect a snapshot of those models.
tag: Dual reading
key_points: Perplexity had the highest median DISCERN score (50.00) and Gemini the lowest (38.00). | Copilot had the highest median EQIP score (85.00) and Gemini the lowest (60.00). | Median JAMA Benchmark scores were 1.00 for ChatGPT, Perplexity and Copilot and 0.00 for Gemini. | Flesch-Kincaid Grade Level ranged from 11.66 to 13.14, and Flesch Reading Ease from 34.60 to 45.71, so no model met recommended readability thresholds.
rundown: The study was cross-sectional and drew its 37 high-frequency English queries from Google Trends for the term plagiocephaly worldwide over the previous five years.

Between-model differences were tested with the Friedman test, Kendall W effect sizes and Holm-adjusted paired Wilcoxon signed-rank tests, and quality scores differed significantly among the models.

The authors conclude chatbot responses should supplement rather than replace professional assessment, and that patient-facing content needs professional review, source traceability and lower reading levels.
sources:
- peer_reviewed | Journal of Craniofacial Surgery | https://doi.org/10.1097/scs.0000000000013552 | 2026-10-23
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
b3e344afd56dce8a209adff286e6025a3ca9cd623cf39727f072db9ffe4e5349
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2254 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.