TruaceTracing the truth around AIWednesday, August 26, 2026
TRV-2026-0859Certified recordPeer-reviewed

Artificial intelligence-driven transformation in healthcare: the mediating role of technostress in the impact of openness to organizational change and attitude toward AI on innovative behavior

Purpose The rapid proliferation of artificial intelligence (AI) applications in healthcare is transforming the ways in which employees interact with technology, making it crucial to understand the effects of this process on employee behavior. The purpose of this study is to examine the effects of openness to organizational change and attitudes toward AI on employees' innovative behavior, and to test the mediating role of technostress in these effects. Design/methodology/approach The research was conducted using…

Health · The Trace — both readings · certified 2026-08-24 · v1 · article view · machine-readable

Current reading — gain

Healthcare workers with high openness to organizational change and positive attitudes toward AI reported lower technostress, which was linked to higher innovative work behavior.

Current reading — problem

Technostress mediated the relationship, such that when openness to change and positive AI attitudes were low, higher technostress was associated with reduced innovative work behavior among the same hospital staff.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0859, v1: “Artificial intelligence-driven transformation in healthcare: the mediating role of technostress in the impact of openness to organizational change and attitude toward AI on innovative behavior.” Truvace, 2026-08-24. /record/TRV-2026-0859 (accessed at citation time). sha256 60612a2a0cac72a0

Calibration history

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

  1. Certifiedv160612a2a0cac

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