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

Artificial intelligence technologies and compassion in healthcare: A systematic scoping review

Background Advances in artificial intelligence (AI) technologies, together with the availability of big data in society, creates uncertainties about how these developments will affect healthcare systems worldwide. Compassion is essential for high-quality healthcare and research shows how prosocial caring behaviors benefit human health and societies. However, the possible association between AI technologies and compassion is under conceptualized and underexplored. Objectives The aim of this scoping review is to p…

Health · G Space — documented gain · certified 2026-07-12 · v5 · 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

Artificial intelligence technologies and compassion in healthcare: A systematic scoping review: Compassion is essential for high-quality healthcare and research shows how prosocial caring behaviors benefit human health and societies.

Evidence

Cite this record

Truvace Impact Record TRV-2026-0063, v5: “Artificial intelligence technologies and compassion in healthcare: A systematic scoping review.” Truvace, 2026-07-13. /record/TRV-2026-0063 (accessed at citation time). sha256 2a372e5061784874

Calibration history

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

  1. Retractedv52a372e506178

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

  2. Revisedv450f35a9179b7

    Reading revised

  3. Sources changedv3b99a4a507730

    Source set updated

  4. Sources changedv2d8e7dda7577c

    Source set updated

  5. Certifiedv1cd69cb8fc0c9

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