TruaceTracing the truth around AIWednesday, August 26, 2026
TRV-2026-0064Retracted — remains on the recordPeer-reviewed

The growing field of digital psychiatry: current evidence and the future of apps, social media, chatbots, and virtual reality

As the COVID-19 pandemic has largely increased the utilization of telehealth, mobile mental health technologies - such as smartphone apps, vir-tual reality, chatbots, and social media - have also gained attention. These digital health technologies offer the potential of accessible and scalable interventions that can augment traditional care. In this paper, we provide a comprehensive update on the overall field of digital psychiatry, covering three areas. First, we outline the relevance of recent technological ad…

Health · G Space — documented gain · certified 2026-07-12 · v7 · article view · machine-readable

This record was retracted on 2026-07-13Model backfill: source did not support a publishable AI-impact claim. It remains permanently retrievable here, as does every prior version below.
Current reading — gain

The growing field of digital psychiatry: current evidence and the future of apps, social media, chatbots, and virtual reality: As the COVID-19 pandemic has largely increased the utilization of telehealth, mobile mental health technologies - such as smartphone apps, vir-tual reality, chatbots, and social media - have also gained attention.

Evidence

Cite this record

Truvace Impact Record TRV-2026-0064, v7: “The growing field of digital psychiatry: current evidence and the future of apps, social media, chatbots, and virtual reality.” Truvace, 2026-07-13. /record/TRV-2026-0064 (accessed at citation time). sha256 cc682fd47a92599b

Calibration history

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

  1. Retractedv7cc682fd47a92

    Model backfill: source did not support a publishable AI-impact claim

  2. Revisedv606644ae7c308

    Reading revised

  3. Sources changedv5be72bdc707a1

    Source set updated

  4. Sources changedv4c38fbc74f111

    Source set updated

  5. Sources changedv36e2ec1852148

    Source set updated

  6. Sources changedv21550cb19f17a

    Source set updated

  7. Certifiedv10d36f2df83a1

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