Skip to main content    

An official website of the United States government

Here’s how you know

**Official websites use .gov**              A **.gov** website belongs to an official government organization in the United States.            

**Secure .gov websites use HTTPS**              A **lock** (  LockA locked padlock) or **https://** means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.            

https://www.nist.gov/itl/ssd/systems-interoperability-group/rxhres-release-1-script

            -  Topics  -  All Topics 
-  Advanced communications 
-  Artificial intelligence 
-  Bioscience 
-  Buildings and construction 
-  Chemistry 
-  Climate 
-  Cybersecurity 
-  Electronics 
-  Energy 
-  Environment 
-  Fire 
-  Forensic science 
-  Health 
-  Information technology 
-  Infrastructure 
-  Manufacturing 
-  Materials 
-  Mathematics and statistics 
-  Metrology 
-  Nanotechnology 
-  Neutron research 
-  Performance excellence 
-  Physics 
-  Public safety 
-  Resilience 
-  Standards 
-  Transportation 
 
            -  Publications 
            -  Labs & Major Programs  -  Laboratories    -  Communications Technology Laboratory 
  -  Engineering Laboratory 
  -  Information Technology Laboratory 
  -  Material Measurement Laboratory 
  -  Physical Measurement Laboratory 
-  User Facilities    -  NIST Center for Neutron Research 
  -  CNST NanoFab 
-  Research Test Beds 
-  Research Projects 
-  Tools & Instruments 
-  Major Programs    -  Baldrige Performance Excellence Program 
  -  CHIPS for America Initiative 
  -  Manufacturing Extension Partnership (MEP) 
  -  Office of Advanced Manufacturing 
  -  Special Programs Office 
  -  Technology Partnerships Office 
 
            -  Services & Resources  -  Standards and Measurements    -  Calibration Services 
  -  Laboratory Accreditation (NVLAP) 
  -  Quality System 
  -  Standard Reference Materials (SRMs) 
  -  Standards.gov 
  -  Time Services 
  -  Office of Weights and Measures 
-  Software 
-  Data    -  Chemistry WebBook 
  -  National Vulnerability Database 
  -  Physical Reference Data 
  -  Standard Reference Data (SRD) 
-  Storefront 
-  License & Patents 
-  Computer Security Resource Center (CSRC) 
-  NIST Research Library 
 
            -  News & Events  -  News 
-  Events 
-  Blogs 
-  Feature Stories 
-  Awards 
-  Video Gallery 
-  Image Gallery 
-  Media Contacts 
 
            -  About NIST  -  About Us    -  Leadership 
  -  Organization Structure 
  -  Budget & Planning 
-  Contact Us 
-  Visit 
-  Careers    -  Student programs 
-  Work with NIST 
-  History    -  NIST Digital Archives 
  -  NIST Museum 
  -  NIST and the Nobel 
-  Educational Resources 
 

Information Technology LaboratorySoftware and Systems Division

## Systems Interoperability Group

# RXHRES :: Release 1 :: SCRIPT

## Share

Facebook

Linkedin

Twitter

Email

The following message specification was auto-generated using the Messaging Workbench tool . This specification was auto-generated from a standard-based message profile. The comments and annotations included in this specification are those provided by the message profile authors as implementation notes and notes included in the associated Messaging Workbench file.

For more information about the NCPDP SCRIPT,refer to **National Council for Prescription Drug Programs :** www.ncpdp.org 

## Overview

*The NCI Terminology is available at: http://evs.nci.nih.gov/ftp1/NCPDP/*

*This specification combines the information available in the SCRIPT Implementation  Guide 10.6*
                  - 8. Transmission from sender to receiver structure 
                  - 9. Structure Quick  Reference  
                  - 10. Specific segment discussion 

*This specification is also including an analysis of the changes introduced in version 10.11 of the SCRIPT implementation guide and compares the implementation guide guidance with the XML Schema Descriptions (XSD) provided for XML-encoded SCRIPT messages.*

*A Medication History request (RXHREQ) can be responded to with a Medication History response (RXHRES), a Status message (STATUS), or an Error message (ERROR). Medication History Response (RXHRES) transaction includes Source and Fill Number information so the receiver's system when appropriate to send, so receivers will be able to de-duplicate records from multiple sources that reflect the same medication dispensing, and better determine patient compliance for the medication. The information also assists the receiver if follow-up contact is required regarding the medication records. If more medication history information is available within the date range provided, or if no date range was provided and more medication history information is available, a Response Type, coded (Response Segment 020-1131) 'AQ' of 'More Medication History Available' is returned. For a Medication History Response (RXHRES), in the RES Segment, Response Type, coded (010-4343), the acceptable values are 'A' (Approved) and 'D' (Denied). If the Medication History Request fails, an ERROR message is returned.*

