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

From IHE Wiki
Jump to navigation Jump to search
(New page: ==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...)
 
Line 11: Line 11:
 
==2. The Problem==
 
==2. The Problem==
  
−
''<Summarize the integration problem. What doesn’t work, or what needs to work.>''
+
XDS.b and XDS-I.b provide the framework and solution for cross-enterprise image exchange. 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==
  
−
''<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>''
+
Use Case
−
 
 
−
==3. Key Use Case==
 
  
−
''<Describe a short use case scenario from the user perspective.  The use case should demonstrate the integration/workflow problem.>''
+
An image 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 intitiating gateway.  The manifest entry is agrigated and forwarded on to the Image Document Consumer whom requested the information.  The Image document Source requests the image manifest from the initiating gateway.  The initiating Gateway communicates with the responding Gateway to retrieve the manifest and routed back to the Image Dodument Consumer via the Intitiating Gateway.  The image document source 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 Image Document Consumer and forwards on to the Image Document Consumer via the Initiating Image Gateway.
  
−
''<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.>''
+
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==
 
==4. Standards and Systems==
  
−
''<List existing systems that are/could be involved in the problem/solution.>''
+
XDS.b
  
−
''<If known, list standards which might be relevant to the solution>''
+
XDS-I.b
  
−
==5. Discussion==
+
XCA
  
−
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''
+
Image Exchange Systems, PACS, EMRs, RISs
−
:''<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?>''
 
  
 +
==5. Discussion==
  
−
''<This is the brief proposal.  Try to keep it to 1 or at most 2 pages>''
+
:IHE is the logical choice for developing a standards-based approach to cross-community Image Exchange.  The alternative is proprietary methods.
−
 
+
:  The IHE Technical approach would be an extension or adaptation of the existing Cross-Community Access (XCA) protocol defined in ITI.
 +
: The primary risk is that the behaviour would need to be constrained to leverage the existing protocol defined in XDS.b, XCA and XDS-I.b with the extensions needed to provide cross-community access of images in this profile.
  
−
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]
+
extend in the same framework as the XDS-I.b framework has the Image access XDS.b/XCA framework
 +
''<What are some of the risks or open issues to be addressed?>''

Revision as of 14:07, 13 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

XDS.b and XDS-I.b provide the framework and solution for cross-enterprise image exchange. 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

An image 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 intitiating gateway. The manifest entry is agrigated and forwarded on to the Image Document Consumer whom requested the information. The Image document Source requests the image manifest from the initiating gateway. The initiating Gateway communicates with the responding Gateway to retrieve the manifest and routed back to the Image Dodument Consumer via the Intitiating Gateway. The image document source 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 Image Document Consumer and forwards on to the Image 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.
The IHE Technical approach would be an extension or adaptation of the existing Cross-Community Access (XCA) protocol defined in ITI.
The primary risk is that the behaviour would need to be constrained to leverage the existing protocol defined in XDS.b, XCA and XDS-I.b with the extensions needed to provide cross-community access of images in this profile.

extend in the same framework as the XDS-I.b framework has the Image access XDS.b/XCA framework <What are some of the risks or open issues to be addressed?>

Retrieved from "http://wiki.ihe.net/index.php?title=Cross-Community_Access_-_Images_(XCA-I)&oldid=44651"