14
September 2006 www.virtualpatients Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability of Virtual Patients Findings from the eViP project

September 2006 Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

Embed Size (px)

Citation preview

Page 1: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006www.virtualpatients.eu

Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J

Enabling Interoperability, Accessibility and Reusability of Virtual Patients Findings from the eViP project

Page 2: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

eViPSeptember 2006

Aims of the presentation

• What eViP is about• The goals of this sub-project• How we achieved our goals• Results• Challenges• Recommendations

www.virtualpatients.eu

Page 3: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

eViPSeptember 2006

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 outcomeCreate a bank of repurposed and enriched multilingual and multicultural virtual patients and share them

www.virtualpatients.eu

Page 4: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

eViPSeptember 2006

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

www.virtualpatients.eu

Page 5: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006

Participating systems

www.virtualpatients.eu

CASUSCASUS

CampusCampus

Web-SPWeb-SP

OpenLabyrinthOpenLabyrinth

Page 6: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

eViPSeptember 2006

Result: eViP application profile

www.virtualpatients.eu

The aim of application profiles is the selection and re-use of existing elements to tailor to the needs of a given group of users.

• MedBiquitous Virtual Patient 0.48• MedBiquitous Healthcare Learning Object Metadata (Healthcare LOM)• SCORM packages • Conformance testing suite

What does this mean???

Page 7: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006

The same VP in different systems

www.virtualpatients.eu

Page 8: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006

Challenge 1

www.virtualpatients.eu

• Importing a branched VP to linear VP system

NodeNode

NodeNode NodeNode

NodeNode NodeNodeNodeNode

NodeNode

NodeNode

NodeNode

NodeNode

NodeNode

NodeNode

Branched VP Linear VP

NodeNode

Page 9: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006

Challenge 1 - Implications

www.virtualpatients.eu

• Import all branches• Put information about (best) next node(s), end nodes(s) and

start node into imported VP

• Has to be done manually

Page 10: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006

Challenge 2

www.virtualpatients.eu

• Importing a linear VP to a branched VP system

NodeNode

NodeNode NodeNode

NodeNode NodeNodeNodeNode

NodeNode

NodeNode

NodeNode

NodeNode

NodeNode

NodeNode

Branched VP Linear VP

NodeNode

Page 11: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006

Challenge 3

www.virtualpatients.eu

PhysicalExam

InterviewItem

Diagnosis

Therapy

"Structured" system

Text Element

"Non-Structured" system

Text Element

Text Element

Text Element

???

• Importing and exporting from "structured" to "unstructured"

Page 12: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

eViPSeptember 2006

How the VP systems use different parts of the specifications

www.virtualpatients.eu

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

Page 13: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006

Best practice guidelines

www.virtualpatients.eu

• 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

Page 14: September 2006  Zary N, Hege I, Heid J, Kononowicz A, Woodham L, Donkers J Enabling Interoperability, Accessibility and Reusability

September 2006www.virtualpatients.eu

Thank you!

Nabil [email protected]

More information: www.virtualpatients.eu