Centre for Virtual Patients Time And Effort Of

Centre for Virtual Patients Time And Effort Of Repurposing Virtual Patients From CASUS To CAMPUS Using The e. Vi. P Standard: Automated Vs. Manual Transfer Benjamin Hanebeck 1; Stephan Oberle 1; Jörn Heid 2; Frank Hess 2; Inga Hege 3; Martin Fischer 4; Martin Haag 2; Sören Huwendiek 1 1 Department of General Paediatrics, University Hospital for Adolescent and Paediatric Medicine and Centre for Virtual Patients, Medical Faculty of Heidelberg University, Heidelberg, Germany ; 2 Centre for Virtual Patients, Medical Faculty of Heidelberg University, Heidelberg, Germany ; 3 Ludwig-Maximilians-University München, Germany ; 4 University Witten-Herdecke, Germany 2 nd International Conference on Virtual Patients & Med. Biquitous Annual Conference, 28. 04. 2010

Centre for Virtual Patients Introduction • Developing new virtual patients (VP) is costly • Repurposing existing VP is a reasonable means to save resources • However, transfer of VP between different VP systems is complicated

Centre for Virtual Patients Introduction • VP Standard was established: Medbiq VP taken as part of the e. Vi. P-standard as a shared structure • System specific features can be covered by extensions – QTI extension for knowledge-questions –. . . • Additionally, a repurposed VP needs to be adapted to local needs (content, scenario)

Centre for Virtual Patients Introduction • Efforts, boundaries and benefits of using the e. Vi. P-standard to transfer a VP from one VP-system to another are, as yet, unreported. • Does the standard reduce efforts by enabling automatic repurposing?

Centre for Virtual Patients Introduction • Efforts, boundaries and benefits of using the e. Vi. P-standard to transfer a VP from one VP-system to another are, as yet, unreported. • Does the standard reduce efforts by enabling automatic repurposing?

Centre for Virtual Patients Methods • Development of a new CAMPUS player component enables playback of e. Vi. PStandard-compliant material

Centre for Virtual Patients Methods Modification of the CAMPUS authoring component to enable • …import of e. Vi. P-Standard compliant VP with QTI support • … editing of the imported VP

Centre for Virtual Patients Methods • Choice of an appropriate VP-System for VP exchange / automated repurposing • CASUS and CAMPUS – linear VP structures – QTI extension • Selection of 15 VP from CASUS in average 17, 7 cards/VP (± 6, 2)

Centre for Virtual Patients Methods - Manual repurposing • A new blank CAMPUS VP was created • The content was copied manually from the existing CASUS VP into the CAMPUS authoring component • Question were recreated where possible, Media was embedded • Efforts were noted by using the e. Vi. P effort sheet

Centre for Virtual Patients Methods - Automated repurposing • An e. Vi. P-Standard compliant export of the CASUS VP was imported into the CAMPUS authoring component

Centre for Virtual Patients Methods - Automated repurposing • Playback and check of the VP • Corrections were made where necessary • Efforts were noted manually • In all cases of manual and automatic import: No efforts for content adaption were taken into account

Centre for Virtual Patients Results – Manual repurposing It took 11, 3 hours in average / VP.

Centre for Virtual Patients Results – Automated repurposing It took 1, 8 hours in average / VP.

Centre for Virtual Patients Results – Automated repurposing: Issues Problems: • Hyperlinks imported incorrectly (concerning CASUS Expert Network, links to videos, external resources…) • Some questions displayed incorrectly (e. g. sorting task) • Layout problems (e. g. different font types) • Labels of pictures not displayed Solutions: Manual corrections

Centre for Virtual Patients Boundaries • Originating VP has to be e. Vi. P-Standard compliant • As many extensions as possible should be shared between the used VP systems (e. g. QTI) • Results were achieved with easy repurposing approach (linear pathway, QTI extension, same language) • Efforts increase with differences between VP systems (e. g. linear vs. branched)

Centre for Virtual Patients Benefits • Repurposing VP is a lot more time efficient by using an automated import • Only little corrections necessary • Adaptations / extension of content in target VP system possible • Improving of export/import-functionalities continuously increases quality of interoperability

Centre for Virtual Patients Conclusion • Repurposing VP using the e. Vi. P-standard can save time and efforts • Not completely automated but semi-automated repurposing process +

Centre for Virtual Patients Thank you! Contact: www. campusvirtuals. de

Is still done • but beforehand • only once Resulting in an increase in interoperability

Centre for Virtual Patients Results – manual repurposing It took 11, 3 hours in average / VP.

Centre for Virtual Patients Results – automated repurposing: Problems and Solutions Problem Solution Duplicated questions Manual deletion (double import) External links did not Manual integration work (e. g. videos) Answers to questions were doubled Manual correction

Centre for Virtual Patients Results – automated repurposing It took 1, 8 hours in average / VP.

Centre for Virtual Patients Introduction • Remaining problem: – Teaching content sometimes differs not only internationally but also nationally – Often an identical reproduction of a VP is not satisfactory for teachers • Need: No playback-only solution, but possibilities to edit and adapt a VP

Centre for Virtual Patients Results – manual repurposing: Problems and Solutions Missing question types • Problem: some types are not natively supported by CAMPUS authoring component (e. g. rating of symptoms, sorting tasks) • Solution: • manual substitution by an available question type (e. g. MCQ, free text) covering the same content • manual creation of an interactive graphic based on Flash using an editor implemented in CAMPUS

Centre for Virtual Patients Methods • CAMPUS, a system for learning with VP exists since 1996 • Consists of – – An authoring system A simulative Java based player A card-based e. Vi. P standard compliant player An application for secure, keyfeature-based assessments • Linear order of interactions