220 likes | 333 Views
Using the MedBiq VP Data Standard: A Reality Check. James B. McGee, Dmitriy Babichenko, Chris Toth, Jane Alexander, Teppituk Krinchai. May 2011. Laboratory for Educational Technology University of Pittsburgh School of Medicine. Disclosure. Chair, Scientific Advisory Board & equity holder
E N D
Using the MedBiq VP Data Standard: A Reality Check James B. McGee, Dmitriy Babichenko, Chris Toth, Jane Alexander, Teppituk Krinchai May 2011 Laboratory for Educational TechnologyUniversity of Pittsburgh School of Medicine
Disclosure • Chair, Scientific Advisory Board & equity holder • Decision Simulation, LLC - licensee of virtual patient simulation technology from the University of Pittsburgh
vpSim Experience:Export & Import with the MedBiq VP spec • export is hard – import is (very) hard • > 5000 lines of code • vpSim Player application is 1800 lines • THREE steps: • 1) export to valid XML and content package • 2) import back into vpSim or “round-trip” • 3) import others’ cases into vpSim
The Reality Test • selected 26 representative cases from eVip Referatory • www.virtualpatients.eu • criteria: technical import (y/n), text, media, questions, logic • examples…
Observations • everyone likes “free” cases • over 550 cases on DecisionSim, none were imported • Web-SP has imported all CASUS cases • better if similar case design (linear vs. branching) • import/export technically challenging • why not just cut & paste from browser window? • many VPs are not MedBiq VPs – DxR, MedU (CLIPP)
thankYou vpSim vpSim.pitt.edu Lab for Educational Technology let.pitt.edu JB McGee mcgee@medschool.pitt.edu | +1-412-648-9679
The way forward… • sharing within VP families • linear <-----> linearbranched <-----> branched • community of VP implementers and users • mash-ups, crowd sourcing…Wiki Cases? • mix of prepared, instant and from scratch virtual patient network