Allows for the Exchange of State Prescription Drug Monitoring Program (PDMP) Data

Type	Standard / Implementation Specification	Standards Process Maturity	Implementation Maturity	Adoption Level	Federally required	Cost	Test Tool Availability
Standard	2015 ASAP Prescription Monitoring Program Web Service Standard 2.1A	Final	Production		No	Free	No
Standard	2011 ASAP Version 4.2 Standard for Prescription Monitoring Programs	Final	Production		No	Free	No
Standard	PMIX,* Version 2	Final	Production		No	Free	No
Standard	2010 ASAP Prescription Monitoring Program Standards Versions 1.0 for PMP Zero Reports and Error Reports	Final	Production		No	Free	No
Implementation Specification	NIEM, Version 3.2	Final	Production		No	Free	No
Standard	2017 ASAP Version 4.2A Standard for Prescription Monitoring Programs	Final	Production		No	Free	No
Standard	HL7®, Version 2	Final	Production	Feedback Requested	No	Free	No
Standard	NCPDP® Telecommunication Standard,Version D.0	Final	Production	Feedback Requested	No	$	No
Standard	2020 ASAP Version 4.2B Standard for Prescription Monitoring Programs	Final	Pilot	Feedback Requested	No	Free	No
Implementation Specification	NCPDP SCRIPT Standard Implementation Guide Version 2017071	Final	Production		No	$	No
Implementation Specification	NCPDP Prescription Drug Monitoring Programs Reporting Standard, Implementation Guide, Version 12	Final	Production	Feedback Requested	No	$	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	Yes
Implementation Specification	NCPDP Telecommunication Standard, Version F6	Final	Pilot	Feedback Requested	No	$	No
Implementation Specification	2023 ASAP Version 5.0 Standard for Prescription Drug Monitoring Programs	Final	Production	Feedback Requested	No	$

Limitations, Dependencies, and Preconditions for Consideration	Applicable Security Patterns for Consideration
National Drug Code (NDC) The use of NDC in conjunction with RxNorm can help minimize gaps in representing medications, including compounded products, over -the-counter medications, and herbals. RxNorm RxNorm is often used for the exchange of information; however, it may not be available for export and import by end users. RxNav NDC mappings are available through RxNorm via RxNav. Please note that many of the standards, emerging standards, and implementation specifications outlined above are specific to the in-state and interstate exchange of PDMP data. See the PDMP query ISA page for a working list of standards, emerging standards, and implementation specifications specific to a provider's ability to query a PDMP from health information technology such as an EHR. Data may be exchanged directly or through an intermediary. Prescribers, Dispensers, Prescription Monitoring Drug Program (PDMPs), and other intermediaries and endpoints 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. If a state PDMP requests either ASAP 4.2, 4.2A, or 4.2B, these versions of the standard includes the Zero Reports and Error Reports standard. ASAP 4.2, 4.2A, 4.2B, and the Zero Reports and Error Reports are also available as separate standards. All of the ASAP standards are free to non-commercial and non-profit entities such as state PDMPs. The HL7 FHIR Implementation Guide: US Meds STU2 includes US Meds Prescription Drug Monitoring Program (PDMP) standards mapping. * 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

National Drug Code (NDC)
- The use of NDC in conjunction with RxNorm can help minimize gaps in representing medications, including compounded products, over -the-counter medications, and herbals.
RxNorm
- RxNorm is often used for the exchange of information; however, it may not be available for export and import by end users.
RxNav
- NDC mappings are available through RxNorm via RxNav.

Please note that many of the standards, emerging standards, and implementation specifications outlined above are specific to the in-state and interstate exchange of PDMP data. See the PDMP query ISA page for a working list of standards, emerging standards, and implementation specifications specific to a provider's ability to query a PDMP from health information technology such as an EHR.
Data may be exchanged directly or through an intermediary. Prescribers, Dispensers, Prescription Monitoring Drug Program (PDMPs), and other intermediaries and endpoints 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.
If a state PDMP requests either ASAP 4.2, 4.2A, or 4.2B, these versions of the standard includes the Zero Reports and Error Reports standard. ASAP 4.2, 4.2A, 4.2B, and the Zero Reports and Error Reports are also available as separate standards.
All of the ASAP standards are free to non-commercial and non-profit entities such as state PDMPs.
The HL7 FHIR Implementation Guide: US Meds STU2 includes US Meds Prescription Drug Monitoring Program (PDMP) standards mapping.

* 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.
NCPDP recommends that ASTP/ONC update NCPDP Prescription Drug Monitoring Programs Reporting Standard, Implementation Guide to Version 15.

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

NCPDP Comment

NCPDP recommends that ONC update NCPDP Prescription Drug Monitoring Programs Reporting Standard, Implementation Guide to Version 15.
NCPDP recommends that ONC update “NCPDP Telecommunication Standard, Version D” to “NCPDP Telecommunication Standard, Version D.0”.
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

NCPDP recommends that ONC add the following:

Type- Implementation Specification

Standard Implementation/Specification- NCPDP Telecommunication Standard, Version F6

Standards Process Maturity – Pilot

Implementation Maturity- Feedback Requested

Adoption Level – Feedback Requested

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 update NCPDP Prescription Drug Monitoring Programs Reporting Standard, Implementation Guide to Version 15; updating NCPDP Telecommunication Standard, Version D to NCPDP Telecommunication Standard, Version D.0.

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

NCPDP Comments

NCPDP recommends to sunset NCPDP SCRIPT Standard Implementation Guide Version 10.6

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 Standard, Implementation Guide, Version 10.6

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

NCPDP Comment

Update the following:

Type-Implementation Specification

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

Implementation Maturity – Production

Adoption Level – 1

Test Tool Availability – Yes

For NCPDP SCRIPT Standard, Implementation Guide Version 2017071 add Test Tool Link: https://tools.ncpdp.org/erx/#/home
Remove Implementation Specification: NCPDP SCRIPT Standard, Implementation Guide, Version 10.6

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

NCPDP Comment

NCPDP SCRIPT Standard Implementation Guide, Version 2017071 and the NCPDP Telecommunication Standard Implementation Guide, Version D.0 are mature standards that can alleviate identified interoperability issues.
Update the following:

Type-Implementation Specification

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

Implementation Maturity – Production

Adoption Level – N/A

Test Tool Availability – Yes

Test Tool Link: https://tools.ncpdp.org/erx/#/home