IHE Patient Care Coordination Technical Framework Vol I
IHE Patient Care Coordination Technical Framework Vol I
IHE Patient Care Coordination Technical Framework Vol I
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
PCC <strong>Technical</strong> <strong>Framework</strong> V3.0, vol. 1<br />
________________________________________________________________________<br />
400<br />
Integration<br />
Profile<br />
Depends on Dependency Type Purpose<br />
Cross-<br />
Enterprise<br />
Document<br />
Sharing (XDS)<br />
Implementers of a PCC Content Profile may<br />
implement the XDS Profile to enable sharing<br />
of the clinical documents within an XDS<br />
Affinity Domain. When the XDS profile is<br />
used to provide document interchange, each<br />
PCC Content Creators must be grouped with<br />
an XDS Document Source actor, and each<br />
PCC Content Consumer must be grouped<br />
with an XDS Document Consumer actor.<br />
Ensure that the sharing of<br />
PCC Document Content<br />
Profiles within an XDS<br />
Affinity Domain can coexist<br />
with the sharing of<br />
other types of documents<br />
(e.g. imaging, ECG, etc.)<br />
All PCC Content<br />
Profiles<br />
Cross-<br />
Enterprise<br />
Document<br />
Media<br />
Interchange<br />
(XDM)<br />
Cross-<br />
Enterprise<br />
Document<br />
Reliable<br />
Interchange<br />
(XDR)<br />
Implementers of a PCC Content Profile may<br />
implement the XDM Profile to enable<br />
sharing of the clinical documents using<br />
media. When the XDM profile is used to<br />
provide document interchange, each PCC<br />
Content Creator must be grouped with an<br />
XDM Portable Media Creator actors, and<br />
each PCC Content Consumer must be<br />
grouped with an XDM Portable Media<br />
Consumer.<br />
Implementers of a PCC Content Profile may<br />
implement the XDR Profile to enable<br />
sharing of the clinical documents using<br />
reliable point-to-point network messages.<br />
When the XDR profile is used to provide<br />
document interchange, each PCC Content<br />
Creator must be grouped with an XDR<br />
Document actor, and each PCC Content<br />
Consumer must be grouped with an XDR<br />
Document Recipient.<br />
Ensure that the sharing of<br />
PCC Document Content<br />
Profiles on media can coexist<br />
with the sharing of<br />
other types of documents<br />
(e.g. imaging, ECG, etc.)<br />
Ensure that the sharing of<br />
PCC Document Content<br />
Profiles through reliable<br />
point-to-point messages<br />
can co-exist with the<br />
sharing of other types of<br />
documents (e.g. imaging,<br />
ECG, etc.)<br />
Audit Trail and<br />
Node<br />
Authentication<br />
(ATNA)<br />
Each Content Creator and Content<br />
Consumer actor shall be grouped with the<br />
ATNA Secured Node Actor<br />
Required to manage audit<br />
trail of exported PHI,<br />
node authentication, and<br />
transport encryption.<br />
Consistent Time<br />
(CT)<br />
Each Content Creator and Content<br />
Consumer actor shall be grouped with the<br />
Time Client Actor<br />
Required to manage and<br />
resolve conflicts in<br />
multiple updates.<br />
Exchange of<br />
Personal Health<br />
Record Content<br />
(XPHR)<br />
Document<br />
Digital<br />
Signatures<br />
(DSG)<br />
XPHR Actors should digitally sign the<br />
content, and verify the digital signature of<br />
the content before importing it.<br />
Ensures that content is not<br />
maliciously or even<br />
accidentally altered when<br />
tranmitted between PHR<br />
and EHR systems.<br />
Basic <strong>Patient</strong><br />
Privacy<br />
XDS Scanned<br />
Documents<br />
Document Sources publishing Consent<br />
documents must use the XDS-SD profile<br />
When the patient uses wet<br />
signatures (ink on paper),<br />
_____________________________________________________________________<br />
14<br />
Revision 3.0 Public Comment — June 25, 2007<br />
Copyright © 1997-2007: ACC/HIMSS/RSNA