TRV-2026-2360Certified recordPeer-reviewed

Patient trust in medical AI: Conditions under which chatbots are preferred over human providers

Background Artificial intelligence (AI) tools, including medical chatbots, are increasingly integrated into health care delivery. While prior research emphasizes diagnostic accuracy and usability, less is known about the psychological and contextual factors that shape patients' trust and preferences for AI versus human providers, particularly among patients who have experienced medical stigma. Purpose This study investigates when and why patients may prefer medical chatbots over human providers, focusing on the…

Health · Good Space — documented gain · certified 2026-11-04 · v2 · article view · machine-readable

Current reading — gain

In two hypothetical-scenario experiments with 750 participants, those with past medical stigma or more comfort with medical AI reported greater trust in a chatbot, though overall people preferred human providers.

What this doesn’t fix

The findings come from scenario-based experiments, and the authors frame the benefits as applying only to selected contexts, especially low-stakes concerns, rather than care in general.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2360, v2: “Patient trust in medical AI: Conditions under which chatbots are preferred over human providers.” Truvace, 2026-11-04. /record/TRV-2026-2360 (accessed at citation time). sha256 c651d5036709b558…

Calibration history

Every change to this record since certification, in the open.

  1. Revisedv2c651d5036709…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Certifiedv1b10cfddd8659…

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