4.0Change History

The following sections provide the history of changes made to this document.

4.1 December 7, 2007

No changes. This is the first published version of the document.

4.2 March 19, 2008

The changes in this cycle address the following comments:

3007, 3050, 3070, 3223, 3225, 3226, 3227

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

The following changes have been made to the construct:

Made editorial changes based on comments

Added text to clarify construct is used for new prescriptions, refills and renewals

Removed constraint on RXFILL PTT segment Gender, coded field

Removed constraint on RXFILL DRU segment Free Text Code list Qualifier field requiring use of FMT coded values

Added text to clarify that construct isnt used for paper prescriptions

Added TP43 - Medication Orders as a pre-requisite

Removed trigger A request for medication dispensing status is received by Medication Status Dispenser

Set Requirements column in Table Table 2-7 to R, R2, C or O as appropriate

Deleted the requirement for NCPDP to use X12 codes for Drug Form, Strength, etc.

4.3 March 27, 2008

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

4.4 August 20, 2008

This document has been modified to reflect the updated HITSP approach to categorizing standards as Regulatory Guidance, Selected Standards, and Informative References.

Removed the following from list of standards:

Federal Medication Terminologies

National Library of Medicine (NLM) Unified Medical Language System (UMLS) RxNorm

4.5 August 27, 2008

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

4.6 June 30, 2009

Minor editorial changes were made to this document. Boilerplate text was removed for simplification. The term actor was replaced with interface.

4.7 July 8, 2009

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

[1] Above HITSP constraints have been discussed with NCPDP members and are expected to be incorporated into the NCPDP SCRIPT Standard Implementation Guide in a future version.

[2] Neither NCPDP SCRIPT 8.1, nor 10.1 supports the use of Federal Medication Terminology (FMT) coded fields for Drug Form, Drug Strength and Drug Unit of Measure. This will be considered in future versions.

[3] Optionality = R for Required, R2 for Required if Known or O for Optional, or C for Conditional. Conditional footnotes are further described below.

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

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