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 Dr.Bryant on 2018-10-01

PDMP Standards

The Washington State Department of Health (DOH) appreciates the opportunity to submit these comments in response to the Office of the National Coordinator for Health Information Technology (ONC) request for public comments regarding the Interoperability Standards Advisory (ISA). DOH operates the Prescription Drug Monitoring Program (PDMP) in the state of Washington. DOH supports the proposed switch to the National Council for Prescription Drug Programs (NCPDP) 2017-071; however, DOH respectfully requests that the proposed deadline to implement NCPDP 2017-071 be extended to ensure that small to medium sized providers and critical access hospitals have a reasonable period of time to implement.

DOH supports NCPDP 2017-071 and recognizes the benefits, including allowing the system to query the PDMP more than once every 24 hours (which is the current maximum), and allowing the system to send dispense level patient information. A previously adopted Centers for Medicare and Medicaid Services (CMS) rule, CMS-4182-F (Changes to the Medicare Advantage Prescription Drug Benefit Program, aka Medicare part D), required adoption of NCPDP 2017-071 for e-prescribing by January 1, 2020. By moving toward adoption of NCPDP 2017-071, the health care system will keep PDMP in harmony with other federal regulations.

DOH supports the switch to NCPDP 2017-071, but we want to ensure that the deadline to do so is feasible. Currently, Washington State cannot accept NCPDP 2017-071 queries, as DOH’s system uses NCPDP 10.6 for the PDMP. NCPDP 2017-071 is not backward compatible with NCPDP 10.6. DOH staff contacted our electronic medical record vendors and the vendors indicated their certified Health IT software that meet these new requirements will be released in summer of 2019. Hospitals’ adoption of this new version will occur in a rolling adoption period after the release date. For DOH’s PDMP system, we hope to be able to begin the switch to NCPDP 2017-071 by January 1, 2020. DOH anticipate needing to support both NCPDP 2017-071 as well as 10.6, for a transition period from January 1, 2020 through approximately January 1, 2021, assuming not all providers convert simultaneously.

In addition, DOH believes it would also be helpful for CMS to clarify whether, if the community pharmacy could not accept the prescription due to the different versions, this would be considered an exclusion for the hospital to maintain both versions. DOH recommends that CMS consider providing administrative support for public health, community pharmacies, small- to medium-sized providers, and critical access hospitals to upgrade to NCPDP 2017-071. If communities do not have the resources or incentives to upgrade, it will be crucial for PDMP systems to support both versions during this transition period.

The proposed deadline to implement NCPDP version 2017-071 should be extended to ensure that PDMP systems and the health care system have a reasonable period of time to implement. DOH recommends that the ISA allow for NCPDP v10.6 grandfathering until January 1, 2021.

Sincerely,

John Wiesman, DrPH, MPH

Secretary of Health

Washington State Department of Health

Submitted by pwilson@ncpdp.org on 2018-10-01

NCPDP Comment

NCPDP supports the use of the NCPDP SCRIPT RxHistoryRequest/RxHistoryResponse transactions for PDMP.
For NCPDP SCRIPT Standard, Implementation Guide, Version 10.6, modify testing tool availability to Yes.

Submitted by shellyspiro on 2018-10-01

The Pharmacy HIT Collaborative supports the use of NCPDP SCRIPT

The Pharmacy HIT Collaborative supports the use of NCPDP SCRIPT Standard, Implementation Guide Versions 10.6, as well as the move to NCPDP SCRIPT Standards, Implementation Guide, Version 2017071 and HL7 FHIR Implementation Guide, US Meds STU2 as soon as participants can be ready to implement such a change. We also recommend including NCPDP SCRIPT Standard Implementation Guide Version 2013101.

Submitted by pwilson@ncpdp.org on 2017-12-15

NCPDP Comment on Version 10.6

NCPDP supports the naming of the SCRIPT standard for PDMP.

Submitted by cgraeff on 2017-12-12

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.