Difference between revisions of "Cross-Community Patient Discovery"

From IHE Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
supports the means to locate communities which hold patient relevant health data and the translation of patient identifiers across communities holding the same patient’s data. 
 
__TOC__
 
__TOC__
  
 +
==Formal Specification==
  
−
==Summary==
+
===[https://profiles.ihe.net/ITI/TF/Volume1/ch-27.html XCPD (html) specification]===
 +
* [https://profiles.ihe.net/ITI/TF/Volume1/ch-27.html Final Text]
  
−
'''Cross-Community Patient Discovery (XCPD)''' - supports the means to locate communities which hold patient relevant health data and the translation of patient identifiers across communities holding the same patient’s data. 
+
==See Also==
−
 
 
−
==Benefits==
 
−
* supports the means to locate communities which hold patient relevant health data
 
−
* translation of patient identifiers across communities holding the same patient’s data.
 
−
 
 
−
==Details==
 
−
The Cross-Community Patient Discovery (XCPD) profile supports the means to locate communities which hold patient relevant health data and the translation of patient identifiers across communities holding the same patient’s data.  A community is defined as a group of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing health information within the community via an established mechanism.  Facilities/enterprises may host any type of healthcare application such as EHR, PHR, etc.  A community is identifiable by a globally unique id called the homeCommunityId.  Membership of a facility/enterprise in one community does not preclude it from being a member in another community.  Such communities may be XDS Affinity Domains which define document sharing using the XDS profile or any other communities, no matter what their internal sharing structure.
 
−
 
 
−
===Modes of Operation===
 
−
Modes of Operation:
 
−
 
 
−
There are a few modes of operation of XCPD to allow for different types of typical interactions:
 
−
*Demographic Query and Feed mode: This is the base mode and allows the initiator to both feed knowledge or a local patient as well as query for a match at the responder site. This mode allows both sides of the transaction to learn about matching patients.
 
−
*Demographic Query only mode: Here we see a simple demographic query, asking only for the responder to provide a match to a local patient. This mode does not allow responder to know about a match with the initiator’s patient. This satisfies the requirement for nodes that will not support other peer network pull requests.
 
−
*Shared/national Patient Identifier Query and Feed: This mode includes in the query only identifiers, no demographic data is shared.
 
−
 
 
−
===Interaction Modes===
 
−
 
 
−
The following modes are supported and are intended
 
−
 
 
−
*Normal (synchronous)
 
−
**the SOAP request and response are carried in one TCP/IP connection
 
−
***Response is expected in very short timeframe, e.g. less than 60 seconds
 
−
*Asynchronous
 
−
**where the WS-Addressing support for “replyTo” is used to return the response through a separate TCP/IP connection
 
−
***Response is expected in short timeframe, e.g. less than 60 minutes
 
−
*Deferred
 
−
**where the request is decoupled from the reply so each are a separate SOAP interaction (Section 3.55.6.2)
 
−
***Response is expected to have lengthy delay, e.g. more than 60 minutes
 
−
 
 
−
==Systems Affected==
 
−
Systems involved in this profile are:
 
−
* HIS
 
−
 
 
−
'''Actors & Transactions:'''
 
−
 
 
−
[[Image:XCPD-Actor-Transaction.jpg]]
 
−
 
 
−
==Specification==
 
−
 
 
−
'''Profile Status:''' [[Comments| Final Text]] 
 
−
 
 
−
'''Documents:'''
 
−
* [http://www.ihe.net/Technical_Framework/index.cfm] Technical Framework
 
−
:* Vol. 1 - Section 27
 
−
:* Vol. 2b - Sections 3.55 & 3.56
 
−
:* Vol. 2x - Appendix O HL7 v3 Transmission and Trigger Event Control Act Wrappers
 
−
:* Vol. 2x - Appendix E IHE Requirements for Patient Identifier Data Types in HL7 Messages
 
−
:* Vol. 2x - Appendix O HL7 v3 Transmission and Trigger Event Control Act Wrappers
 
−
:* Vol. 2x - Appendix Q  HL7 V3 Sample Payload XML Schemas
 
−
 
 
−
'''Underlying Standards:'''
 
−
:* [http://www.hl7.org/memonly/downloads/v3edition.cfm#V32008 HL7 Version 3 Edition 2008, Patient Administration DSTU, Patient Topic]
 
−
:* HL7 V3 Datatypes  2008 Normative Edition
 
  
−
==See Also==
+
[[Document Sharing]]
  
 
Guest blog articles by Karen Witting, co-chair of the IHE ITI Planning Committee and prime on the XCPD profile
 
Guest blog articles by Karen Witting, co-chair of the IHE ITI Planning Committee and prime on the XCPD profile
Line 75: Line 24:
 
[[Category:ITI Profile]]
 
[[Category:ITI Profile]]
 
[[Category:DocShare]]
 
[[Category:DocShare]]
 +
[[Category:HL7v3]]
 +
[[Category:PatientId]]
  
 
Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].
 
Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].

Latest revision as of 10:09, 12 January 2022

supports the means to locate communities which hold patient relevant health data and the translation of patient identifiers across communities holding the same patient’s data.

Formal Specification

XCPD (html) specification

See Also

Document Sharing

Guest blog articles by Karen Witting, co-chair of the IHE ITI Planning Committee and prime on the XCPD profile

Related Profiles

This page is based on the Profile Template

Current: IT Infrastructure Technical Framework.

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