2007 Brief Profile Proposal: IHE XDS Publish/Subscribe Profile
| The current published version of an ITI White Paper on this topic can be found at the IHE web site. The general ITI Publish Subscribe wiki page contains the most up-to-date information on this topic. |
1. Proposed Workitem: XDS Publish/Subscribe
- 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
The IHE XDS profiles require Document Consumers to constantly poll the Document Registry for new documents or updates to existing documents in cases when there is an expectation that additional documents may become available after an initial query. In many such cases a publish/subscribe method of receiving new information for patients of interest. In addition, the NAV profile assumes some kind of subscription method. Providing a consistent pub/sub framework will benefit various use cases where constant polling is not feasible.
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.