70/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Physician AI disclosure, condition severity, and public trust in digital medicine

Truvace record
TRV-2026-3061raw data (JSON)
Version
v1Published
First published
Evidence type
Randomized controlled trial
Sources
1 sourcePeer-reviewed
sha256
6681c2c9c4c7…check it

Abstract Public trust is central to the implementation of artificial intelligence (AI) in digital medicine, yet little is known about how patients respond to different forms of physician AI disclosure across clinical risk contexts. In a 5 × 2 factorial experiment in mainland China, 1574 adults were randomly assigned to physician profiles varying by AI use type and condition severity. Administrative AI was rated more favorably than diagnostic and therapeutic AI across physician perception and care-seeking intenti…

The problem

In a randomized experiment with 1,574 adults in mainland China, physicians who disclosed diagnostic or therapeutic AI use were rated less favorably than those disclosing administrative AI, and high-severity conditions amplified negative responses to therapeutic AI.

What this doesn’t fix

The authors say the findings need preregistered replication using behavioral outcomes, and the mediation analyses were exploratory.

Sources

1 on file
  1. npj Digital Medicinedoi:10.1038/s41746-026-03484-7
    Peer-reviewed2026-11-19

Cite this record

v1

Truvace Impact Record TRV-2026-3061, v1: “Physician AI disclosure, condition severity, and public trust in digital medicine.” Truvace, 2026-11-19. /record/TRV-2026-3061 (accessed on the day you copy it). sha256 6681c2c9c4c7cd09…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv16681c2c9c4c7…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3061 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.