1 / 15

virtualpatients.eu

Implementation of the MVP standard by four European VP systems – challenges and recommendations. T. Calinici, D. Davies, J. Donkers, I. Hege, J. Heid, A. Kononowicz, L. Woodham, N. Zary (Technical reference group of eViP). www.virtualpatients.eu. Overview. What is eViP?

eellen
Download Presentation

virtualpatients.eu

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementation of the MVP standard by four European VP systems – challenges and recommendations T. Calinici, D. Davies, J. Donkers, I. Hege, J. Heid, A. Kononowicz, L. Woodham, N. Zary(Technical reference group of eViP) www.virtualpatients.eu

  2. Overview • What is eViP? • Participating systems • Implementation of the MVP standard • Challenges and Best Practice Guidelines • Future Work eViP www.virtualpatients.eu

  3. What is eViP • eViP = electronic Virtual Patients • 3 year project co-funded by the European Union • Aim: create a bank of repurposed and enriched multicultural virtual patients • Development of the eViP application profile for exchanging virtual patient cases between systems eViP www.virtualpatients.eu

  4. eViP application profile (2.0.1) • MedBiquitous Virtual Patient spec 0.48 • Standard for Learning Object Metadata (LOM) • MedBiquitous Healthcare Learning Object Metadata Spec (Healthcare LOM) • SCORM packages • Conformance testing suite • External to the profile: • IMS Question and Test Interoperability specification (QTI) • W3C Timed Text (TT) Authoring Format 1.0 eViP www.virtualpatients.eu

  5. Participating systems Campus Web-SP OpenLabyrinth CASUS www.virtualpatients.eu

  6. Participating systems Campus VP Web-SP Import Export OpenLabyrinth CAMPUSVP XML CASUS XSLT University of Heidelberg, Germany Model: semi-linear Terminology-based system Implementation: using XSLT CAMPUSeViP zip www.virtualpatients.eu

  7. Participating systems WEB-SPVP Campus Web-SP OpenLabyrinth Java model of MVP CASUS ??? Karolinksa Institutet, Sweden Model: semi-linear Implementation: XML files zip file www.virtualpatients.eu

  8. Participating systems OpenLabyrinthVP Campus St. Georges University, UK Model: branched Implementation: Using a C#.Net model Web-SP OpenLabyrinth C#.Net model of MVP CASUS ??? XML files zip file www.virtualpatients.eu

  9. Participating systems CASUSVP Campus University of Muenchen, Germany Model: linear Implementation: using Java model, Castor Web-SP OpenLabyrinth Java model of MVP CASUS Castor XML files zip file www.virtualpatients.eu

  10. Usage statistics • Semi-linear systems use many specialized fields • Linear systems use mostly text elements (VPDText) • Branched systems use many Link and Rule elements • All elements in DataAvailabilityModel (DAM) are used • 3 systems use XtensibleInfo • Not used elements: Conditional Rules, Counter, Timer, Specialized Body Locations eViP www.virtualpatients.eu

  11. Challenges - Example • Importing and exporting from branched to linear and vice versa: Branched VP Linear VP Node Node Node Node Node Node Node Node Node Node Node Node www.virtualpatients.eu

  12. Challenges - Example Branched structure in OpenLabyrinth Linear structure in CASUS www.virtualpatients.eu

  13. Best practice guidelines • Possibility to override exported content • Conformance level testing • Package validation • XML/XSD validation • Import validation • Runtime validation • External specifications handling • XtensibleInfo (add schema files and create namespace) • e.g. IMS QTI, W3C Timed Text format • Use same version of specification automated by testing suites manually in target system www.virtualpatients.eu

  14. Future Work • Using the import/export functionality in "real life" • Evaluate the semi-automatic repurposing process • Develop best-practice guidelines for this process • Increase number of case studies • Consider updates of MVP • Dissemination of results • Storage of consent forms • eViP profile metadata • Storing VP's repurposing lifecycle www.virtualpatients.eu

  15. Thank you! More information: www.virtualpatients.eu www.virtualpatients.eu

More Related