### Notation

The following codes are used in this specification to refer to message element usage and table column names:

### Summary

### Interactions

### MedicationDispensed : MedicationDispensed

*Loops through up to 300 times. Each loop may have 1 corresponding SRC Segment, 2 corresponding PVD Segments, 1 or more than 1 corresponding Sig Segment*

Note that the order of the elements in the XML schema differs from the structure specified in the Implementation Guide. The XML structure requires that the PVD segments for pharmacy and prescriber are interspersed among the  elements of the DRU segment. 

#### Detail

MedicationDispensed

### RES : Response segment used for "NewRxRequestType" XML element

*Designates whether the prescription history was supplied (values accepted or denied supported).*

#### Response segment used for "NewRxRequestType" XML element Detail

### PVDP2 : PVD-P2 Segment to specify the "Pharmacy" XML element

*Provider Segment used for Pharmacy- all its elements are optional.*

This segment specialization appears in the XML structure as "Pharmacy"  XML element. 

#### PVD-P2 Segment to specify the "Pharmacy" XML element Detail

### PVDPC : PVD-PC corresponding to the "Prescriber" XML element

*Provider Segment used for Prescriber- all its elements are optional.*

NOTE: In the SCRIPT implementation guide this is the first PVD, in the XML XSD this information follows the "Pharmacy" PVD- P2 segment. 

#### PVD-PC corresponding to the "Prescriber" XML element Detail

### PTTRXHRES : PTT segment for "Patient" XML element in RXHRES

*PTT for RXHRES, all elements are optional*

#### PTT segment for "Patient" XML element in RXHRES Detail

### COO : Coordination of Benefits segment corresponding to the "BenefitsCoordination" XML element

*Benefit information used to determine plan and help identify the patient. Also contains the date range for the needed history records.*

#### Coordination of Benefits segment corresponding to the "BenefitsCoordination" XML element Detail

### DRU1 : Drug Segment for "MedicationDispensed" XML element

*The fields of this segment are part of the "MedicationDispensed" element. The qualifier 'D' is used to specify 'MedicationDispensed'.*

This segment is interspersed in XML with Pharmacy and Prescriber (PVD) segment fields. 

#### Drug Segment for "MedicationDispensed" XML element Detail

### PVDP2 : PVD-P2 Segment to specify the "Pharmacy" XML element

*Provider Segment used for Pharmacy. This segment specialization appears in the XML structure as "Pharmacy"  XML element.*

Loop for the pharmacy that dispensed the drug in this DRU Loop. This segment is not used when the sender of the Medication History request is a pharmacy. 

#### PVD-P2 Segment to specify the "Pharmacy" XML element Detail

### PVDPC : PVD-PC corresponding to the "Prescriber" XML element

*Loop for the prescriber of the drug in this DRU Loop. This segment specialization appears in the XML structure as "Prescriber" element.*

Loop for the prescriber of the drug in this DRU Loop. 

#### PVD-PC corresponding to the "Prescriber" XML element Detail

### DRU2 : Second set of elements from the Drug Segment as they appear in the "MedicationDispensed" XML element

*The fields of this segment are part of the "MedicationPrescribed" element. Item Description Identification "P" for "MedicationPrescribed" and "D" for "MedicationDispensed".*

This is the second set of fields interspersed with the PVD elements. 

#### Second set of elements from the Drug Segment as they appear in the "MedicationDispensed" XML element Detail

### SIG : "StructuredSIG" XML element corresponds to SIG segment

*The fields of this segment are part of the "MedicationPrescribed" element.*

Backwards compatibility note: the order of the SIG elements was changed in 10.11. 

#### "StructuredSIG" XML element corresponds to SIG segment Detail

### SRC : Source Segment (Prescriber) represented as "HistorySource" XML element

#### Source Segment (Prescriber) represented as "HistorySource" XML element Detail

Health IT

### HEADQUARTERS

301-975-2000

Webmaster | Contact Us | Our Other Offices

TwitterFacebookLinkedInInstagramYouTubeGiphyRSS FeedMailing List

Feedback

            -  Site Privacy 
            -  Accessibility 
            -  Privacy Program 
            -  Copyrights 
            -  Vulnerability Disclosure 
            -  No Fear Act Policy 
            -  FOIA 
            -  Environmental Policy 
            -  Scientific Integrity 
            -  Information Quality Standards 
            -  Commerce.gov 
            -  Science.gov 
            -  USA.gov 
            -  Vote.gov