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 MCentre for Virtual Patients, University Hospital of Heidelberg

The MedBiq Virtual Patient (MVP)

• 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

SCORM-Package

VirtualPatient Data

Data Avail-ability Model

ActivityModel

Media Resources

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

• 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

The MVP Spec: „And Now for Something Completely Different”

• 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

How to Overcome Those Differences?

Screenshot of the Keyfeature Editor

• 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

Finally: Displaying MVP VPs

• 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“)

The MVP Player: Technical View

The MVP Player: Screenshot

The MVP Player: Workflow

Server„getPage“

Modifies state

Object-Model

MVPPackage

XMLfile

XHTMLfragment

JSON-packedresponse

Transformationvia XSLT

Serialization

• 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/

Where we are now…

Thank you.

Contact:Centre for Virtual Patients

University Hospital Heidelberghttp://campusvirtualpatients.com

Any questions?