1 / 6

ITI Publish/Subscribe Infrastructure

This proposal outlines a web-services based publish/subscribe profile, essential for enabling event-based transactions across various domains. It is crucial to address high-volume transaction environments, like public health surveillance. Neglecting this proposal could impact other IHE domains. The use case scenario illustrates the process flow in a healthcare setting, demonstrating the significance of the proposed standards and systems. The document also highlights open issues requiring further clarification for smooth implementation.

claudetaylor
Download Presentation

ITI Publish/Subscribe Infrastructure

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. ITI Publish/Subscribe Infrastructure Profile Proposal for 2008/09 presented to the IT Infrastructure Technical Committee Vassil Peytchev November 18, 2008

  2. The Problem • This proposal is for a general web-services based publish/subscribe profile, which can enable other profiles and domains top use event-based transactions when necessary • This is continuation of the work published as a white paper during the last cycle, available here: http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Whitepaper_XDS-b_pub_sub_2008_08_22.pdf\ • “Eventing” is the preferred method for environments with high-volume of transactions, such as public health surveillance • If the proposal is not undertaken in this cycle, the work of other IHE domains may be negatively affected, and ad-hoc solution used instead.

  3. Use Case • Use case: • Person A visits his PCP with week-old trauma to his foot. • Concerned about possible fracture and infection, the PCP orders x-ray and a lab panel, and refers him to a specialist. • Upon receiving the referral (which is out of scope here), the specialist queries the document registry, and received the referral summary. • The specialist also subscribes for any additional information about the patient. As the radiology and lab reports are submitted to the registry, a notification is sent to the specialist's system, and an XDS document retrieve transaction is executed.

  4. Proposed Standards & Systems • New Actors: • Subscriber • Notification Broker • Notification Consumer • Publisher • Standards under consideration: • OASIS Web Services Notification • XPath

  5. Actors and Transactions Subscriber Publisher Notification Broker Notification Consumer

  6. Open Issues • This is a meta-profile, similar to ATNA. This probably means that there is a need for additional non-normative explanatory materials (e.g. an implementation guide on the Wiki) • How to formally describe the process of binding other profiles to publish/subscribe • The Notify transaction needs to be context-specific

More Related