HITSP CDA Content Modules

The purpose of the HITSP CDA Content Modules Component is to define the library of components that may be used by HITSP constructs in standards based exchanges. The components are organized into modules to simplify navigation. These modules are organized along the same principals as the HL7 Continuity of Care Document.

The data elements found in these modules are based on IHE PCC Technical Framework Volume II, Release 4. That Technical Framework contains specifications for document sections that are consistent with all Implementation Guides for clinical documents currently selected for HITSP constructs.

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.

Certain materials contained in this Interoperability Specification are reproduced from Health Level Seven (HL7) HL7 Implementation Guide: CDA Release 2 Continuity of Care Document (CCD), with permission of Health Level Seven, Inc. No part of the material may be copied or reproduced in any form outside of the Interoperability Specification documents, including an electronic retrieval system, or made available on the Internet without the prior written permission of Health Level Seven, Inc. Copies of standards included in this Interoperability Specification may be purchased from the Health Level Seven, Inc. Material drawn from these standards is credited where used.

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.

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
TN901 - Clinical Documents	TN901 is a reference document that provides the overall context for use of the HITSP Care Management and Health Records constructs
TN903 Data Architecture	TN903 is a reference document that provides the overall context for use of the HITSP Data Architecture 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, 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.

1.5 Document Conventions

1.5.1 Key Words

The key words shall, shall not, should, should not and may are to be interpreted as described in RFC 2119 and will appear when used in that fashion in this typeface.

The key words required and optional are also to be interpreted as described in RFC 2119 when they are used to indicate the optionality of components used in an exchange.

1.0 Introduction

1.1 Overview