Difference between revisions of "Cross-Enterprise Document Sharing"

From IHE Wiki
Jump to navigation Jump to search
(34 intermediate revisions by 10 users not shown)
Line 1: Line 1:
−
The Cross-Enterprise Document Sharing IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records.
+
'''Cross-Enterprise Document Sharing (XDS)''' is an interoperability profile that facilitates the registration, distribution and access across health enterprises of patient electronic health records.
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
−
Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.  This is managed through federated document repositories and a document registry to create a longitudinal record of information about a patient within a given clinical affinity domain. These are distinct entities with separate responsibilities:
+
Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility and personal health record systems.  This is managed through federated document repositories and a document registry to create a longitudinal record of information about a patient within a given clinical affinity domain. These are distinct entities with separate responsibilities:
 
* A [[Document Repository]] is responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests.
 
* A [[Document Repository]] is responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests.
 
* A [[Document Registry]] is responsible for storing information about those documents so that the documents of interest for the care of a patient may be easily found, selected and retrieved irrespective of the repository where they are actually stored.
 
* A [[Document Registry]] is responsible for storing information about those documents so that the documents of interest for the care of a patient may be easily found, selected and retrieved irrespective of the repository where they are actually stored.
 
* Documents are provided by one or more [[Document Source]]s  
 
* Documents are provided by one or more [[Document Source]]s  
 
* They are then accessed by one or more [[Document Consumer]]s
 
* They are then accessed by one or more [[Document Consumer]]s
−
 
−
''<Include a simple graphic that, at a glance, gives an impression of what the profile does.  See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on including an image/graphic.>''
 
  
 
==Benefits==
 
==Benefits==
  
 +
'''Facilitates management of the Electronic Health Record'''
 +
* facilitates the registration, distribution and access across health enterprises of patient electronic health records.
 +
* focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.
  
 
==Details==
 
==Details==
  
−
''<Detailed discussion of what the profile does and how it works>''
+
The '''''Cross-Enterprise Document Sharing (XDS) Integration Profile''''':
 +
* assumes that the enterprises belong to one or more XDS Affinity Domains. An XDS Affinity Domain is a group of healthcare enterprises that have agreed to work together using a common set of policies and share a common infrastructure.
 +
Examples of XDS Affinity Domains include:
 +
::*Community of Care supported by a regional health information organizations in order to serve all patients in a given region.
 +
::*Nationwide EHR
 +
::*Specialized or Disease-oriented Care
 +
:::*Cardiology Specialists and an Acute Cardiology Center
 +
:::*Oncology network
 +
:::*Diabetes network
 +
::*Federation of enterprises
 +
:::*A regional federation made up of several local hospitals and healthcare providers
 +
::*Government sponsored facilities (e.g., VA or Military)
 +
::*Insurance Provider Supported Communities
 +
* The concept of a document in XDS is not limited to textual information. As XDS is document content neutral, any type of clinical information without regard to content and representation is supported. This makes the XDS IHE Integration Profile equally able to handle documents containing simple text, formatted text (e.g., HL7 CDA Release 1), images (e.g., DICOM) or structured and vocabulary coded clinical information (e.g., CDA Release 2, CCR, CEN ENV 13606, DICOM SR). In order to ensure the necessary interoperability between the document sources and the document consumers, the XDS Affinity Domain must adopt policies concerning document format, structure and content.
 +
 
  
 
==Systems Affected==
 
==Systems Affected==
−
''<List (in user terms) systems that would be likely candidates for implementing this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >''
 
  
−
==References==
+
Systems involved in this profile are:
−
[http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_028946.html From Regional Healthcare Information Organizations to a National Healthcare Information Infrastructure]
+
 
 +
* Enterprise-wide information systems that manage a patient’s Electronic Health Record, such as a Hospital Information System.
 +
 
 +
 
 +
'''Actors & Transactions:'''
 +
 
 +
[[Image:XDS-Actor-Transaction-b.jpg]]
 +
 
 +
==Specification==
 +
 
 +
'''Profile Status:''' [[Comments| Final Text]]
  
−
[http://www.diagnosticimaging.com/pacsweb/newsupdate/showArticle.jhtml?articleID=189601278 Cross-enterprise image sharing sees breakthrough]
+
'''Documents:'''
 +
[http://www.ihe.net/Technical_Framework/index.cfm#IT IHE IT Infrastructure Technical Framework Version 2 or later]
 +
* Vol. 1 -
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_Cross_Enterprise_Document_Sh Section 10],
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_1_Document_Replacement_Opt Document Replace Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_2_Document_Addendum_Option Document Addendum Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_3_Document_Transformation_ Document Transformation Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_4_Folder_Management_Option Folder Management Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_5_Asynchronous_Web_Service Asynchronous Web Service Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_6_Reference_ID_Option Reference ID Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_7_On_Demand_Documents_Opti On-Demand Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_8_Persistence_of_Retrieved Persistence of Retrieved Option]
 +
*** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol1.pdf#nameddest=10_2_9_Basic_Patient_Privacy_En Basic Patient Privacy Enforcement Option]
 +
