Cross-Community Access for Imaging: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Lindop (talk | contribs)
 
(8 intermediate revisions by 4 users not shown)
Line 7: Line 7:


==Benefits==
==Benefits==
* Fully compatible profile with XCA as an extension.
* Image access between Communities
**  XCA/XCA-I supports peer-to-peer querying with other communities
* Common health information infrastructure with non-imaging data
**  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==
==Details==
Line 30: Line 28:


[[File:XCA-I.jpg]]
[[File:XCA-I.jpg]]
The shaded actors are NOT included in this profile but are shown to illustrate the full set of actors that play a role other endpoint of transactions that ARE part of the profile (e.g., the Document Registry Actor is an endpoint for the Registry Stored Query Transaction).


==Specification==
==Specification==


'''Profile Status:''' [[Comments| Trial Implementation]]   
'''Profile Status: ''' [https://wiki.ihe.net/index.php/Comments#Phases_of_Development Final Text]   


'''Documents:'''  
'''Documents:'''  


[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
:* [https://profiles.ihe.net/RAD/ IHE Radiology Technical Framework]
Su
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Suppl_XCA-I_Rev1-1_TI_2011-05-17.pdf
Cross-Community Access for Imaging (XCA-I)]


'''Underlying Standards:'''
'''Underlying Standards:'''
Line 50: Line 47:
==See Also==
==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.>''
* [[Document Sharing]]
 


'''Related Profiles'''
'''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.>''
* [XCA] [[Cross-Community Access]] allows to query and retrieve patient electronic health records, including the reports and image manifests held by other communities.  
 
* [XDS] [[Cross Enterprise Document Sharing]] share and discover electronic health record documents between healthcare enterprises, physician offices, clinics, acute care in-patient facilities and personal health records within the community.
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''


* [XDS-I.b] [[Cross-enterprise Document Sharing for Imaging]].b Update extends XDS to share images, diagnostic reports and related information across a group of care sites.


'''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]]


[[Category:Profiles]]
[[Category:Profiles]]
 
[[Category:DocShare]]
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
[[Category:RAD Profile]]
[[Category:DICOM]]

Latest revision as of 08:53, 26 June 2024

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

  • Image access between Communities
  • Common health information infrastructure with non-imaging data

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:

The shaded actors are NOT included in this profile but are shown to illustrate the full set of actors that play a role other endpoint of transactions that ARE part of the profile (e.g., the Document Registry Actor is an endpoint for the Registry Stored Query Transaction).

Specification

Profile Status: Final Text

Documents:

Underlying Standards:

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

See Also

Related Profiles

  • [XCA] Cross-Community Access allows to query and retrieve patient electronic health records, including the reports and image manifests held by other communities.
  • [XDS] Cross Enterprise Document Sharing share and discover electronic health record documents between healthcare enterprises, physician offices, clinics, acute care in-patient facilities and personal health records within the community.