®
MedBiquitous Virtual
Patient Standard:
A Technical
Overview
What are virtual patients?
“interactive computer programs that simulate
real life clinical scenarios and provide an
effective way for healthcare professionals to
not only learn about a wide range of clinical
topics, but to practice in a virtual and
therefore safe environment.”
®
MedBiquitous Virtual Patient
Standard (MVP)
• A technical specification for the exchange of
Virtual Patient activities across Virtual Patient
systems
Institution A
<XML>
Institution B
®
Does my VP System fit?
• Digital – XML
• Delivery
• Web-based
• Mobile
• Virtual worlds
• Navigation
• Linear
• A representation of
data
• Must be interpreted
by a runtime system
• Output: zip file of
XML documents and
media
• Branching
• Global
®
Current Limitations
• Does NOT encode artificial intelligence
algorithims
• Does NOT encode physiology engine rules
and models
®
The MVP Architecture
Virtual Patient
Data
Media
Resource
Data Availability
Model
Activity
Model
Player Functional Specification
®
Virtual Patient
Data
• Personal and clinical
data
• Similar to a clinical
chart
• May include references
to healthcare
terminologies
®
Media
Resource
• Images, animations,
videos, etc.
®
Data Availability
Model
• Aggregates virtual
patient data and media
resources for reference
in an activity
• Enables progressive
disclosure of virtual
patient data and media
resources
DAM
Part 1:
Patient History
Virtual
Patient data
Part 2:
Diagnostics
Media
Resources
Text
Interview
item
Diagnostic
test
®
Activity
Model
• Integrates data and
media into a cohesive
learning activity
• Node based
• Activity flow (node sections,
p 84; links, p 99)
Node 1:
Start
Node 2:
Option
1
Node 3:
Option
2
Node 4:
Option
3
Node 5:
Option
4
Node 5:
Option
6
• Counters (p 75, p 87)
• Timers (p 81)
• Rules (p 79)
®
®
/DataAvailabilityModel/DAMNode[@id=‘463']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘23']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘463']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘23']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘463']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘23']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘463']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘23']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘463']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘23']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘321']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘6']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘321']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘6']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘321']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘6']
</ItemPath>
/DataAvailabilityModel/DAMNode[@id=‘321']
<ItemPath>
/VirtualPatientData/VPDText[@id=‘6']
</ItemPath>
Next Steps
Read the specifications and samples in the
implementation toolkit: http://bit.ly/mbq_vp
Questions? Contact Valerie Smothers
[email protected]
®