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 />
Discharge<br />
Summary<br />
Medical Document Binding to XDS, XDM<br />
and XDR<br />
Content Creator O (Note 1)<br />
Content Consumer<br />
R<br />
800<br />
805<br />
810<br />
815<br />
820<br />
Figure 3.1-5 Content Bindings<br />
Note 1: Content Creators must support generation of at least one type of content from this table with a<br />
transaction in order for the transaction to meet the requirements of the XDS-MS profile. Content<br />
Consumers must support both types of content to meet these requirements.<br />
3.1.9 Content Modules<br />
Content modules describe the content of a payload found in an <strong>IHE</strong> transaction. Content<br />
profiles are transaction neutral. They do not have dependencies upon the transaction that<br />
they appear in. These dependencies are reflected in the Bindings listed above.<br />
3.1.9.1 Referral Summary<br />
All referral summaries shall be structured and coded as required by the Referral<br />
Summary Content Module described in PCC TF-2. The inclusion of the specific coded<br />
attributes explicitly defined as optional, may be supported by specific implementations of<br />
Document Sources using an <strong>IHE</strong> identified coded terminology of their choice. The<br />
requirements and manner in which implementations support such capabilities is beyond<br />
the scope of this Integration Profile.<br />
3.1.9.2 Discharge Summary<br />
All discharge summaries shall be structured and coded as required by the Discharge<br />
Summary Content Module described in PCC TF-2. The inclusion of the specific coded<br />
attributes explicitly defined as optional, may be supported by specific implementations of<br />
Document Sources using an <strong>IHE</strong> identified coded terminology of their choice. The<br />
requirements and manner in which implementations support such capabilities is beyond<br />
the scope of this Integration Profile.<br />
3.1.10 Grouping with other Profile Actors<br />
Content profiles may impose additional requirements on the transactions used when<br />
grouped with actors from other <strong>IHE</strong> Profiles.<br />
825<br />
830<br />
3.1.10.1 Cross Enterprise Document Sharing, Media Interchange and<br />
Reliable Messages<br />
Actors from the ITI XDS, XDM and XDR profiles embody the Content Creator and<br />
Content Consumer sharing function of this profile. A Content Creator or Content<br />
Consumer must be grouped with appropriate actors from the XDS, XDM or XDR<br />
profiles, and the metadata sent in the document sharing or interchange messages has<br />
_____________________________________________________________________<br />
29<br />
Revision 3.0 Public Comment — June 25, 2007<br />
Copyright © 1997-2007: ACC/HIMSS/RSNA