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
Implementation Specification	NCPDP SCRIPT Standard Implementation Guide Version 2017071	Final	Production		No	$	No
Implementation Specification	NCPDP SCRIPT Standard Implementation Guide Version 10.6	Final	Production		No	$	No
Implementation Specification	NCPDP Prescription Drug Monitoring Programs Reporting Standard, Implementation Guide, Version 12	Final	Production	Feedback Requested	No	$	No
Standard	NCPDP Telecommunication Standard,Version D	Final	Production	Feedback Requested	No	$	No
Implementation Specification	NIEM, Version 3.2	Final	Production		No	Free	No
Standard	PMIX, Version 2	Final	Production		No	Free	No
Standard	2020 ASAP Version 4.2B Standard for Prescription Monitoring Programs	Final	Pilot	Feedback Requested	No	Free	No
Standard	2017 ASAP Version 4.2A Standard for Prescription Monitoring Programs	Final	Production		No	Free	No
Standard	2011 ASAP Version 4.2 Standard for Prescription Monitoring Programs	Final	Production		No	Free	No
Standard	2015 ASAP Prescription Monitoring Program Web Service Standard 2.1A	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
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

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.	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.

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 [email protected] on 2021-09-29

NCPDP Comments

Sunset NCPDP SCRIPT Standard, Implementation Guide, Version 10.6

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.

About the ISA

ISA Content

ISA Sections

Appendices

Specialty Care and Settings

ISA Publications

Recent ISA Updates

21st Century Cures

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

Comment

NCPDP Comments

WA State Department of Health PDMP Comments