Difference between revisions of "Cross-Community Document Reliable Interchange (XCDR)"

From IHE Wiki
Jump to navigation Jump to search
(Starting creation)
(Complete page creation)
Line 7: Line 7:
 
The Cross-Community Document Reliable Interchange (XCDR) Profile provides the capability to send a set of documents in a Cross-Community environment. The XCDR Profile specifies the transaction to push documents from an Initiating Gateway of a source Community to the Responding Gateway of a target Community. XCDR extends the deployment of a community organized around an XDS Document Registry and Repository(s) by allowing both Document Source Actors within this XDS based community, and also those in different communities to act as a source of documents.
 
The Cross-Community Document Reliable Interchange (XCDR) Profile provides the capability to send a set of documents in a Cross-Community environment. The XCDR Profile specifies the transaction to push documents from an Initiating Gateway of a source Community to the Responding Gateway of a target Community. XCDR extends the deployment of a community organized around an XDS Document Registry and Repository(s) by allowing both Document Source Actors within this XDS based community, and also those in different communities to act as a source of documents.
  
−
[[Image:XCDR-Simple.png]]
+
[[Image:XCDR-Simple.png|500x500px]]
  
  
Line 29: Line 29:
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
−
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[Image:XCDR Actor Diagram.png|500x500px]]
  
 
==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:'''  
Line 40: Line 40:
 
''<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.>''
 
''<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/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_XCDR.pdf XCDR Profile]
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
−
:* [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_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''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]
+
:* [https://docs.oasis-open.org/regrep/v3.0/specs/regrep-rim-3.0-os.pdf OASIS/ebXML Registry Information Model v3.0]
−
:* [http://www.hl7.org HL7]
+
:* [http://docs.oasis-open.org/regrep/regrep-rs/v3.0/regrep-rs-3.0-os.pdf OASIS/ebXML Registry Services Specifications v3.0]
−
:* ...
+
:* [http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/cs02/ebms_core-3.0-spec-cs-02.pdf OASIS/ebXML Messaging Services Specifications v3.0]
  
 
==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.>''
 
−
 
  
 
'''Related Profiles'''
 
'''Related Profiles'''
Line 61: Line 55:
 
''<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.>''
 
''<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.''
+
* ''[[Cross-Community_Access]] [XCA] Basis for Cross Community data interchange.''
−
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
+
* ''[[Cross-enterprise Document Reliable Interchange]] [XDR] PRofile that describes basic push between communities.''
−
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
+
* ''[[Cross-enterprise Document Sharing]] [XDS] facilitates the registration, distribution and access across health enterprises of patient electronic health records.''
−
* ''[[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]]
 
This page is based on the [[Profile Overview Template]]
−
 
−
 
−
 
−
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
 

Revision as of 14:24, 16 February 2016

XCDR introduces the capability to send documents from a source Community with sufficient information to direct the documents through gateways to a designated target Community.


Summary

The Cross-Community Document Reliable Interchange (XCDR) Profile provides the capability to send a set of documents in a Cross-Community environment. The XCDR Profile specifies the transaction to push documents from an Initiating Gateway of a source Community to the Responding Gateway of a target Community. XCDR extends the deployment of a community organized around an XDS Document Registry and Repository(s) by allowing both Document Source Actors within this XDS based community, and also those in different communities to act as a source of documents.

XCDR-Simple.png


Benefits

The XCDR Profile:

  • has similar deployment characteristics to the IHE Cross-Community Access (XCA) Profile and is easily combined and deployed in an environment that is already using XCA.
  • fully specifies the combined use with the IHE Cross-Enterprise Document Reliable Interchange (XDR) Profile, enabling XDR Document Source and Document Recipient Actors in separate communities to become connected. End-to-end acknowledgement is assured. A Document Source receives acknowledgment only when the Document Recipient in a remote community has received the document.
  • extends the deployment of a community organized around an XDS Document Registry and Repository(s) by allowing both Document Sources Actors within this XDS based community, and also those in different communities to act as a source of documents.

Details

XCDR supports the exchange of documents within a Cross-Community environment with Web-Services as transport. The routing of the document set relies on an Initiating Gateway in the source community and Responding Gateway(s) in one or more remote communities.


Systems Affected

This profile would be implemented in systems using XCA gateways.


Actors & Transactions:

XCDR Actor Diagram.png

Specification

Profile Status: Trial Implementation


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.>

XCDR Profile

Underlying Standards:


See Also

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.>

This page is based on the Profile Overview Template

Retrieved from "http://wiki.ihe.net/index.php?title=Cross-Community_Document_Reliable_Interchange_(XCDR)&oldid=92563"