Difference between revisions of "Cross-Community Patient Discovery"
Line 1: | Line 1: | ||
+ | __TOC__ | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Summary== | ==Summary== | ||
− | |||
− | '' | + | '''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. |
− | |||
− | |||
==Benefits== | ==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== | ==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. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
==Systems Affected== | ==Systems Affected== | ||
− | + | Systems involved in this profile are: | |
− | + | * HIS | |
− | * | ||
− | |||
− | |||
'''Actors & Transactions:''' | '''Actors & Transactions:''' | ||
− | + | [[Image:XCPD-Actor-Transaction.jpg]] | |
==Specification== | ==Specification== | ||
− | '''Profile Status:''' [[Comments| | + | '''Profile Status:''' [[Comments| Trial Implementation]] |
− | |||
'''Documents:''' | '''Documents:''' | ||
− | + | * [http://www.ihe.net/Technical_Framework/index.cfm#IT Cross-Community Patient Discovery (XCPD)] Trial Implementation Supplement | |
− | + | :* Vol. 1 - Section 27 | |
− | + | :* Vol. 2b - Sections 3.55 & 3.56 | |
− | [http://www.ihe.net/Technical_Framework/index.cfm# | + | :* Vol. 2x - Appendix O HL7 v3 Transmission and Trigger Event Control Act Wrappers |
− | :* | + | * [http://www.ihe.net/Technical_Framework/index.cfm#IT Patient Identifier Cross-Reference (PIX) and Patient Demographic Query (PDQ) HL7 v3] Trial Implementation Supplement |
− | :* | + | :* 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:''' | '''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 | |
− | :* [http:// | ||
− | |||
− | :* | ||
==See Also== | ==See Also== | ||
− | |||
− | |||
− | |||
'''Related Profiles''' | '''Related Profiles''' | ||
− | + | This page is based on the [[Profile Template]] | |
− | + | [[Category:Profiles]] | |
− | + | [[Category:ITI Profile]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Current: [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]]. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 13:47, 15 February 2011
Summary
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.
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.
Systems Affected
Systems involved in this profile are:
- HIS
Actors & Transactions:
Specification
Profile Status: Trial Implementation
Documents:
- Cross-Community Patient Discovery (XCPD) Trial Implementation Supplement
- Vol. 1 - Section 27
- Vol. 2b - Sections 3.55 & 3.56
- Vol. 2x - Appendix O HL7 v3 Transmission and Trigger Event Control Act Wrappers
- Patient Identifier Cross-Reference (PIX) and Patient Demographic Query (PDQ) HL7 v3 Trial Implementation Supplement
- 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:
- HL7 Version 3 Edition 2008, Patient Administration DSTU, Patient Topic
- HL7 V3 Datatypes 2008 Normative Edition
See Also
Related Profiles
This page is based on the Profile Template
Current: IT Infrastructure Technical Framework.