TRV-2026-1746Certified recordPeer-reviewed

Evaluating Generative Artificial Intelligence Chatbots in Answering Public Questions About Altered Consciousness: A Comparative Study of Safety, Accuracy, Reliability, and Readability

Introduction People increasingly use generative artificial intelligence chatbots to interpret health concerns before contacting clinicians. Although these systems are not formal autonomous emergency department triage tools, their responses may influence whether and when users seek professional care. Altered consciousness is especially high-risk because delayed or ambiguous escalation can postpone time-sensitive evaluation. This study evaluated the safety and quality of chatbot answers from an emergency nursing p…

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

Current reading — gain

Across 330 chatbot responses, nurse-rated safe-response rates were high, from 89.4% to 95.5%, suggesting chatbots can support public education about altered consciousness.

Current reading — problem

Every tested chatbot produced at least one potentially unsafe answer, with omissions, unsafe sequencing and urgency-softening making them unsuitable for autonomous triage.

What this doesn’t fix

Each question was submitted only once per chatbot, and the paper itself concludes the tools are unsuitable for autonomous triage because every model produced at least one potentially unsafe answer.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1746, v1: “Evaluating Generative Artificial Intelligence Chatbots in Answering Public Questions About Altered Consciousness: A Comparative Study of Safety, Accuracy, Reliability, and Readability.” Truvace, 2026-10-17. /record/TRV-2026-1746 (accessed at citation time). sha256 9e1d5d430630f085…

Calibration history

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

  1. Certifiedv19e1d5d430630…

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