aceIntegration of artificial intelligence in quality improvement projects for undergraduate nursing students: Enhancing nursing education through innovative applications
Background and objective: Nursing faculty have been hesitant to incorporate artificial intelligence into coursework due to various reasons, including the risk of affecting academic integrity and the potential for receiving inaccurate information. As nursing cohorts continue to grow, innovative approaches are needed to meet learning objectives; such as artificial intelligence. Incorporating artificial intelligence into group projects may increase responsible, ethical, and critical use of artificial intelligence a…
Six undergraduate nursing students who used AI to find evidence for a patient safety project reported useful creative ideas, workflow steps and a broad range of solutions, and AI findings matched most of their literature review articles.
Students found the AI output lacked concrete examples and tended to be more practical than theoretical, which limits how far it can replace conventional literature review work.
The initiative involved only six self-selecting students in one honors course option, so the reported benefits and challenges cannot be generalized to wider nursing cohorts.
Evidence
- Peer-reviewedJournal of Nursing Education and Practice2026-10-22
How should this claim be treated?
Truvace Impact Record TRV-2026-2193, v1: “Integration of artificial intelligence in quality improvement projects for undergraduate nursing students: Enhancing nursing education through innovative applications.” Truvace, 2026-10-22. /record/TRV-2026-2193 (accessed at citation time). sha256 2204b8247c4b03bb…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2193 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.