Difference between revisions of "Cross-Community Access"

From IHE Wiki
Jump to navigation Jump to search
(New page: __TOC__ ==Summary== '''Healthcare Provider Directory (HPD)''' - supports management of healthcare provider information, both individual and organizational, in a directory structure. =...)
 
Line 4: Line 4:
 
==Summary==
 
==Summary==
  
−
'''Healthcare Provider Directory (HPD)''' - supports management of healthcare provider information, both individual and organizational, in a directory structure.
+
'''Cross-Community Access (XCA)''' - upports the means to query and retrieve patient relevant medical data held by other communities.
 +
 
 
==Benefits==
 
==Benefits==
−
* supports querying against a directory of healthcare provider information
+
* supports peer-to-peer querying with other communities
−
* supports feeding a directory of healthcare provider information
+
* supports peer-to-peer retrieve with other communities
  
 
==Details==
 
==Details==
−
The Healthcare Provider Directory (HPD) profile supports management of healthcare provider information in a directory structure.  HPD directory structure is a listing of the following two categories of healthcare providers that are classified by provider type, specialties, credentials, demographics and service locations:
+
The Cross-Community Access profile supports the means to query and retrieve patient relevant medical data held by other communities.  A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information 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.
−
* Individual Provider - A person who provides healthcare services, such as a physician, nurse, or pharmacist.  
 
−
* Organizational Providers - Organizations that provide or support healthcare services, such as hospitals, Counseling Organizations (e.g., Drug, Alcohol) Healthcare Information Exchanges (HIEs), Managed Care, Integrated Delivery Networks (IDNs), and Associations.
 
−
 
 
−
Typical provider information maintained by the directory is demographics, address, credential and specialty information as well as electronic endpoint to facilitate trusted communications with a provider.  The directory can also maintain relationship. Some examples of relationship are: a Health Information Exchange (HIE) and its members: Integrated Delivery Networks and their care delivery members, hospitals and their practitioners, hospitals and their sub organizations including departments, physician Practice Groups and their practitioners, practitioners and the hospitals they are associated with (members of), and Medical Associations and their members.
 
−
 
 
−
Different kinds of data sources and consumers interface with the Provider Information Directory to:
 
−
* Send new and updated provider information
 
−
* Query provider information
 
−
 
 
−
It is intended that provider information comes from authorized international, regional, state and national sources, as stewards of the most accurate and current data. Some identified sources are:
 
−
* State licensing bureaus
 
−
* National Associations
 
−
* Commercial registries
 
−
* Delivery Networks
 
−
* Information Exchanges etc
 
  
−
The scope of this profile focuses initially on the minimum "foundational" attribute set required for defining a provider information directory, resulting in a usable work product as well as recommendations for future phase expansions. This profile is readily adaptable and scalable to production environments needing to operate trusted provider directory services that link multiple endpoints spanning enterprise, regional, national, and global jurisdictions.  This profile is extendable to information not explicitly defined in the profile.
 
  
 
==Systems Affected==
 
==Systems Affected==
Line 35: Line 20:
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
−
[[Image:HPD-Actor-Transaction.jpg]]
+
[[Image:XCA-Actor-Transaction.jpg]]
  
 
==Specification==
 
==Specification==
Line 42: Line 27:
  
 
'''Documents:'''  
 
'''Documents:'''  
−
* [http://www.ihe.net/Technical_Framework/index.cfm#IT Cross-Community Healthcare Provider Directory (HPD)] Trial Implementation Supplement
+
* [http://www.ihe.net/Technical_Framework/index.cfm#IT Cross-Community Access (XCA)] Trial Implementation Supplement
−
:* Vol. 1 - Section 28
+
:* Vol. 1 - Section 18
−
:* Vol. 2b - Sections 3.58 & 3.59
+
:* Vol. 2a - Sections 3.18
 +
:* Vol. 2b - Sections 3.43, 3.38 & 3.39
 +
 
 +
[http://www.ihe.net/Technical_Framework/index.cfm#IT IHE IT Infrastructure Technical Framework Version 5 or later]
 +
:* Vol. 1 - Appendix J, K
 +
:* Vol. 2x - Appendix B, K, L, N, V, W
 +
:* Vol. 3 - Section 4.1, 4.2, 4.3
 +
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
−
* Health informatics - Directory services for health care providers, subjects of care, and other entities (ISO/TS 21091)
+
:* ebRIM OASIS/ebXML Registry Information Model v3.0
−
* IETF LDAP v3  
+
:* ebRS OASIS/ebXML Registry Services Specifications v3.0
−
* DSMLv2
 
−
* SOAP 1.2
 
  
 
==See Also==
 
==See Also==

Revision as of 15:00, 22 March 2011


Summary

Cross-Community Access (XCA) - upports the means to query and retrieve patient relevant medical data held by other communities.

Benefits

  • supports peer-to-peer querying with other communities
  • supports peer-to-peer retrieve with other communities

Details

The Cross-Community Access profile supports the means to query and retrieve patient relevant medical data held by other communities. A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information 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:

XCA-Actor-Transaction.jpg

Specification

Profile Status: Trial Implementation

Documents:

  • Vol. 1 - Section 18
  • Vol. 2a - Sections 3.18
  • Vol. 2b - Sections 3.43, 3.38 & 3.39

IHE IT Infrastructure Technical Framework Version 5 or later

  • Vol. 1 - Appendix J, K
  • Vol. 2x - Appendix B, K, L, N, V, W
  • Vol. 3 - Section 4.1, 4.2, 4.3


Underlying Standards:

  • ebRIM OASIS/ebXML Registry Information Model v3.0
  • ebRS OASIS/ebXML Registry Services Specifications v3.0

See Also

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_Access&oldid=49353"