68/100

Moderate evidence

GainPublished recordHealthGood Space

Mental Health Support for People with Depression Using Artificial Intelligence: The Effects of Appearance and Emotion Anthropomorphism

Truvace record
TRV-2026-2558raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
31f349bf736e…check it

Abstract Depression is globally prevalent, yet psychiatric shortages restrict care access. Artificial intelligence (AI) doctors may address this shortage, but their adoption is hindered by distrust and privacy concerns. By making AI doctors seem socially present and humanlike, anthropomorphic design may shape users’ psychological responses. Drawing on media equation theory, this study distinguishes between appearance and emotion anthropomorphism and examines their effects on trust, privacy concerns, and adoption…

The gain

In a 2 × 2 experiment with 319 participants, an AI doctor designed to express emotion increased trust and reduced privacy concerns, and higher trust raised intention to adopt it for depression support.

What this doesn’t fix

The findings come from an experiment measuring intentions to adopt an AI doctor among 319 participants, not actual use or clinical outcomes for people with depression.

Sources

1 on file
  1. Information Systems Frontiersdoi:10.1007/s10796-026-10807-2
    Peer-reviewed2026-08-24

Cite this record

v1

Truvace Impact Record TRV-2026-2558, v1: “Mental Health Support for People with Depression Using Artificial Intelligence: The Effects of Appearance and Emotion Anthropomorphism.” Truvace, 2026-11-12. /record/TRV-2026-2558 (accessed on the day you copy it). sha256 31f349bf736ec919…

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. Publishedv131f349bf736e…

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