Difference between revisions of "PCC TF-1/Dependencies"
| Line 1: | Line 1: | ||
===Dependencies of the PCC Integration Profiles=== | ===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 [[#PCC Integration Profiles Dependencies|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 | + | 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 [[#PCC Integration Profiles Dependencies|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 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. |
{|border="2" cellspacing="0" cellpadding="4" width="100%" align="center" id='PCC Integration Profiles Dependencies' | {|border="2" cellspacing="0" cellpadding="4" width="100%" align="center" id='PCC Integration Profiles Dependencies' | ||
| Line 18: | Line 18: | ||
|Required to manage and resolve conflicts in multiple updates. | |Required to manage and resolve conflicts in multiple updates. | ||
|- | |- | ||
| − | |align = "center"| | + | |align = "center"|Functional Status Assessments (FSA) |
| − | |align = "center"|''Cross Enterprise Document Exchange of Medical Summaries (XDS-MS)''<br/>''Exchange of Personal Health Record Content (XPHR)'' | + | |align = "center"|''Cross Enterprise Document Exchange of Medical Summaries (XDS-MS)''<br/>OR<br/>''Exchange of Personal Health Record Content (XPHR)'' |
| − | |Content Creators of a Functional Status Assessment shall be grouped with Content | + | |Content Creators of a Functional Status Assessment shall be grouped with a Content Creator from the XDS-MS or the XPHR Profile. |
|Ensures that the Functional Status Assessment is communicated as part of an exchange of medical summary information. | |Ensures that the Functional Status Assessment is communicated as part of an exchange of medical summary information. | ||
|- | |- | ||
Revision as of 22:04, 23 July 2007
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 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 |
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. | |
| Functional Status Assessments (FSA) | Cross Enterprise Document Exchange of Medical Summaries (XDS-MS) OR Exchange of Personal Health Record Content (XPHR) |
Content Creators of a Functional Status Assessment shall be grouped with a Content Creator from the XDS-MS or the XPHR Profile. | Ensures that the Functional Status Assessment is communicated as part of an exchange of medical summary information. |
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 |