IHE Patient Care Coordination Technical Framework Vol I
IHE Patient Care Coordination Technical Framework Vol I
IHE Patient Care Coordination Technical Framework Vol I
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
PCC <strong>Technical</strong> <strong>Framework</strong> V3.0, vol. 1<br />
________________________________________________________________________<br />
385<br />
390<br />
395<br />
Figure 2.5-1 <strong>IHE</strong> <strong>Patient</strong> <strong>Care</strong> <strong>Coordination</strong> Content Integration Profiles<br />
2.6 Dependencies of the PCC Integration Profiles<br />
Dependencies among <strong>IHE</strong> Integration Profiles exist when implementation of one<br />
integration profile is a prerequisite for achieving the functionality defined in another<br />
integration profile. The table below defines these dependencies. Some dependencies<br />
require that an actor supporting one profile be grouped with one or more actors<br />
supporting other integration profiles. For example, Cross-Enterprise Sharing of Medical<br />
Summaries (XDS-MS) requires that different participating actors support the Cross-<br />
Enterprise Document Sharing (XDS) Integration Profile as well as that its actors be<br />
grouped with a Secured Node Actor of the Audit Trail and Node Authentication (ATNA)<br />
Integration Profile. The dependency exists because XDS-MS and XDS actors must<br />
support a secured communication channel with proper auditing of the exchange of patient<br />
identified information in order to function properly in an environment where protection<br />
of patient privacy is critical.<br />
_____________________________________________________________________<br />
13<br />
Revision 3.0 Public Comment — June 25, 2007<br />
Copyright © 1997-2007: ACC/HIMSS/RSNA
Change language