Enabling Interoperability, Accessibility and Reusability of Virtual Patients Findings from the e. Vi. P project Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J September 2006 www. virtualpatients
Aims of the presentation • • • What e. Vi. P is about The goals of this sub-project How we achieved our goals Results Challenges Recommendations e. Vi. P September 2006 www. virtualpatients
What is e. Vi. P about? • • e. Vi. P = Project about electronic Virtual Patients 3 year (2007 -2010) 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 e. Vi. P September 2006 www. virtualpatients
The goals of the sub-project • Development of the systematic method for exchanging virtual patient cases between VP systems = e. Vi. P application profile • Implementation of the e. Vi. P application profile by 4 VP systems e. Vi. P = import/export of VPs September 2006 www. virtualpatients
Participating systems Campus Web-SP Open Labyrinth CASUS September 2006 www. virtualpatients
Result: e. Vi. P 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. • Med. Biquitous Virtual Patient 0. 48 • Med. Biquitous Healthcare Learning Object Metadata (Healthcare LOM) • SCORM packages • Conformance testing suite e. Vi. P What does this mean? ? ? September 2006 www. virtualpatients
The same VP in different systems September 2006 www. virtualpatients
Challenge 1 • Importing a branched VP to linear VP system Branched VP Linear VP Node Node Node Node September 2006 www. virtualpatients
Challenge 1 - Implications • Has to be done manually • • Import all branches Put information about (best) next node(s), end nodes(s) and start node into imported VP September 2006 www. virtualpatients
Challenge 2 • Importing a linear VP to a branched VP system Branched VP Linear VP Node Node Node Node September 2006 www. virtualpatients
Challenge 3 • Importing and exporting from "structured" to "unstructured" "Structured" system Physical. Exam Interview. Item Diagnosis Therapy "Non-Structured" system ? ? ? Text Element September 2006 www. virtualpatients
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 e. Vi. P Similarities • All elements in Data. Availability. Model (DAM) are used • 3 of the 4 systems use Xtensible. Info • Not used elements: Conditional Rules, Counter, Timer, Specialized Body Locations September 2006 www. virtualpatients
Best practice guidelines • • Possibility to override exported content Conformance level testing • Package validation automated by testing suites • XML/XSD validation • Import validation manually in target system • Runtime validation • External specifications handling • Xtensible. Info • e. g. IMS QTI, W 3 C Timed Text format Use same version of specification • September 2006 www. virtualpatients
Thank you! Nabil Zary Nabil. Zary@ki. se More information: www. virtualpatients. eu September 2006 www. virtualpatients
Скачать презентацию Enabling Interoperability Accessibility and Reusability of Virtual Patients
4b2111829664769e7671723b4ae27977.ppt