PCC TF-1/Overview

PCC Integration Profiles Overview

In this document, each IHE Integration Profile is defined by:

• The IHE actors involved
• The specific set of IHE transactions exchanged by each IHE actor.

These requirements are presented in the form of a table of transactions required for each actor supporting the Integration Profile. Actors supporting multiple Integration Profiles are required to support all the required transactions of each Integration Profile supported. When an Integration Profile depends upon another Integration Profile, the transactions required for the dependent Integration Profile have not been included in the table.

Note that IHE Integration Profiles are not statements of conformance to standards, and IHE is not a certifying body. Users should continue to request that vendors provide statements of their conformance to standards issued by relevant standards bodies, such as HL7 and DICOM. Standards conformance is a prerequisite for vendors adopting IHE Integration Profiles.

Also note that there are critical requirements for any successful integration project that IHE cannot address. Successfully integrating systems still requires a project plan that minimizes disruptions and describes fail-safe strategies, specific and mutually understood performance expectations, well-defined user interface requirements, clearly identified systems limitations, detailed cost objectives, plans for maintenance and support, etc.

Cross-Enterprise Sharing of Medical Summaries (XDS-MS)

This profiles provides a mechanism to automate the sharing process between care providers of Medical Summaries. Medical summaries are a class of clinical documents that contain the most relevant portions of information about the patient intended for a specific provider or a broad range of potential providers in different settings. Medical Summaries are commonly created and consumed by electronic medical record systems at points in time of transfers of care such as referrals or discharge.

Note that this Cross-Enterprise Sharing of Medical Summaries Integration Profile is specialized for regions or countries in term of detailed content of sections and information elements by a set of Document Content Profiles. This Integration profile has been structured to facilitate the inclusion of national extensions in the form of country or "realm" specific Content Profiles. When developed by the national IHE Chapters these will be included in the PCC TF-3.

Exchange of Personal Health Record Content (XPHR)

This integration profile describes the content and format of summary information extracted from a PHR system used by a patient for import into healthcare provider information systems, and visa versa. The purpose of this profile is to support interoperability between PHR systems used by patients and the information systems used by healthcare providers.

This profile does not address all the data exchange requirements of PHR systems. A PHR system may leverage other IHE Integration and Content Profiles for interoperability in addition to the XPHR Content Profile. For example, a PHR Systems may implement XDS-MS to import medical summaries produced by EHR systems, XDS-I to import imaging information, XDS-Lab to import laboratory reports, et cetera.

Basic Patient Privacy Consents (BPPC)

This profile provides a mechanism to record the patient privacy consent(s), a method to mark documents published to XDS with the patient privacy consent that was used to authorize the publication, and a method for XDS Consumers to use to enforce the privacy consent appropriate to the use. The XDS profile provides little guidance on supporting privacy policies within an affinity Domain. Documents can be marked with a confidentialityCode, but no information has been provided on how to use this information to support patient privacy concerns. This profile corrects that deficiency by describing a mechanism whereby an Affinity Domain can develop and implement multiple privacy policies, and describes how that mechanism can be integrated with the access control mechanisms supported by the XDS Actors (e.g. EHR systems). There are three key parts of the profile:

1. It provides a content module for capturing a patient consent to a privacy policy or policies.
2. It describes how the XDS metadata is used to support the consent policies.
3. Finally it describes the method by which XDS Actors can enforce the privacy policies determined by the document confidentialityCode and the patient privacy consents.

Preprocedure History and Physical (PPHP)

This purpose of this content profile is to provide a mechanism to record a pre-procedure assessment, and to communicate that assessment and other relevant documentation, such as laboratory and imaging reports to relevant parties prior to surgery.

Emergency Department Referral (EDR)

This profile provides a means to communicate medical summary data from an EHR System to an EDIS System during a referral from a provider to an emergency department.