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

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

Embed Size (px)

Citation preview

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

““XDS.c” XDS.c” Common SOAP interface to Clinical SourcesCommon SOAP interface to Clinical Sources

Brief Profile Proposal for 2008/09Brief Profile Proposal for 2008/09presented to thepresented to the

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Alean Kirnak & Joe NatoliAlean Kirnak & Joe NatoliOctober 1, 2008October 1, 2008

Page 2: XDS.c Common SOAP interface to Clinical Sources Brief Profile Proposal for 2008/09 presented to the IT Infrastructure Planning Committee Alean Kirnak &

IT Infrastructure Planning CommitteeIT 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 Providing a common, yet simple service interface on top of clinical

applications which support interoperability across a network in service bus applications which support interoperability across a network in service bus oriented deployment architecturesoriented deployment architectures

• Identify any existing IHE profile gaps/overlaps that this proposal will Identify any existing IHE profile gaps/overlaps that this proposal will improve uponimprove upon– XDS & XDRXDS & 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 Most large scale health integration networks are implementing service

oriented architectures to scale at a reasonable cost oriented architectures to scale at a reasonable cost – Flexibility in deployment models with common service interfaces is a Flexibility in deployment models with common service interfaces is a

emerging patternemerging 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 Every region/country defines its own solution. These custom built solutions are more expensive and cannot be tested at connectathons. This results in 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 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.less reliable solutions, since they cannot be tested a connectathons.

Page 3: XDS.c Common SOAP interface to Clinical Sources Brief Profile Proposal for 2008/09 presented to the IT Infrastructure Planning Committee Alean Kirnak &

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Use Case

• Large scale HIN / HIE with >20-50 or so end points Large scale HIN / HIE with >20-50 or so end points

• To meet cost objectives, reliability and scalability objectives To meet cost objectives, reliability and scalability objectives where central broker or point to point architecture does not where central broker or point to point architecture does not meet needsmeet needs– Implement a “data-dial” tone network across loosely coupled Implement a “data-dial” tone network across loosely coupled

interoperating units of data sources and consumersinteroperating units of data sources and consumers– Provide common standards and approaches to exposing what Provide common standards and approaches to exposing what

functionality is available and how to access it via a service bus functionality is available and how to access it via a service bus networknetwork

XDR

XDS.a/b

“XDS.c”

Each node of service networkexists as a standardized SOAPinterface describing data semanticsand common operations

A single application or datastore can expose one or manyservice interfaces supportingeach needed data representation

Page 4: XDS.c Common SOAP interface to Clinical Sources Brief Profile Proposal for 2008/09 presented to the IT Infrastructure Planning Committee Alean Kirnak &

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Proposed Standards & Systems

• What standards and/or systems should be considered in What standards and/or systems should be considered in addressing this proposal?addressing this proposal?– HL7 V2 data HL7 V2 data – HL7 V3 data, including CDA and CCD documentsHL7 V3 data, including CDA and CCD documents– Entity Identification Service Functional Model from HSSPEntity Identification Service Functional Model from HSSP– Retrieve, Locate, and Update Service from HSSPRetrieve, Locate, and Update Service from HSSP

Page 5: XDS.c Common SOAP interface to Clinical Sources Brief Profile Proposal for 2008/09 presented to the IT Infrastructure Planning Committee Alean Kirnak &

IT Infrastructure Planning CommitteeIT Infrastructure Planning Committee

Discussion

• What level of effort do you foresee in developing this What level of effort do you foresee in developing this profile?profile?– MediumMedium

• Is there someone who is willing to act as profile editor? Is there someone who is willing to act as profile editor? Please provide the name, organization, emailPlease provide the name, organization, email– Alean Kirnak, Software Partners, [email protected] Kirnak, Software Partners, [email protected]– Joe Natoli, Intel Corporation, [email protected] Natoli, Intel Corporation, [email protected]