** [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_Vol2a.pdf#nameddest=3_18_Registry_Stored_Query__ITI Vol. 2a - Sections 3.18 Registry Stored Query]
 +
* [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_Vol2b.pdf#nameddest=3_42_Register_Document_Set_b__I Vol. 2b - Sections 3.42 Register Document Set]
 +
* [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2b.pdf#nameddest=3_43_Retrieve_Document_Set__ITI Vol. 2b - Sections 3.43 Retrieve Document Set]
 +
* Vol. 2x - Appendix A, B, K, L, M, N, V, W
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2x.pdf#nameddest=Appendix_A__Web_Service_Definit Vol. 2x - Appendix A Web Services Definition]
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2x.pdf#nameddest=Appendix_B__Definition_of_Docum Vol. 2x - Appendix B Definition of a Document]
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2x.pdf#nameddest=Appendix_K__XDS_Security_Enviro Vol. 2x - Appendix K XDS Security Environment]
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2x.pdf#nameddest=Appendix_M__Using_Patient_Demog Vol. 2x - Appendix M Using Patient Demographics Query in a Multi-Domain Environment]
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2x.pdf#nameddest=Appendix_N__Common_Data_Types Vol. 2x - Appendix N Common Datatypes]
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2x.pdf#nameddest=Appendix_V__Web_Services_for_IH Vol. 2x - Appendix V Web Services for IHE Transactions]
 +
** [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_TF_Vol2x.pdf#nameddest=Appendix_W__Implementation_Mate Vol. 2x - Appendix Implementation Materials]
 +
* [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]
  
−
[http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=17108551 Medical Data GRIDs as approach towards secure cross enterprise document sharing (based on IHE XDS).]
+
'''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]
  
−
[http://www.healthimaging.com/content/view/4240/68/ IHE Update: Bigger, Better Events, New Standards & Guides]
+
'''Additional Supplements: Trial Implementation'''
 +
:* [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_XDS_Metadata_Update.pdf XDS Metadata Update]
 +
:* [[Remove Metadata and Documents (RMD)]]
 +
:* [http://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_Delayed_Doc_Assem.pdf Delayed Document Assembly]
  
−
[http://www.europacs.net/Extended%20abstracts/Integration%20of%20PACS%20RIS%20and%20EPR/Raimund%20Vogel%20Full_Paper_DistEHR_RVo_EuroPACS2006.pdf Architecture for a Distributed National Electronic Health Record System in Austria]
+
'''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
 +
:* HTTP HyperText Transfer Protocol HTTP/1.1 (IETF RFC2616)
 +
:* ISO/IEC 9075 Database Language SQL
 +
:* [http://www.hl7.org HL7 Version 2.5]
 +
:* [http://www.hl7.org HL7 Version 2.3.1 Chapter 2 – Control, Chapter 3 – Patient Administration]
  
 
==See Also==
 
==See Also==
−
Related Profiles:  [[Patient Identity Cross Referencing]], [[Patient Demographics Query]], [[Audit Trail and Node Authentication]] and [[Concistent Time]]
+
[[Document Sharing]]
  
−
Profile Status: [[Comments| Final Text]]
+
Related Profiles:
  
−
The [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]] is the official master document for this Profile.  
+
* [[Patient Identifier Cross-Referencing]] PIX
 +
* [[Patient Demographics Query]] PDQ
 +
* [[Notification of Document Availability]] NAV
 +
* [[Cross-enterprise Sharing of Scanned Documents]] XDS-SD
 +
* Security/Privacy
 +
** [[Audit Trail and Node Authentication]] ATNA
 +
** [[Consistent Time]] CT
 +
** [[Basic Patient Privacy Consents]] BPPC
 +
** [[Cross-Enterprise User Assertion (XUA)]]
 +
** [[Document Digital Signature]] DSG
 +
* Other Derivatives
 +
** [[Cross-Community Access]] XCA
 +
** [[Cross-enterprise Document Media Interchange]] XDM
 +
** [[Cross-enterprise Document Reliable Interchange]] XDR
 +
 
 +
[[XDS Purchasing]] describes considerations when purchasing equipment to deploy this Profile.
 +
 
 +
===Sample Transactions===
 +
[http://ihewiki.wustl.edu/wiki/index.php/Annotated_Provide_And_Register_Transaction.b Annotated example of Provide and Register Transaction]
 +
 
 +
[ftp://ftp.ihe.net/TF_Implementation_Material/ITI/examples/XDS.b/ raw examples]
  
 
The [[XDS FAQ]] answers typical questions about what the Profile does.
 
The [[XDS FAQ]] answers typical questions about what the Profile does.
  
−
[[XDS Purchasing]] describes considerations when purchasing equipment to deploy this Profile.
+
[[XDS Implementation]] provides additional information about implementing this Profile in software.
 +
 
 +
===References===
 +
 
 +
[http://tinyurl.com/wwxds Where in the World is CDA and XDS?]
 +
 
 +
[http://www.e-health-media.com/comment_and_analysis/266/the_xds_factor The XDS Factor]
 +
 
 +
[http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_028946.html From Regional Healthcare Information Organizations to a National Healthcare Information Infrastructure]
 +
 
 +
[http://www.diagnosticimaging.com/pacsweb/newsupdate/showArticle.jhtml?articleID=189601278 Cross-enterprise image sharing sees breakthrough]
 +
 
 +
[http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=17108551 Medical Data GRIDs as approach towards secure cross enterprise document sharing (based on IHE XDS).]
 +
 
 +
[http://www.healthimaging.com/content/view/4240/68/ IHE Update: Bigger, Better Events, New Standards & Guides]
 +
 
 +
[http://www.europacs.net/Extended%20abstracts/Integration%20of%20PACS%20RIS%20and%20EPR/Raimund%20Vogel%20Full_Paper_DistEHR_RVo_EuroPACS2006.pdf Architecture for a Distributed National Electronic Health Record System in Austria]
 +
 
 +
[http://www.srdc.metu.edu.tr/webpage/projects/saphire/publications/April24SaphireEchallenges.doc SAPHIRE: A semantic Web service based Clinical guideline deployment infrastructure exploiting IHE XDS (Turkey)]
  
−
[[XDS Implementation]] provides additional information about implementing this Profile in software.
+
''<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 something.  You might be surprised. >''
  
 
This page is based on the [[Profile Template]]
 
This page is based on the [[Profile Template]]
  
−
[[Category:IT Infrastructure]]
+
[[Category:DocShare]]
 +
[[Category:Profiles]]
 +
[[Category:ITI Profile]]
  
−
[[Category:Profiles]]
+
Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].

Revision as of 10:01, 30 October 2017

Cross-Enterprise Document Sharing (XDS) is an interoperability profile that facilitates the registration, distribution and access across health enterprises of patient electronic health records.

Summary

Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility and personal health record systems. This is managed through federated document repositories and a document registry to create a longitudinal record of information about a patient within a given clinical affinity domain. These are distinct entities with separate responsibilities:

  • A Document Repository is responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests.
  • A Document Registry is responsible for storing information about those documents so that the documents of interest for the care of a patient may be easily found, selected and retrieved irrespective of the repository where they are actually stored.
  • Documents are provided by one or more Document Sources
  • They are then accessed by one or more Document Consumers

Benefits

Facilitates management of the Electronic Health Record

  • facilitates the registration, distribution and access across health enterprises of patient electronic health records.
  • focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.

Details

The Cross-Enterprise Document Sharing (XDS) Integration Profile:

  • assumes that the enterprises belong to one or more XDS Affinity Domains. An XDS Affinity Domain is a group of healthcare enterprises that have agreed to work together using a common set of policies and share a common infrastructure.

Examples of XDS Affinity Domains include:

  • Community of Care supported by a regional health information organizations in order to serve all patients in a given region.
  • Nationwide EHR
  • Specialized or Disease-oriented Care
  • Cardiology Specialists and an Acute Cardiology Center
  • Oncology network
  • Diabetes network
  • Federation of enterprises
  • A regional federation made up of several local hospitals and healthcare providers
  • Government sponsored facilities (e.g., VA or Military)
  • Insurance Provider Supported Communities
  • The concept of a document in XDS is not limited to textual information. As XDS is document content neutral, any type of clinical information without regard to content and representation is supported. This makes the XDS IHE Integration Profile equally able to handle documents containing simple text, formatted text (e.g., HL7 CDA Release 1), images (e.g., DICOM) or structured and vocabulary coded clinical information (e.g., CDA Release 2, CCR, CEN ENV 13606, DICOM SR). In order to ensure the necessary interoperability between the document sources and the document consumers, the XDS Affinity Domain must adopt policies concerning document format, structure and content.


Systems Affected

Systems involved in this profile are:

  • Enterprise-wide information systems that manage a patient’s Electronic Health Record, such as a Hospital Information System.


Actors & Transactions:

XDS-Actor-Transaction-b.jpg

Specification

Profile Status: Final Text

Documents: IHE IT Infrastructure Technical Framework Version 2 or later

CDA mapping to XDS Metadata:

Additional Supplements: Trial Implementation

Underlying Standards:

See Also

Document Sharing

Related Profiles:

XDS Purchasing describes considerations when purchasing equipment to deploy this Profile.

Sample Transactions

Annotated example of Provide and Register Transaction

raw examples

The XDS FAQ answers typical questions about what the Profile does.

XDS Implementation provides additional information about implementing this Profile in software.

References

Where in the World is CDA and XDS?

The XDS Factor

From Regional Healthcare Information Organizations to a National Healthcare Information Infrastructure

Cross-enterprise image sharing sees breakthrough

Medical Data GRIDs as approach towards secure cross enterprise document sharing (based on IHE XDS).

IHE Update: Bigger, Better Events, New Standards & Guides

Architecture for a Distributed National Electronic Health Record System in Austria

SAPHIRE: A semantic Web service based Clinical guideline deployment infrastructure exploiting IHE XDS (Turkey)

<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 something. You might be surprised. >

This page is based on the Profile Template

Current: IT Infrastructure Technical Framework.

Retrieved from "http://wiki.ihe.net/index.php?title=Cross-Enterprise_Document_Sharing&oldid=105381"