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

Type	Standard / Implementation Specification	Standards Process Maturity	Implementation Maturity	Adoption Level	Federally required	Cost	Test Tool Availability
Standard	PMIX *, Version 2	Final	Production		No	Free	No
Standard	SMART® on FHIR®	Final	Production		No	Free	Yes
Standard	CDS Hooks™ Services	Final	Production		No	Free	Yes
Implementation Specification	NCPDP® SCRIPT Standard Implementation Guide Version 2017071	Final	Production		No	$	No
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 2022011	Final	Pilot		No	$	No
Standard	HL7®, Version 2	Final	Production	Feedback Requested	No	Free	No
Implementation Specification	HL7 FHIR® Implementation Guide: US Meds STU2	Balloted Draft	Pilot	Feedback Requested	No	Free	No
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 2023011	Final	Feedback requested	Feedback Requested	No
Emerging Standard	HL7 FHIR SMART Application Launch Framework Implementation Guide Release 2.0.0	Final	Production	Feedback Requested	No	Free	Yes

Limitations, Dependencies, and Preconditions for Consideration	Applicable Security Patterns for Consideration
Please refer to CMS.gov for more information regarding Medicare Part D electronic prescribing requirements and sign up to receive the latest announcements. The following NCPDP SCRIPT 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 it includes the prescriber's name. 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. The medication history response transaction in SCRIPT Version 2017071 has been enhanced to return data from Prescription Drug Monitoring Program (PDMP) administrators. Please note that the NCPDP electronic prescribing test tool does not currently test the capabilities of any health IT to exchange data with a state PDMP. 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. The HL7 FHIR Implementation Guide: US Meds STU2 includes US Meds Prescription Drug Monitoring Program (PDMP) mapping. SMART on FHIR defines a mechanism for interoperable “SMART Apps” that can be plugged in to EHRs and other Health IT systems. Each SMART App can expose a user interaction and can access data in the underlying system. This presents a powerful way to extend EHR capabilities via “pluggable” app functionality. Dozens of SMART apps are available, including apps for medication management, pain management, and PDMP-EHR integration, with more expected in the future. These apps serve many different clinical needs, yet they all use the same underlying FHIR-based API functionality. When using the SMART on FHIR model, the authentication model uses OAuth2. Except for "Secure Communication", the security patterns listed do not apply. The HL7 FHIR® SMART Application Launch Framework Implementation Guide Release 2.0.0 is a newer version of the standard that is available for health IT developers to voluntarily update and provide to their customers. It became available when it was added to the Approved Standards for 2022 through ONC’s Standards Version Advancement Process (SVAP). * PMIX is not an ANSI-Accredited Standards Developer. For more information, see www.ansi.org.	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.

Limitations, Dependencies, and Preconditions for Consideration

Applicable Security Patterns for Consideration

Please refer to CMS.gov for more information regarding Medicare Part D electronic prescribing requirements and sign up to receive the latest announcements.
The following NCPDP SCRIPT 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 it includes the prescriber's name.
  - 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.
The medication history response transaction in SCRIPT Version 2017071 has been enhanced to return data from Prescription Drug Monitoring Program (PDMP) administrators.
Please note that the NCPDP electronic prescribing test tool does not currently test the capabilities of any health IT to exchange data with a state PDMP.
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.
The HL7 FHIR Implementation Guide: US Meds STU2 includes US Meds Prescription Drug Monitoring Program (PDMP) mapping.
SMART on FHIR defines a mechanism for interoperable “SMART Apps” that can be plugged in to EHRs and other Health IT systems. Each SMART App can expose a user interaction and can access data in the underlying system. This presents a powerful way to extend EHR capabilities via “pluggable” app functionality. Dozens of SMART apps are available, including apps for medication management, pain management, and PDMP-EHR integration, with more expected in the future. These apps serve many different clinical needs, yet they all use the same underlying FHIR-based API functionality.
When using the SMART on FHIR model, the authentication model uses OAuth2. Except for "Secure Communication", the security patterns listed do not apply.
The HL7 FHIR® SMART Application Launch Framework Implementation Guide Release 2.0.0 is a newer version of the standard that is available for health IT developers to voluntarily update and provide to their customers. It became available when it was added to the Approved Standards for 2022 through ONC’s Standards Version Advancement Process (SVAP).

* PMIX is not an ANSI-Accredited Standards Developer. For more information, see www.ansi.org.

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.

Comment

Submitted by pwilson@ncpdp.org on 2024-08-13

NCPDP Comment

NCPDP recommends removing NCPDP SCRIPT Standard, Implementation Guide, Version 2022011, as this version was never implemented. NCPDP SCRIPT Standard Implementation Guide, Version 2023011 is the next version named by ASTP/ONC and Medicare. Federally required should be changed to a Yes for the NCPDP SCRIPT Standard Implementation Guide, Version 2023011.

Submitted by pwilson@ncpdp.org on 2023-10-06

NCPDP Comment

NCPDP recommends that ONC add the following:

Type- Implementation Specification

Standard Implementation/Specification- NCPDP SCRIPT Standard, Implementation Guide, Version 2022011

Standards Process Maturity – Final

Implementation Maturity- Pilot

Adoption Level – 1

Federally Required – No

Cost – $

Test Tool Availability – No

Submitted by shellyspiro on 2023-10-02

Pharmacy HIT Collaborative (PHIT) comment

PHIT supports NCPDP’s recommendation to add NCPDP SCRIPT Standard, Implementation Guide, Version 2022011.

Submitted by pwilson@ncpdp.org on 2022-09-30

NCPDP Comments

NCPDP recommends to sunset NCPDP SCRIPT Standard Implementation Guide Version 10.6
NCPDP recommends to sunset NCPDP SCRIPT Standard Implementation Guide Version 2013101

Submitted by chris.baumgart… on 2022-09-20

WA State Department of Health PDMP Comments

Washington State Department of Health appreciates having the standards listed on the PDMP pages and does not have any recommended changes at this time.

Submitted by chris.baumgart… on 2021-09-29

WA State Department of Health PDMP Comments

Washington State Department of Health appreciates having the standards listed on the PDMP pages and does not have any recommended changes at this time.

Submitted by pwilson@ncpdp.org on 2021-09-29

NCPDP Comments

Sunset NCPDP SCRIPT Implementation Guide Version 10.6

Submitted by pwilson@ncpdp.org on 2021-09-29

NCPDP Comments

NCPDP supports ONC’s recommendations.

Submitted by pwilson@ncpdp.org on 2020-11-07

NCPDP Comment

Modify NCPDP SCRIPT Standard, Implementation Guide, Version 2017071 test tool to Yes
Include Test Tool Link: https://tools.ncpdp.org/erx/#/home

Submitted by pwilson@ncpdp.org on 2019-09-23

NCPDP Comment

For NCPDP SCRIPT Standard, Implementation Guide, Version 10.6, modify testing tool availability to Yes. Test Tool Link: https://tools.ncpdp.org/erx/#/home
For NCPDP SCRIPT Standard, Implementation Guide, Version 2017071, modify testing tool availability to Yes. Test Tool Link: https://tools.ncpdp.org/erx/#/home
NCPDP SCRIPT Standard is a mature standard that can alleviate identified interoperability issues.