Effect of Large Language Model-Powered Virtual Standardized Patients on History-Taking Among Undergraduate Medical Students: Propensity-Matched Cohort Study
Background Medical history taking (MHT) is a foundational clinical competency for medical students; however, traditional training models using standardized patients face challenges such as resource constraints. Large language model-powered virtual standardized patients (LLM-VSPs) offer a safe, repeatable platform for self-directed practice with AI-automated feedback. Nevertheless, their effectiveness in authentic teaching environments and underlying learning mechanisms require further investigation. Objective Th…
Undergraduate medical students who used LLM-powered virtual standardized patients as extracurricular self-practice achieved higher end-of-term history-taking performance at an OSCE with real standardized patients compared to routine instruction.
Students with medium and low baseline history-taking proficiency showed relatively limited score improvements from LLM-VSP self-practice, with practice frequency alone not independently predicting final performance.
Effect may depend on baseline proficiency, with preliminary evidence of a cognitive threshold where only students with solid theoretical foundations benefit substantially, and assignment was based on voluntary participation requiring propensity matching rather than randomization.
Evidence
- Peer-reviewedJMIR Medical Education2026-09-09
How should this claim be treated?
Truvace Impact Record TRV-2026-1044, v1: “Effect of Large Language Model-Powered Virtual Standardized Patients on History-Taking Among Undergraduate Medical Students: Propensity-Matched Cohort Study.” Truvace, 2026-09-10. /record/TRV-2026-1044 (accessed at citation time). sha256 75073b2f5a6fb37c…
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-1044 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.
ace