ITI Publish/Subscribe Infrastructure Profile Proposal for 2008/09 presented to the IT Infrastructure Technical Committee Vassil Peytchev November 18, 2008

IT Infrastructure Planning Committee 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 necessaryThis 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:This is continuation of the work published as a white paper during the last cycle, available here: S-b_pub_sub_2008_08_22.pdf\ S-b_pub_sub_2008_08_22.pdf\ Eventing is the preferred method for environments with high-volume of transactions, such as public health surveillanceEventing 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.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.

IT Infrastructure Planning Committee Use Case 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.

IT Infrastructure Planning Committee Proposed Standards & Systems New Actors:New Actors: –Subscriber –Notification Broker –Notification Consumer –Publisher Standards under consideration:Standards under consideration: –OASIS Web Services Notification –XPath

IT Infrastructure Planning Committee Actors and Transactions Subscriber Notification Consumer Publisher Notification Broker

IT Infrastructure Planning Committee 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)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/subscribeHow to formally describe the process of binding other profiles to publish/subscribe The Notify transaction needs to be context-specificThe Notify transaction needs to be context-specific