1 / 14
Télécharger la présentation

Enhancing Virtual Patient Interoperability and Accessibility

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. Enabling Interoperability, Accessibility and Reusability of Virtual Patients Findings from the eViP project Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J www.virtualpatients.eu

  2. Aims of the presentation • What eViP is about • The goals of this sub-project • How we achieved our goals • Results • Challenges • Recommendations eViP www.virtualpatients.eu

  3. What is eViP about? • eViP = 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 eViP www.virtualpatients.eu

  4. 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 eViP www.virtualpatients.eu

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

  6. Result: eViP application profile • The aimofapplicationprofilesistheselection and re-useofexistingelementstotailortotheneedsof a givengroupofusers. • MedBiquitous Virtual Patient 0.48 • MedBiquitous Healthcare Learning ObjectMetadata (Healthcare LOM) • SCORM packages • Conformancetestingsuite • Whatdoesthismean??? eViP www.virtualpatients.eu

  7. The same VP in different systems www.virtualpatients.eu

  8. Challenge 1 • Importing a branched VP to linear VP system Branched VP Linear VP Node Node Node Node Node Node Node Node Node Node Node Node Node www.virtualpatients.eu

  9. 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 www.virtualpatients.eu

  10. Challenge 2 • Importing a linear VP to a branched VP system Branched VP Linear VP Node Node Node Node Node Node Node Node Node Node Node Node Node www.virtualpatients.eu

  11. Challenge 3 • Importing and exporting from "structured" to "unstructured" "Structured" system "Non-Structured" system ??? PhysicalExam Text Element Text Element InterviewItem Text Element Diagnosis Text Element Therapy www.virtualpatients.eu

  12. 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 eViP 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 • 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. Thankyou! Nabil Zary Nabil.Zary@ki.se More information: www.virtualpatients.eu www.virtualpatients.eu

More Related