Allows a Prescriber to Request a Patient’s Medication History from a State Prescription Drug Monitoring Program (PDMP)

Printer Friendly, PDF & Email
Type Standard / Implementation Specification Standards Process Maturity Implementation Maturity Adoption Level Federally required Cost Test Tool Availability
Emerging Implementation Specification
Feedback requested
Feedback Requested
Implementation Specification
Rating 2
Limitations, Dependencies, and Preconditions for Consideration
Applicable Security Patterns for Consideration
  • The following transactions need to be implemented for interoperability purposes:
    • RxHistoryRequest: a request from a prescriber for a list of medications that have been prescribed, dispensed, claimed or indicated (OTCs) by a patient to a state Prescription Drug Monitoring Program (PDMP).
      • This patient-specific transaction supplies enough information to uniquely identify the patient
    • RxHistoryResponse: a response from a PDMP to an RxHistoryRequest containing a patient’s medication history; includes the medications that were dispensed or obtained within a certain timeframe, optionally including the prescriber that prescribed it
      • PDMP must evaluate the Consent for accurate reporting
      • Returns with loops of Medication, HistorySource (pharmacy), Prescriber, Pharmacy, and Patient elements
      • HistorySource and FillNumber elements are included, when appropriate, so prescribers are able to de-duplicate records from multiple sources that reflect the same medication dispensing, and to help determine patient compliance with a prescription
        • Helps the prescriber determine if follow-up contact is required regarding the medication records
  • RxHistoryRequest and RxHistoryResponse may be sent directly or through an intermediary
  • Both the prescriber and the Prescription Monitoring Drug Program (PDMP) must have their systems configured for the transaction in order to facilitate successful exchange, including the ability to send or receive status, or error transactions.
  • See NCPDP projects in the Interoperability Proving Ground
  • Secure Communication – create a secure channel for client-to- server and server-to-server communication.
  • Secure Message Router – securely route and enforce policy on inbound and outbound messages without interruption of delivery.
  • Authentication Enforcer – centralized authentication processes.
  • Authorization Enforcer – specifies access control policies.
  • Credential Tokenizer – encapsulate credentials as a security token for reuse  (e.g.,  – SAML, Kerberos).
  • Assertion Builder – define processing logic for identity, authorization and attribute statements.
  • User Role – identifies the role asserted by the individual initiating the transaction.
  • Purpose of Use - Identifies the purpose for the transaction.


PDMP Medication History using NCPDP SRIPT v10.6

NCPDP SCRIPT v10.6 was piloted by the S&I Framework and shown to effectively allow a prescriber to inquire into a PDMP using NCPDP's SCRIPT RxHistory request transaction and receive a RxHistory response. It is recommended that this standard be named so that prescriber and pharmacy system vendors can enhance systems so that these entities can obtain PDMP patient information within workflow. SCRIPT version 2017071 has recently been named in a CMS NPRM for comment and includes recommended changes as a result of the 10.6 pilots.