Cross-Community Patient Discovery

From IHE Wiki
Jump to: navigation, search


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.

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:

XCPD-Actor-Transaction.jpg

Specification

Profile Status: Final Text

Documents:

  • Primary Content

Trial Implementation of Option extracted out


Underlying Standards:

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.