Allows a Prescriber to Send a New Prescription to a Pharmacy

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 10.6	Final	Production		Yes	$	Yes
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 2017071	Final	Production		Yes	$	Yes
Emerging Standard	HL7 FHIR Medication Request	In Development	Pilot	Feedback Requested	No	Free	No

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 transactions need to be implemented for interoperability purposes: SCRIPT 10.6 & SCRIPT 2017071 - NewRx: This transaction is a new prescription sent from the prescriber to the pharmacy electronically so that it can be dispensed to a patient SCRIPT 2017071 - NewRxRequest: This transaction is a request from a pharmacy to a prescriber for a new prescription for a patient NewRxResponseDenied: This transaction is a denied response to a previously sent NewRxRequest (If approved, a NewRx would be sent) A NewRxResponseDenied response may occur when the NewRxRequest cannot be processed or if information is unavailable Both the prescriber and the pharmacy must have their systems configured for the transaction in order to facilitate successful exchange, including the ability to send or receive verify, status, or error transactions. See NCPDP projects in the Interoperability Proving Ground.	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 transactions need to be implemented for interoperability purposes:
- SCRIPT 10.6 & SCRIPT 2017071 -
  - NewRx: This transaction is a new prescription sent from the prescriber to the pharmacy electronically so that it can be dispensed to a patient
- SCRIPT 2017071 -
  - NewRxRequest: This transaction is a request from a pharmacy to a prescriber for a new prescription for a patient
    - NewRxResponseDenied: This transaction is a denied response to a previously sent NewRxRequest (If approved, a NewRx would be sent)
      - A NewRxResponseDenied response may occur when the NewRxRequest cannot be processed or if information is unavailable
Both the prescriber and the pharmacy must have their systems configured for the transaction in order to facilitate successful exchange, including the ability to send or receive verify, status, or error transactions.
See NCPDP projects in the Interoperability Proving Ground.

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 2017-11-20

NCPDP - Comments on Version 10.6

The adoption level should be modified to a 5

Submitted by shellyspiro on 2018-10-01

Pharmacy HIT Collaborative's Comments on ONC's Proposed 2018 ISA

The Pharmacy HIT Collaborative supports the move to NCPDP SCRIPT Version 2017071 as soon as participants can reasonably be ready to implement such a change. The Collaborative supports the use of NCPD Script Standard, Implementation Guide, Version 10.6.

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

NCPDP Comment

This topic needs to be broken into three categories:
1. A Pharmacy requests a prescription for a new course of therapy.
2. A Pharmacy requests a new prescription to continue therapy.
3. Where a prescriber sends a new prescription to a pharmacy.
Items 1 + 2 are available currently with adoption level of 5.
Item three is available in SCRIPT 2017071:
1. NewRxResponseDenied Transaction
2. NewRxRequest Transaction

Add the following:

Type-Implementation Specification

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

Standards Process Maturity – Final

Implementation Maturity- Pilot

Adoption Level – 1

Federally Required – No

Cost – $

Test Tool Availability – Yes.

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

NCPDP Comment

Update the following:

Type-Implementation Specification Standard Implementation/Specification- NCPDP SCRIPT Standard, Implementation Guide, Version 2017071 Implementation Maturity- Production (effective 1/1/2020) Test Tool Availability – Yes Test Tool Link: https://tools.ncpdp.org/erx/#/home