Difference between revisions of "Cross-Community Access for Imaging"
| Line 33: | Line 33: | ||
==Specification== | ==Specification== | ||
| − | '''Profile Status:''' [[Comments| | + | '''Profile Status:''' [[Comments| Trial Implementation]] |
| − | |||
'''Documents:''' | '''Documents:''' | ||
| − | |||
| − | |||
[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/ | + | 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:''' | ||
| − | |||
:* [http://dicom.nema.org DICOM] | :* [http://dicom.nema.org DICOM] | ||
| − | :* | + | :* ebRIM OASIS/ebXML Registry Information Model v3.0 |
| − | :* . | + | :* ebRS OASIS/ebXML Registry Services Specifications v3.0 |
==See Also== | ==See Also== | ||
Revision as of 10: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:
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.>
- 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.
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.>