1.0 Introduction

1.1 Overview

The HITSP Transfer of Documents on Media Transaction describes both the type of media (CD-ROM, USB Memory, and e-Mail) that may be used to write the documents and provides a directory structure that must be followed in order for the contents to be successfully accessed and processed by systems. An example might be to transport data from one healthcare provider to another healthcare provider, or a healthcare consumer may wish to move the contents of a Personal Health Record (PHR) using physical media or e-Mail.

This Transaction uses the IHE Cross-Enterprise Document Media Interchange Integration Profile developed by Integrating the Healthcare Enterprise (IHE), a companion to the IHE Cross -Enterprise Document Sharing (XDS) Integration Profile. This Integration Profile has been used by HITSP in a variety of Use Cases and harmonized under HITSP/TP13 Manage Sharing of Documents Transaction Package. HITSP/TP13 Manage Sharing of Documents facilitates the registration, distribution and on-line access of patient electronic healthcare records across health enterprises. Cross-Enterprise Document Media Interchange (XDM) uses the XDS- defined metadata formats in a simpler environment where media is interchanged rather than via on-line network interchanges.

This specification includes by reference the Transactions and Components that comprise the Transfer of Documents on Media Transaction. It describes the processes supported by these structures and the work that is accomplished by implementing this Transaction. Source material is from the IHE IT Infrastructure (ITI) Technical Framework (TF) - Cross-Enterprise Document Media Interchange (XDM) Integration Profile.

1.2 Copyright Permissions

2009 ANSI. This material may be copied without permission from ANSI only if and to the extent that the text is not altered in any fashion and ANSIs copyright is clearly noted.

DICOM materials used in this document have been extracted from relevant copyrighted materials with permission of the Digital Imaging and Communication Standards Committee. Copies of this standard may be retrieved from DICOM at http://medical.nema.org.

IHE materials used in this document have been extracted from relevant copyrighted materials with permission of Integrating the Healthcare Enterprise (IHE) International. Copies of this standard may be retrieved from the IHE Web Site at www.ihe.net.

OASIS materials used in this document have been extracted from relevant copyrighted materials with permission of the Organization for the Advancement of Structured Information Standards (OASIS). Copies of this standard are available from OASIS at www.oasis-open.org.

1.3 Reference Documents

This section provides a list of key reference documents and background material.

A list of key reference documents and background material is provided in the table below. These documents can be retrieved from www.hitsp.org.

Table 1-1 Reference Documents

Reference Document	Document Description
HITSP Acronyms List	Lists and defines the acronyms used in this document
HITSP Glossary	Provides definitions for relevant terms used by HITSP documents
TN900 - Security and Privacy Technical Note	TN900 is a reference document that provides the overall context for use of the HITSP Security and Privacy constructs

1.4 Conformance

This section describes the conformance criteria, which are objective statements of requirements that can be used to determine if a specific behavior, function, interface, or code set has been implemented correctly.

1.4.1 Conformance Criteria

In order to claim conformance to this construct specification, an implementation must satisfy all the requirements and mandatory statements listed in this specification, the associated HITSP Interoperability Specification, its associated construct specifications, as well as conformance criteria from the selected base and composite standards. A conformant system must also implement all of the required interfaces within the scope, subset or implementation option that is selected from the associated Interoperability Specification.

Claims of conformance may only be made for the overall HITSP Interoperability Specification or Capability with which this construct is associated.

1.4.2 Conformance Scoping, Subsetting and Options

A HITSP Interoperability Specification must be implemented in its entirety for an implementation to claim conformance to the specification. HITSP may define the permissibility for interface scoping, sub setting or implementation options by which the specification may be implemented in a limited manner. Such scoping, sub setting and options may extend to associated constructs, such as this construct. This construct must implement all requirements within the selected scope, subset or options as defined in the associated Interoperability Specification to claim conformance.

	Return to detail page at www.hitsp.org	HITSP/T33
	Prev TOC Next