|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| | provides document interchange (push) using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS Registry and Repositories. |
| __TOC__ | | __TOC__ |
|
| |
|
| | ==Formal Specification== |
|
| |
|
| ==Summary== | | ===[https://profiles.ihe.net/ITI/TF/Volume1/ch-15.html XDR (html) specification]=== |
| Cross-Enterprise Document Reliable Interchange (XDR) provides document interchange using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS Registry and Repositories.
| | * [https://profiles.ihe.net/ITI/TF/Volume1/ch-15.html Final Text] |
| | |
| ==Benefits==
| |
| XDR provides a reliable and automatic transfer of documents and metadata for one patient between EHR systems even in the absence of an XDS infrastructure.
| |
| | |
| ==Details==
| |
| XDR supports the reuse of the Provide and Register Set transaction-b with Web-Services as transport. Transfer is direct from source to recipient, no repository or registry actors are involved.
| |
| XDR is document format agnostic, supporting the same document content as XDS and XDM. Document content is described in XDS Document Content Profiles. Examples are XDS-MS, XD-LAB, XPHR, and XDS-SD.
| |
| XDR defines no new metadata or message formats. It leverages XDS metadata with emphasis on patient identification, document identification, description, and relationships.
| |
| | |
| ==Systems Affected==
| |
| Systems involved in this profile are:
| |
| * EHR, EMR, HIE, HIO
| |
| | |
| '''Actors & Transactions:'''
| |
| [[Image:XDR-Actor-Transaction.jpg]]
| |
| | |
| ==Specification==
| |
| | |
| '''Profile Status:''' [[Comments| Final Text]]
| |
| | |
| '''Documents:'''
| |
| [http://www.ihe.net/Technical_Framework/index.cfm#IT IHE IT Infrastructure Technical Framework Version 5 or later]
| |
| * Vol. 1 -
| |
| ** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=15_Cross_Enterprise_Document_Re Section 15],
| |
| ** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=Appendix_E__Cross_Profile_Consi Appendix E Cross Profile Considerations],
| |
| ** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=Appendix_J__Content_and_Format_ Appendix J Content and Format of XDS Documents],
| |
| ** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=Appendix_K__XDS_Concept_Details Appendix K XDS Concepts]
| |
| * [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2b.pdf#nameddest=3_41_Provide_and_Register_Docum Vol. 2b - Sections 3.41 Provide and Register Document Set]
| |
| * [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol3.pdf#nameddest=4_0_Metadata_used_in_Document_S Vol. 3 - Section 4.0 Metadata used in Document Sharing] | |
| | |
| '''CDA mapping to XDS Metadata:'''
| |
| :* [http://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_TF_Vol2.pdf#nameddest=4_1_1_XDSDocumentEntry_Metadata PCC TF-2:4.1.1]
| |
| | |
| | |
| '''Underlying Standards:'''
| |
| :* ebMS OASIS/ebXML Messaging Services Specifications v3.0
| |
| :* ebRIM OASIS/ebXML Registry Information Model v3.0
| |
| :* ebRS OASIS/ebXML Registry Services Specifications v3.0
| |
|
| |
|
| ==See Also== | | ==See Also== |
| Line 54: |
Line 18: |
| [[Category:ITI Profile]] | | [[Category:ITI Profile]] |
| [[Category:DocShare]] | | [[Category:DocShare]] |
| | |
| | Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]]. |
provides document interchange (push) using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS Registry and Repositories.
Formal Specification
See Also
Document Sharing
Related Profiles
This page is based on the Profile Template
Current: IT Infrastructure Technical Framework.