4.0 Document Updates

The following sections provide the details of updates made to this document.

4.1 December 10, 2008

The changes in this construct address the following comments received during the Public Comment and Inspection Testing period (September 29 October 24, 2008).

5594

Section 2.2.1 Data Mapping

- Delete incorrect text related to discharge summary

- Added text to require implementation support IHE PCC Technical Framework and HITSP constraints

- Constrained Data Elements in History of Immunizations Content Module

Administered Date and Drug Manufacturer

Section 2.3.3 Informative Reference Standards

- Corrected Version for Integrating the Healthcare Enterprise (IHE) Patient Care Coordination (PCC) Technical Framework Revision 4.0 in Table 2-6 Informative Reference Standards

Global

- Document Name change from Immunization and Response Component to Immunization Query and Response Component (this change was applied through-out the document for consistency with the HITSP suite of Interoperability Specifications

4.2 December 18, 2008

Upon approval by the HITSP Panel on December 18, 2008, this document is now Released for Implementation.

4.3 June 30, 2009

The changes in this cycle address the following:

Revised the document based on HITSP/TN903 Data Architecture

Section 2.2 Rules for Implementing

- Addition of Note on usage of HITSP Constraints

Section 2.2.1 Data Mapping

- Added Template Identifier to the Immunization Document

- Added Constraint IDs to identify all HITSP Constraints

3.0 Appendix

- Addition links to all C78 Immunization Data Element and HITSP Constraints

Changes based upon Public Comments

- 7071, 7078, 7114

Minor editorial changes were made to this construct. Removed boilerplate text for simplification. The term actor was replaced with interface.

4.4 July 8, 2009

Upon approval by the HITSP Panel on July 8, 2009, this document is now Released for Implementation.



[1] We have added template identifiers to the document specifications that follow. These template identifiers are recommended be used in exchanges, but are not required due to restrictions on major change. It is possible that these identifiers could be required in future editions of this specification.

[2] Optionality = R for Required, R2 for Required if known, O for Optional, or C# for Conditional.