PCC TF-1/Dependencies
Dependencies of the PCC Integration Profiles
Dependencies among IHE Integration Profiles exist when implementation of one integration profile is a prerequisite for achieving the functionality defined in another integration profile. The table below defines these dependencies. Some dependencies require that an actor supporting one profile be grouped with one or more actors supporting other integration profiles. For example, Cross-Enterprise Sharing of Medical Summaries (XDS-MS) requires that different participating actors support the Cross-Enterprise Document Sharing (XDS) Integration Profile as well as that its actors be grouped with a Secured Node Actor of the Audit Trail and Node Authentication (ATNA) Integration Profile. The dependency exists because XDS-MS and XDS actors must support a secured communication channel with proper auditing of the exchange of patient identified information in order to function properly in an environment where protection of patient privacy is critical.
| Integration Profile | Depends on | Dependency Type | Purpose |
| All PCC Content Profiles |
Cross-Enterprise Document Sharing (XDS) | Implementers of a PCC Content Profile may implement the XDS Profile to enable sharing of the clinical documents within an XDS Affinity Domain. When the XDS profile is used to provide document interchange, each PCC Content Creators must be grouped with an XDS Document Source actor, and each PCC Content Consumer must be grouped with an XDS Document Consumer actor. | Ensure that the sharing of PCC Document Content Profiles within an XDS Affinity Domain can co-exist with the sharing of other types of documents (e.g. imaging, ECG, etc.) |
| Cross-Enterprise Document Media Interchange (XDM) |
Implementers of a PCC Content Profile may implement the XDM Profile to enable sharing of the clinical documents using media. When the XDM profile is used to provide document interchange, each PCC Content Creator must be grouped with an XDM Portable Media Creator actors, and each PCC Content Consumer must be grouped with an XDM Portable Media Consumer. | Ensure that the sharing of PCC Document Content Profiles on media can co-exist with the sharing of other types of documents (e.g. imaging, ECG, etc.) | |
| Cross-Enterprise Document Reliable Interchange (XDR) |
Implementers of a PCC Content Profile may implement the XDR Profile to enable sharing of the clinical documents using reliable point-to-point network messages. When the XDR profile is used to provide document interchange, each PCC Content Creator must be grouped with an XDR Document actor, and each PCC Content Consumer must be grouped with an XDR Document Recipient. | Ensure that the sharing of PCC Document Content Profiles through reliable point-to-point messages can co-exist with the sharing of other types of documents (e.g. imaging, ECG, etc.) | |
| Audit Trail and Node Authentication (ATNA) | Each Content Creator and Content Consumer actor shall be grouped with the ATNA Secured Node Actor | Required to manage audit trail of exported PHI, node authentication, and transport encryption. | |
| Consistent Time (CT) | Each Content Creator and Content Consumer actor shall be grouped with the Time Client Actor | Required to manage and resolve conflicts in multiple updates. | |
| Exchange of Personal Health Record Content (XPHR) | Document Digital Signatures (DSG) |
XPHR Actors should digitally sign the content, and verify the digital signature of the content before importing it. | Ensures that content is not maliciously or even accidentally altered when tranmitted between PHR and EHR systems. |
| Basic Patient Privacy Consents (BPPC) |
XDS Scanned Documents (XDS-SD) ITI TF-1: ? |
Document Sources publishing Consent documents must use the XDS-SD profile when creating documents containing scanned images of "wet" signatures. | When the patient uses wet signatures (ink on paper), XDS-SD is used to capture the actual copy of the consent that the patient signed. |
To support a dependent profile, an actor must implement all required transactions in the prerequisite profiles in addition to those in the dependent profile. In some cases, the prerequisite is that the actor selects any one of a given set of profiles.
XDS/XDR Option Requirements of the BPPC Profile
The tables below lists the XDS and XDR options that shall be supported by Document Registry, Document Sources and Document Consumers Actors in the BPPC profile.
| Actor | Options | Vol & Section |
|---|---|---|
| Document Source | Privacy Option | ITI TF-2: 3.15.4.1.1 |
| Document Consumer | Privacy Option | ITI TF-2: 3.17.4.1.1.1 ITI TF-2: 3.18.4.1.1.1 |
| Document Registry | Privacy Option | ITI TF-2: 3.14.4.1.1.1 ITI TF-2: 3.18.4.1.1.1 |
| Document Repository | (none) |
XDM Option Requirements of the BPPC Profile
The table below lists the XDM options that shall be supported by XDM Actors in the BPPC profile.
| Actor | Options | Vol & Section |
|---|---|---|
| Portable Media Creator | Privacy Option | ITI TF-2: 3.32.4.1.1.1 |
| Portable Media Importer | Privacy Option | ITI TF-2: 3.32.4.1.1.1 |