Difference between revisions of "Cross-Community Access for Imaging"

From IHE Wiki
Jump to navigation Jump to search
Line 33: Line 33:
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
  
 
'''Documents:'''  
 
'''Documents:'''  
 
''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
 
  
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
+
Su
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Suppl_XCA-I_Rev1-1_TI_2011-05-17.pdf
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
+
Cross-Community Access for Imaging (XCA-I)]
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
''<list all the standards on which the profile is based; if possible with links to sources>''
 
 
:* [http://dicom.nema.org DICOM]
 
:* [http://dicom.nema.org DICOM]
:* [http://www.hl7.org HL7]
+
:* ebRIM OASIS/ebXML Registry Information Model v3.0
:* ...
+
:* ebRS OASIS/ebXML Registry Services Specifications v3.0
  
 
==See Also==
 
==See Also==

Revision as of 09:00, 29 May 2013

Summary

Cross-Community Access for Imaging(XCA) - Supports the means to query and retrieve patient relevant medical imaging data held by other communities.

The XCA-I Profile extends the IT Infrastructure XCA Profile. XCA provides access to all medical data including diagnostic reports and imaging manifests. XCA-I provides access to the images referenced in the imaging manifests.

Benefits

  • Fully compatible profile with XCA as an extension.
    • XCA/XCA-I supports peer-to-peer querying with other communities
    • XCA/XCA-I supports peer-to-peer retrieve with other communities
    • XCA-I supports peer-to-peer retrieve of DICOM instances hosted by other communities

Details

The Cross-Community Access for Imaging profile supports the means to query and retrieve patient relevant medical image data held by other communities. A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information via an established mechanism. Facilities/enterprises may host any type of healthcare application such as EHR, PHR, etc.

Such communities may be XDS Affinity Domains which define image sharing using the XDS-I profile. This profile addresses sharing between such communities.

The XCA-I Profile extends the IT Infrastructure XCA Profile for Imaging. XCA provides access to Diagnostic reports and Imaging Manifests. XCA-I provides access to the imaging objects referenced in the Manifests.

Systems Affected

Systems involved in this profile include:

  • PACS or RIS systems may store, manage, and display imaging documents.
  • EMR's and other patient management systems which will access and display imaging documents.
  • HIE's, Image Exchange Systems, and VNA's which store, manage and display imaging documents for multiple systems.

Actors & Transactions:

XCA-I.jpg

Specification

Profile Status: Trial Implementation

Documents:

IHE Radiology Technical Framework: Su

Cross-Community Access for Imaging (XCA-I)]

Underlying Standards:

  • DICOM
  • ebRIM OASIS/ebXML Registry Information Model v3.0
  • ebRS OASIS/ebXML Registry Services Specifications v3.0

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>


Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>


Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >


This page is based on the Profile Overview Template

<Delete this Category Templates line since your Profile page is no longer a template.>