TRV-2026-2197Certified recordPeer-reviewed

Artificial intelligence (AI) anxiety and nurses’ turnover intention during healthcare digital transformation: the mediating role of occupational fatigue

Background The rapid integration of artificial intelligence (AI) into healthcare is associated with new psychological challenges. However, the extent of its impact on nursing workforce stability is unclear. Aim To explore the relationship between AI anxiety and turnover intention of clinical nurses, and the mediating effect of occupational fatigue and the moderating effect of emotional intelligence (EI). Methods A cross-sectional survey was conducted from March to June 2026 among 404 clinical nurses from four ho…

Health · Problem Space — documented harm · certified 2026-10-22 · v1 · article view · machine-readable

Current reading — problem

Among 404 clinical nurses in Jiangsu hospitals, higher AI anxiety was linked to greater occupational fatigue and stronger turnover intention, which threatens nursing workforce stability.

What this doesn’t fix

The study is a cross-sectional survey, and the authors describe fatigue only as a potential pathway, so the findings show association and cannot establish causation or actual nurse departures.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2197, v1: “Artificial intelligence (AI) anxiety and nurses’ turnover intention during healthcare digital transformation: the mediating role of occupational fatigue.” Truvace, 2026-10-22. /record/TRV-2026-2197 (accessed at citation time). sha256 cd600cb091ac077c…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1cd600cb091ac…

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