aceModerate evidence
Published recordHealthGood Space
More
Application of an Artificial Intelligence Simulated Patient Model in Teaching Neurosurgical Decision-Making
- Truvace record
- TRV-2026-2459raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- dd7bbe08e35c…check it
AIM: Training in neurosurgical decision-making remains a challenging component of standardized residency training. Traditional teaching models are limited in their ability to simulate the uncertainty and complexity encountered in real-world clinical scenarios. As a novel educational tool, the potential value of artificial intelligence (AI)-simulated patient models in surgical decision-making training requires further evaluation. This study aimed to explore the application of an AI-simulated patient model in neur…
The gain
In a retrospective study of 157 neurosurgery residents, the 72 who trained with a DeepSeek-based AI virtual patient scored higher on a surgical decision-making exam than the 85 taught by traditional case discussion.
What this doesn’t fix
The study was retrospective and compared two cohorts trained in different periods rather than randomized groups, so the authors can report only an association between the AI model and better performance.
Sources
1 on file- Annali Italiani di Chirurgiadoi:10.62713/aic.4849
Cite this record
v1Truvace Impact Record TRV-2026-2459, v1: “Application of an Artificial Intelligence Simulated Patient Model in Teaching Neurosurgical Decision-Making.” Truvace, 2026-11-10. /record/TRV-2026-2459 (accessed on the day you copy it). sha256 dd7bbe08e35c1e57…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2459 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.