1. XDS.c Common SOAP interface to Clinical Sources Brief Profile Proposal for 2008/09 presented to the IT Infrastructure Planning Committee Alean Kirnak & Joe Natoli October 1, 2008

2. IT Infrastructure Planning Committee The Problem What problem is this profile proposal hoping to address?What problem is this profile proposal hoping to address? –Providing a common, yet simple service interface on top of clinical applications which support interoperability across a network in service bus oriented deployment architectures Identify any existing IHE profile gaps/overlaps that this proposal will improve uponIdentify any existing IHE profile gaps/overlaps that this proposal will improve upon –XDS & XDR What is the market readiness for this IHE profile proposal?What is the market readiness for this IHE profile proposal? –Most large scale health integration networks are implementing service oriented architectures to scale at a reasonable cost –Flexibility in deployment models with common service interfaces is a emerging pattern What is the risk of this proposal not being undertaken this cycle?What is the risk of this proposal not being undertaken this cycle? –Every region/country defines its own solution. These custom built solutions are more expensive and cannot be tested at connectathons. This results in higher cost for all countries, who must pay for a one-of-a-kind solution and less reliable solutions, since they cannot be tested a connectathons.

3. IT Infrastructure Planning Committee Use Case Large scale HIN / HIE with >20-50 or so end pointsLarge scale HIN / HIE with >20-50 or so end points To meet cost objectives, reliability and scalability objectives where central broker or point to point architecture does not meet needsTo meet cost objectives, reliability and scalability objectives where central broker or point to point architecture does not meet needs –Implement a data-dial tone network across loosely coupled interoperating units of data sources and consumers –Provide common standards and approaches to exposing what functionality is available and how to access it via a service bus network XDR XDS.a/b XDS.c Each node of service network exists as a standardized SOAP interface describing data semantics and common operations A single application or data store can expose one or many service interfaces supporting each needed data representation

4. IT Infrastructure Planning Committee Proposed Standards & Systems What standards and/or systems should be considered in addressing this proposal?What standards and/or systems should be considered in addressing this proposal? –HL7 V2 data –HL7 V3 data, including CDA and CCD documents –Entity Identification Service Functional Model from HSSP –Retrieve, Locate, and Update Service from HSSP

5. IT Infrastructure Planning Committee Discussion What level of effort do you foresee in developing this profile?What level of effort do you foresee in developing this profile? –Medium Is there someone who is willing to act as profile editor? Please provide the name, organization, emailIs there someone who is willing to act as profile editor? Please provide the name, organization, email –Alean Kirnak, Software Partners, akirnak@swpartners.com –Joe Natoli, Intel Corporation, joseph.d.natoli@intel.com