TRV-2026-1864Certified recordPeer-reviewed

A Patient Simulation Framework for Risk Assessment of Conversational Health Care AI: Development and Evaluation Study

Background Conversational AI systems are increasingly being deployed in health care for clinical decision support, but their performance varies substantially across patient communication styles, health literacy levels, and behavioral patterns. Static benchmarks cannot capture multiturn dynamics through which this variation compounds, and no current evaluation framework implements structured AI risk management guidance for conversational health care AI. The result is a structural risk: AI systems may perform well…

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

Current reading — gain

A simulation framework aligned with the NIST AI RMF exposes performance risks in conversational clinical AI before deployment, with simulated patients expressing medical concepts at high fidelity.

Current reading — problem

The antidepressant decision aid degraded steadily as health literacy fell, retrieving the top concept correctly 47.6% of the time for limited literacy versus 81.9% for proficient literacy.

What this doesn’t fix

The framework was evaluated only on antidepressant selection, so its usefulness for other clinical decision-aid tasks has not been shown.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1864, v1: “A Patient Simulation Framework for Risk Assessment of Conversational Health Care AI: Development and Evaluation Study.” Truvace, 2026-10-18. /record/TRV-2026-1864 (accessed at citation time). sha256 778278fdd05abc66…

Calibration history

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

  1. Certifiedv1778278fdd05a…

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