PCC TF-1/Content Bindings with XDS, XDM and XDR

Content Bindings with XDS, XDM and XDR

It is expected that this profile will be used environment where the physician offices and hospitals have a coordinated infrastructure that serves the information sharing needs of this community of care. Several mechanisms are supported by IHE profiles:

• A registry/repository-based infrastructure is defined by the IHE Cross-Enterprise Document Sharing (XDS) and other IHE Integration Profiles such as patient identification (PIX & PDQ), and notification of availability of documents (NAV).
• A media-based infrastructure is defined by the IHE Cross-Enterprise Document Media Interchange (XDM) profile.
• A reliable messaging-based infrastructure is defined by the IHE Cross-Enterprise Document Reliable Interchange (XDR) profile.
• All of these infrastructures support Security and privacy through the use of the Consistent Time (CT) and Audit Trail and Node Authentication (ATNA) profiles.

For more details on these profiles, see the IHE IT Infrastructure Technical Framework, found here: http://www.ihe.net/Technical_Framework/.

Such an infrastructure is assumed by the use cases that focus on the context for defining the specific clinical information content for this profile.

A content binding describe how the payloads used in IHE transactions are related to and/or constrained by the data elements contained within the content sent or received in those transactions. This section is where any specific dependencies between the content and transaction are defined. The Patient Care Coordination Technical Framework defines a binding to use when grouping the Content Creator of this Profile with the IHE ITI XDS, XDM or XDR Integration Profiles.

Content	Binding	Actor	Optionality
[[PCC TF-1/Content Bindings with XDS, XDM and XDR#{{{2}}}|{{{3}}}]]	Medical Document Binding to XDS, XDM and XDR	Content Creator	{{{5}}}
		Content Consumer	{{{6}}}