Difference between revisions of "Cross-Community Access - Images (XCA-I)"

Latest revision as of 02:00, 21 September 2010

1. Proposed Workitem:Cross Community Access - Images (XCA-I)

Proposal Editor: Chris Lindop'
Editor: Chris Lindop
Date: N/A (Wiki keeps history)
Version: N/A (Wiki keeps history)
Domain: Radiology

2. The Problem

There is no solution for exchanging images between facilities that are not in the same affinity domain.

XDS.b and XDS-I.b provide the framework and solution for cross-enterprise image exchange within an affinity domain. A registry, a set of repositories and a set of Image Document Source actors form the basis of the imaging exchange in a comunity.

For cross-community imaging exchange, XCA provides the frame work for exchanging the manifest, but not images.

This proposal is to extend the imaging exchange framework to include the exchange of images between communities.

3. Key Use Case

Use Case (how it should work)

An Imaging Document Consumer requests images for a particular patient from an XCA Initiating Gateway.
The Initiating Gateway communicates with it's known Responding Gateways with the request.
A Responding Gateway provides a registry entry for an Image Manifest in it's community to the Initiating Gateway.
The manifest entry is agreggated and forwarded on to the Imaging Document Consumer whom requested the information.
The Imaging Document Consumer requests the image manifest from the Initiating Gateway.
The Initiating Gateway communicates with the Responding Gateway to retrieve the manifest and route it back to the Imaging Document Consumer via the Initiating Gateway.
The Imaging Document Consumer would like to retrieve the images from the system. A request is made to an Initiating Image Gateway and forwarded on to the Responding Image Gateway which retrieves the images from the Imaging Document Source and forwards on to the Imaging Document Consumer via the Initiating Image Gateway.

There currently is no concept of an Image Gateway. The proposal is to create this Actor pair to resolve the gap.

4. Standards and Systems

XDS.b

XDS-I.b

XCA

Image Exchange Systems, PACS, EMRs, RISs

5. Discussion

IHE is the logical choice for developing a standards-based approach to cross-community Image Exchange. The alternative is proprietary methods or people figuring it out themselves.

The IHE Technical approach would be an extension or adaptation of the existing Cross-Community Access (XCA) protocol defined in ITI.

Risks?

Question:

Has XCA been sufficiently widely adopted for us to leverage?
- It is a new profile in ITI. There is global interest in leveraging XCA for linking communities. There is no competitor technology. Already we see some uptake in Europe. Canada is using this profile to link the regions. There may be some hold back in the USA due to a lack of National strategy.
Has XDS-I been sufficiently widely deployed for us to leverage?
- Yes. It is the standard for imaging exchange throughout the world. It is being deployed Nationally in Canada, regionally in various location throughout Europe and USA.

@@ Line 1: / Line 1: @@
-==1. Proposed Workitem: =Cross Community Access - Images (XCA-I)=
+==1. Proposed Workitem:Cross Community Access - Images (XCA-I)==
 * Proposal Editor: ''Chris Lindop'
@@ Line 11: / Line 11: @@
 ==2. The Problem==
-''<Summarize the integration problem. What doesn’t work, or what needs to work.>''
+There is no solution for exchanging images between facilities that are not in the same affinity domain.
+XDS.b and XDS-I.b provide the framework and solution for cross-enterprise image exchange within an affinity domain.  A registry, a set of repositories and a set of Image Document Source actors form the basis of the imaging exchange in a comunity.
-''<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>''
+For cross-community imaging exchange, XCA provides the frame work for exchanging the manifest, but not images.
+This proposal is to extend the imaging exchange framework to include the exchange of images between communities.
 ==3. Key Use Case==
-''<Describe a short use case scenario from the user perspective.  The use case should demonstrate the integration/workflow problem.>''
+Use Case (how it should work)
-''<Feel free to add a second use case scenario demonstrating how it “should” work.  Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>''
+* An Imaging Document Consumer requests images for a particular patient from an XCA Initiating Gateway.
+* The Initiating Gateway communicates with it's known Responding Gateways with the request.
+* A Responding Gateway provides a registry entry for an Image Manifest in it's community to the Initiating Gateway.
+* The manifest entry is agreggated and forwarded on to the Imaging Document Consumer whom requested the information.
+* The Imaging Document Consumer requests the image manifest from the Initiating Gateway.
+* The Initiating Gateway communicates with the Responding Gateway to retrieve the manifest and route it back to the Imaging Document Consumer via the Initiating Gateway.
+* The Imaging Document Consumer would like to retrieve the images from the system.  A request is made to an '''Initiating Image Gateway''' and forwarded on to the '''Responding Image Gateway''' which retrieves the images from the Imaging Document Source and forwards on to the Imaging Document Consumer via the Initiating Image Gateway.
+There currently is no concept of an Image Gateway.   The proposal is to create this Actor pair to resolve the gap.
 ==4. Standards and Systems==
-''<List existing systems that are/could be involved in the problem/solution.>''
+XDS.b
+XDS-I.b
+XCA
-''<If known, list standards which might be relevant to the solution>''
+Image Exchange Systems, PACS, EMRs, RISs
 ==5. Discussion==
-''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''
+IHE is the logical choice for developing a standards-based approach to cross-community Image Exchange.  The alternative is proprietary methods or people figuring it out themselves.
-:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''
-:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''
-:''<What are some of the risks or open issues to be addressed?>''
-''<This is the brief proposal.  Try to keep it to 1 or at most 2 pages>''
+The IHE Technical approach would be an extension or adaptation of the existing Cross-Community Access (XCA) protocol defined in ITI.
+Risks?
-''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]
+Question:
+* Has XCA been sufficiently widely adopted for us to leverage?
+** It is a new profile in ITI.  There is global interest in leveraging XCA for linking communities.  There is no competitor technology.  Already we see some uptake in Europe.  Canada is using this profile to link the regions.  There may be some hold back in the USA due to a lack of National strategy.
+* Has XDS-I been sufficiently widely deployed for us to leverage?
+** Yes. It is the standard for imaging exchange throughout the world.  It is being deployed Nationally in Canada, regionally in various location throughout Europe and USA.