Difference between revisions of "2008 Brief Profile Proposal: IHE ITI Publish/Subscribe Profile"
| Line 15: | Line 15: | ||
==2. The Problem== | ==2. The Problem== | ||
| − | + | Event driven information exchange patterns dominate the data interchange in most healthcare settings. For example, most HL7 version 2.x interfaces send messages based on events within the sender's system. Most current IHE profiles assume either static, out-of-band determination of the senders and receivers of event driven information exchange, or describe query-response patterns. There is a need for a profiled dynamic infrastructure for event-driven information exchange patterns within IHE. This profile will provide the underlying infrastructure for publish/subscribe interactions, which other profiles and domains can reuse within their specifications. | |
==3. Key Use Case== | ==3. Key Use Case== | ||
Revision as of 13:47, 25 September 2008
| This proposal is based on the Publish/Subscribe Infrastructure for XDS.b white paper. |
1. Proposed Workitem: ITI Publish/Subscribe Infrastructure
- Proposal Editor: Vassil Peytchev
- Editor: Vassil Peytchev
- Date: N/A (Wiki keeps history)
- Version: N/A (Wiki keeps history)
- Domain: IT Infrastructure
2. The Problem
Event driven information exchange patterns dominate the data interchange in most healthcare settings. For example, most HL7 version 2.x interfaces send messages based on events within the sender's system. Most current IHE profiles assume either static, out-of-band determination of the senders and receivers of event driven information exchange, or describe query-response patterns. There is a need for a profiled dynamic infrastructure for event-driven information exchange patterns within IHE. This profile will provide the underlying infrastructure for publish/subscribe interactions, which other profiles and domains can reuse within their specifications.
3. Key Use Case
How it works with current XDS
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, see proposal for referral orders), the specialist queries the document registry, and received the referral summary. Noticing the outstanding radiology and lab orders, the specialist, or the staff at the specialist's practice, will have to periodically query the registry to retrieve the radiology and lab reports.
How it should work
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, see proposal for referral orders), 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, either a notification is sent to the specialist's system, or an online XDR transaction is exectuted.
4. Standards & Systems
Document Source, Document Consumer, Document Repository, Document Registry
ebXML Registry, existing XDS transactions
5. Discussion
Why would IHE be a good venue to solve the problem and what you think should IHE do to solve it.
This is a natural extension to the XDS-b profile (possibly including asynchronous transactions).
What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?
A new profile, derived from XDS-b and XDR
What are some of the risks or open issues to be addressed?
There are additional use cases where publish/subscribe may be useful. There is likely a need for PCC (or several committees) to define appropriate topics for healthcare-specific publish/subscribe infrastructure.