1 / 12

Implementation Of A MedBiquitous Virtual Patient Compatible Web-Player

Implementation Of A MedBiquitous Virtual Patient Compatible Web-Player. Hess F, Heid J, Huber S, Haag M Centre for Virtual Patients, University Hospital of Heidelberg. The MedBiq Virtual Patient (MVP). SCORM-Package. Virtual Patient Data. Data Avail- ability Model. Activity Model.

rollo
Télécharger la présentation

Implementation Of A MedBiquitous Virtual Patient Compatible Web-Player

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 A MedBiquitous Virtual Patient Compatible Web-Player Hess F, Heid J, Huber S, Haag M Centre for Virtual Patients, University Hospital of Heidelberg

  2. The MedBiq Virtual Patient (MVP) SCORM-Package Virtual Patient Data Data Avail- ability Model Activity Model • XML files, combined with XPath expressions • Defines the interaction (Activity Model) between aggregated (Data Availability Model) data elements (Virtual Patient Data and Media Resources) for branched nodes Media Resources

  3. Starting Position: An Existing System • CAMPUS, a system for learning with Virtual Patients exists since 1996 • Consists of • An authoring system • A simulative Java based player • A card-based DHTML player • An application for secure, keyfeature-based assessments • Based on vocabularies • Linear order of interactions

  4. The MVP Spec: „And Now for Something Completely Different” • The MVP spec is based on free text, not on vocabularies • The MVP spec defines a network of nodes, no linear order • Knowledge questions are not directly supported by the MVP

  5. How to Overcome Those Differences? • Free text can‘t be matched with a vocabulary automatically • An export is quite simple as a linear path is possible in the MVP • The knowledge questions can be mapped to XHTML and/or added via extensions • The keyfeature editor, used for assessments, can be used to import and export free text nodes

  6. Screenshot of the Keyfeature Editor

  7. Finally: Displaying MVP VPs • To support all MVP VPs within CAMPUS a new MVP compatible player has to be developed • Because of the complexity of the MVP spec a pure client-side implementation is not recommendable • Different display modes and system based optimizations are possible with a server component

  8. The MVP Player: Technical View • Uses a full featured Java server component and a lightweight client written in HTML and JavaScript • Holding the object tree as Java objects for supporting MVP rules and display modes • Rendering the XHTML code using W3C standard XSLT • Uses Ajax for communication between client and server („getNode“)

  9. The MVP Player: Screenshot

  10. „getPage“ Modifies state Object-Model MVP Package JSON-packed response Serialization Transformation via XSLT The MVP Player: Workflow Server XHTML fragment XML file

  11. Where we are now… • Tested with the three other systems of the European „electronic Virtual Patients” (eViP) project • Support for QTI IMS extension • Support for W3Cs Timed Text • Need for other MVP packages • Free and open sourced MVP test suite available at http://code.google.com/p/mvp-evip-xslt-test-suite/

  12. Any questions? Thank you. Contact: Centre for Virtual Patients University Hospital Heidelberg http://campusvirtualpatients.com

More Related