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 cycle address the following comments received during the September 29th through October 24th, 2008 public review and comment period.

No comments were received.

Minor editorial changes were made to this document.

4.1.1 Section 2.2.1 Data Mapping

Added clarification as to where the reader should go to find all constraints applied to the data.

Expanded the Note for Table 2-3 and Table 2-4 to define the values used in the Repeatable Entry column.

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

Revised the document based on HITSP/TN903 Data Architecture

4.3.1 General Updates

Section 2.2 Rules for Implementing: Addition of Note on usage of HITSP Constraints

Section 2.2.1 Data Mapping: Added Template Identifiers to Consultation Note, and History and Physical Note. Added Constraint IDs to identify all HITSP Constraints

Section 3.0 Appendix: Added links to all HITSP/C84 Encounter Data Elements and HITSP Constraints

The changes in this construct address the following comments received via the HITSP comment tracking system.

7071, 7078

The full text of the comments along with the Technical Committees disposition can be reviewed on the HITSP Public Web Site.

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 or O for Optional, or C for

Conditional. Repeatable = Y for yes, N for No.

[3] See HITSP/C83 for information regarding the repeatability of Data Elements with a Section.

[4] Optionality = R for Required, R2 for Required if Known or O for Optional, or C for

Conditional. Repeatable = Y for yes, N for No.

[5] See HITSP/C83 for information regarding the repeatability of Data Elements with a Section.