TRV-2026-1832Certified recordPeer-reviewed

Differences in perceived influences and educational support needs of generative AI among medical and nursing students across educational levels: a descriptive qualitative study

Generative artificial intelligence (GAI) has been extensively integrated into nursing and medical education, significantly transforming the academic practices of students. Nonetheless, the varying impacts of GAI on core competency of student across educational stages remain ambiguous, with limited empirical evidence on hierarchical educational support needs. Drawing on cross-sectional comparisons of GAI-related experiences among undergraduate, master’s, and doctoral students, this study aimed to explore differen…

Education · The Trace — both readings · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

Students perceived generative AI as benefiting critical thinking and knowledge acquisition, with research competency gains largely confined to postgraduates.

Current reading — problem

Students perceived generative AI as bringing risks of over-reliance, academic integrity breaches and cognitive offloading in their studies.

What this doesn’t fix

The authors say their proposed model is preliminary and needs further validation in diverse educational contexts; the sample is also from a single western Chinese medical university.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1832, v1: “Differences in perceived influences and educational support needs of generative AI among medical and nursing students across educational levels: a descriptive qualitative study.” Truvace, 2026-10-18. /record/TRV-2026-1832 (accessed at citation time). sha256 74e01968b001d353…

Calibration history

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

  1. Certifiedv174e01968b001…

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