1 / 5

“XDS.c” Common SOAP interface to Clinical Sources

“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. The Problem. What problem is this profile proposal hoping to address?

ike
Download Presentation

“XDS.c” Common SOAP interface to Clinical Sources

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. The Problem • 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 upon • XDS & XDR • 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? • 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. Use Case • Large 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 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 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 XDS.a/b “XDS.c”

  4. Proposed Standards & Systems • 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. Discussion • 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, email • Alean Kirnak, Software Partners, akirnak@swpartners.com • Joe Natoli, Intel Corporation, joseph.d.natoli@intel.com

More Related