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

---

1.0 Introduction

1.1 Overview

The Transaction Package enables capture of supplemental data variables not typically maintained in an electronic health record or laboratory information system through a more seamless integration with the local information system. This allows for the local system to retrieve a form specific to the identified potential public health threat. In the context of quality, it allows for the local system to capture supplemental data elements required for quality reporting that may not be available to the electronic health record.

1.2 Copyright Permissions

COPYRIGHT NOTICE

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.

1.3 Reference Documents

This section provides a list of key reference documents and background material. If you are already familiar with this information, proceed to Section 2.0.

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

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, subsetting or implementation options by which the specification may be implemented in a limited manner. Such scoping, subsetting 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/TP50
	Prev  TOC  Next