September Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability of Virtual Patients Findings from the eViP project
eViP September 2006 Aims of the presentation What eViP is about The goals of this sub-project How we achieved our goals Results Challenges Recommendations
eViP September 2006 What is eViP about? eViP = Project about electronic Virtual Patients 3 year ( ) project, 9 partners and co-funded by the European Union Main outcome Create a bank of repurposed and enriched multilingual and multicultural virtual patients and share them
eViP September 2006 The goals of the sub-project Development of the systematic method for exchanging virtual patient cases between VP systems = eViP application profile Implementation of the eViP application profile by 4 VP systems = import/export of VPs
September 2006 Participating systems CASUS Campus Web-SP Open Labyrinth
eViP September 2006 Result: eViP application profile The aim of application profiles is the selection and re-use of existing elements to tailor to the needs of a given group of users. MedBiquitous Virtual Patient 0.48 MedBiquitous Healthcare Learning Object Metadata (Healthcare LOM) SCORM packages Conformance testing suite What does this mean???
September 2006 The same VP in different systems
September 2006 Challenge 1 Importing a branched VP to linear VP system Node Branched VPLinear VP Node
September 2006 Challenge 1 - Implications Import all branches Put information about (best) next node(s), end nodes(s) and start node into imported VP Has to be done manually
September 2006 Challenge 2 Importing a linear VP to a branched VP system Node Branched VPLinear VP Node
September 2006 Challenge 3 PhysicalExam InterviewItem Diagnosis Therapy "Structured" system Text Element "Non-Structured" system Text Element ??? Importing and exporting from "structured" to "unstructured"
eViP September 2006 How the VP systems use different parts of the specifications Differences Semi-linear systems use many specialized fields Linear systems use mostly text elements (VPDText) Branched systems use many Link and Rule elements Similarities All elements in DataAvailabilityModel (DAM) are used 3 of the 4 systems use XtensibleInfo Not used elements: Conditional Rules, Counter, Timer, Specialized Body Locations
September 2006 Best practice guidelines Possibility to override exported content Conformance level testing Package validation XML/XSD validation Import validation Runtime validation External specifications handling XtensibleInfo e.g. IMS QTI, W3C Timed Text format Use same version of specification automated by testing suites manually in target system
September Thank you! Nabil Zary More information: