50/100

Moderate evidence

GainPublished recordHealthGood Space

Examining the impact of artificial intelligence on physicians' performance: mediating effects of innovative work behavior and skills enhancement

Truvace record
TRV-2026-2690raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
0a60ed16b3a2…check it

PURPOSE: While prior studies have explored artificial intelligence (AI) adoption in various sectors, the specific impact on employee performance in healthcare organizations remains underexamined, particularly regarding the mediating roles of innovative work behavior and skills enhancement. This study critically investigates whether AI adoption genuinely enhances employee performance or if its effects are overstated, scrutinizing the extent to which innovative work behavior and skills development mediate this rel…

The gain

In a questionnaire survey of 240 healthcare professionals in a developing country, AI adoption was significantly and positively associated with employee performance, through more innovative work behavior and skills development.

What this doesn’t fix

The evidence comes from a questionnaire of 240 healthcare professionals in a single developing context with technological and resource constraints, so results may not carry over to other settings.

Sources

1 on file
  1. Peer-reviewed2026-05-26

Cite this record

v1

Truvace Impact Record TRV-2026-2690, v1: “Examining the impact of artificial intelligence on physicians' performance: mediating effects of innovative work behavior and skills enhancement.” Truvace, 2026-11-12. /record/TRV-2026-2690 (accessed on the day you copy it). sha256 0a60ed16b3a2df90…

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

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