Artemis Project A Semantic Web Service-based P2P Infrastructure for the Interoperability of Medical Information Systems (IST-1-002103-STP) Asuman Dogac COPRAS Kick-off Meeting, Oct. 14, 2004, Brussels 1/24 Challenges of Healthcare Informatics Most of the health information systems today are (cid:132) proprietary They often only serve one specific department within a (cid:132) healthcare institute To complicate the matters worse, a patient's health (cid:132) information may be spread out over a number of different institutes which do not interoperate This makes it very difficult for clinicians to capture a (cid:132) complete clinical history of a patient COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 2/24 Electronic Healthcare Record (EHR) Architectures The nice thing about standards is that there are so many to choose from ☺ „Candidates“ of EHR architectures: (cid:132) CEN ENV 13606 „EHR Communication“ (cid:137) Good Electronic Health Record (GEHR) (cid:137) OpenEHR (cid:137) CEN EN 13606 (draft) (cid:137) HL7 Clinical Document Architecture (cid:137) HL7 v2 Information Model (implicit) (cid:137) HL7 v3 Reference Information Model (draft) (cid:137) COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 3/24 Artemis Architecture The Artemis project addresses the interoperability (cid:132) problem in the healthcare domain where organisations have proprietary application systems to access data To exchange information in an interoperable manner, the (cid:132) medical institutes: Classify the Web services that they are providing through (cid:137) Service Functionality Ontologies Determine the semantics of Service Messages through Service (cid:137) Message Ontologies COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 4/24 Semantic Mediation: Ontology Mapping The differences between disparate Service Functionality (cid:132) and Service Message Ontologies will be resolved through Ontology Mapping Although we propose to develop ontologies based on the (cid:132) prominent healthcare standards, the ontologies we are proposing is just to facilitate ontology mediation It realistic to expect healthcare institutes to conform to (cid:132) one global ontology COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 5/24 What kind of Semantics? Service Functionality Semantics: (cid:132) HL7 Version 2.x has categorized the events in healthcare domain (cid:137) by considering service functionality which reflects the business logic in this domain This classification can be used as a basis for defining the service (cid:137) action semantics through a Service Functionality Ontology Service Message Semantics: (cid:132) Electronic healthcare record (EHR) based standards like HL7 (cid:137) CDA (Clinical Document Architecture), GOM (GEHR Object Model), and CEN TC251's ENV 13606 define meaningful components of EHR so that when transferred, the receiving party can understand the record content better The meaningful components defined by these standards can (cid:137) be used in developing service message ontologies COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 6/24 HL7 Version 2.x and Web Services The primary goal of HL7 is to provide standards for the exchange (cid:132) of data among healthcare computer applications An event in the healthcare world, called the trigger event, causes (cid:132) exchange of messages between a pair of applications When an event occurs in an HL7 compliant system, an HL7 (cid:132) message is prepared by collecting the necessary data from the underlying systems and it is passed to the requestor, usually as an EDI message Mapping HL7’s message based events directly into Web services (cid:132) may result in several inefficiencies COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 7/24 HL7 Version 2.x and Web Services The input and output messages defined for HL7 events are (cid:132) usually very complex containing innumerous segments of different types and optionality Furthermore, all the semantics about the business logic and (cid:132) the document structure are hard coded in the message This implies that, the party invoking the Web service must be (cid:132) HL7 compliant to make any sense of the content of the output parameter(s) returned by the service Furthermore, the information contained in an HL7 message may (cid:132) be coming from different systems either proprietary or complying to different standards Hence, in Web services terminology, HL7 events correspond to (cid:132) Composite services, whereas more elementary services are needed COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 8/24 An Example Service Functionality Ontology based on HL7 HealthCareServices PatientAdministration PatientCare PatientReferral Scheduling ObservationReporting PatientReferralRequest PatientInfoRequest CancelPatientReferral InsuranceInformation ClinicalInformation DemographicData GetClinicalInformation Properties of the serviceQuality location Generic Service Class COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 9/24 Service Messages A Web service in the healthcare domain usually accesses or (cid:132) updates a part of an electronic healthcare record, that is, parts of the EHR constitute the service parameters An electronic healthcare record may get very complex with data (cid:132) coming from diverse systems such as lab tests, diagnosis, prescription of drugs which may be in different formats Electronic healthcare record (EHR) based standards like HL7 (cid:132) CDA, GOM and CEN's ENV 13606 aim to facilitate the interoperability between Medical Information Systems These standards provide conceptual building blocks or (cid:132) meaningful components We propose to use these standards as a basis for Service (cid:132) Message Ontology COPRAS Kick-off Meeting Asuman Dogac Oct. 14, 2004, Brissels 10/24