Difference between revisions of "PCC TF-1/Dependencies"
Jump to navigation
Jump to search
| (6 intermediate revisions by the same user not shown) | |||
| 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 9: | Line 9: | ||
|align = "center"|'''Purpose''' | |align = "center"|'''Purpose''' | ||
|- | |- | ||
| − | |rowspan = " | + | |rowspan = "2"|All PCC Content Profiles<br> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|align = "center"|''Audit Trail and Node Authentication (ATNA)'' | |align = "center"|''Audit Trail and Node Authentication (ATNA)'' | ||
|Each Content Creator and Content Consumer actor shall be grouped with the ATNA Secured Node Actor | |Each Content Creator and Content Consumer actor shall be grouped with the ATNA Secured Node Actor | ||
| Line 30: | 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"|''Document | + | |align = "center"|''Cross Enterprise Document Exchange of Medical Summaries (XDS-MS)''<br/>OR<br/>''Exchange of Personal Health Record Content (XPHR)''<br/>OR<br/>''Emergency Department Referral (EDR)'' |
| − | | | + | |Content Consumers implementing the Functional Status Assessments profile shall be grouped with either the XDS-MS, XPHR or EDR Content Consumer. Content Creators implementing the Functional Status Assessments profile shall be grouped with either the XDS-MS, XPHR or EDR Content Creator. |
| − | |Ensures that | + | |Ensures that the Functional Status Assessment is communicated as part of an exchange of medical summary information. |
|- | |- | ||
| − | |align = "center" | | + | |align = "center" rowspan=2|Functional Status Assessments (QED) |
| − | |align = "center"|'' | + | |align = "center"|''Audit Trail and Node Authentication (ATNA)'' |
| − | | | + | |Each actor in this profile shall be grouped with the ATNA Secure Node or Secure Application actor. |
| − | | | + | |Required to manage audit trail of exported PHI, node authentication, and transport encryption. |
|- | |- | ||
| + | |align = "center"|''Consistent Time (CT)'' | ||
| + | |Each actor in this profile shall be grouped with the Time Client Actor | ||
| + | |Required to manage and resolve conflicts in multiple updates. | ||
|} | |} | ||
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. | 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. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 15:23, 21 August 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) OR Emergency Department Referral (EDR) |
Content Consumers implementing the Functional Status Assessments profile shall be grouped with either the XDS-MS, XPHR or EDR Content Consumer. Content Creators implementing the Functional Status Assessments profile shall be grouped with either the XDS-MS, XPHR or EDR Content Creator. | Ensures that the Functional Status Assessment is communicated as part of an exchange of medical summary information. |
| Functional Status Assessments (QED) | Audit Trail and Node Authentication (ATNA) | Each actor in this profile shall be grouped with the ATNA Secure Node or Secure Application actor. | Required to manage audit trail of exported PHI, node authentication, and transport encryption. |
| Consistent Time (CT) | Each actor in this profile shall be grouped with the Time Client Actor | Required to manage and resolve conflicts in multiple updates. |
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.