Allows a Pharmacy to Request Additional Refills

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		Yes	$	Yes
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 10.6	Final	Production		No	$	N/A
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 2022011	Final	Feedback requested	Feedback Requested	No	$	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 2017071 - RxRenewalRequest, originated from the pharmacy to request additional refills beyond those originally prescribed. (Within the RxRenewalRequest) FollowUpRequest, originated from the pharmacy to: Notify prescribers that this is a follow-up RxRenewalRequest or RxChangeRequest transaction, when the prescriber has not responded to the first RxRenewalRequest or first RxChangeRequest transaction in a reasonable amount of time. Not sent on the original request of the RxRenewalRequest or RxChangeRequest transaction. RxRenewalResponse, originated from the prescriber to respond to the request. Options allowed when generating an RxRenewalResponse to an RxRenewalRequest from a pharmacy: Approved: Grant the RxRenewalRequest as requested by the pharmacy, or, when the pharmacy does not request a specific number of fills (PharmacyRequestedRefills is not present) and the prescriber approves any number of fills. ApprovedWithChanges: Grant the RxRenewalRequest, approving a NumberOfRefills different than the number requested by the pharmacy or when the information submitted in the RxRenewalRequest does not include all elements constituting a fillable prescription; the prescriber should include all information. Denied: Deny the RxRenewalRequest as requested by the pharmacy. In a Denied response, the only new meaning that should be conveyed to the pharmacy is information that explains the denial. It is recommended that the prescribing software update the NumberOfRefills to zero and leave all other data as is in the RxRenewalResponse. Replace: Data is allowed to be changed except the patient DateOfBirth. If patient DateOfBirth changes, a Denied response would be sent, and then a NewRx would follow. The receiving pharmacy might handle each of these responses differently. Approved, ApprovedWithChanges, and Replace responses might be directed to a fulfillment queue, where a Denied response might be directed to a review queue. The Replace response should be used if there are any changes beyond what is outlined in the Response Element. RxRenewalRequest should never be responded to with a NewRx, as this would result in duplicate valid prescriptions. DeniedNewPrescriptionToFollow response is not to be sent in an RxRenewalResponse for this version of SCRIPT. However, the DeniedNewPrescriptionToFollow response could be received in an RxRenewalResponse from a previous version of SCRIPT and is included for backwards compatibility. DeniedNewPrescriptionToFollow response only exists for entities that need to map this version to a previous version of SCRIPT that does not support a Replace. Both the pharmacy and the prescriber 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.	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 transactions need to be implemented for interoperability purposes:
- SCRIPT 2017071 -
  - RxRenewalRequest, originated from the pharmacy to request additional refills beyond those originally prescribed. (Within the RxRenewalRequest) FollowUpRequest, originated from the pharmacy to:
    - Notify prescribers that this is a follow-up RxRenewalRequest or RxChangeRequest transaction, when the prescriber has not responded to the first RxRenewalRequest or first RxChangeRequest transaction in a reasonable amount of time.
    - Not sent on the original request of the RxRenewalRequest or RxChangeRequest transaction.
    - RxRenewalResponse, originated from the prescriber to respond to the request.
  - Options allowed when generating an RxRenewalResponse to an RxRenewalRequest from a pharmacy:
    - Approved: Grant the RxRenewalRequest as requested by the pharmacy, or, when the pharmacy does not request a specific number of fills (PharmacyRequestedRefills is not present) and the prescriber approves any number of fills.
    - ApprovedWithChanges: Grant the RxRenewalRequest, approving a NumberOfRefills different than the number requested by the pharmacy or when the information submitted in the RxRenewalRequest does not include all elements constituting a fillable prescription; the prescriber should include all information.
    - Denied: Deny the RxRenewalRequest as requested by the pharmacy.
    - In a Denied response, the only new meaning that should be conveyed to the pharmacy is information that explains the denial. It is recommended that the prescribing software update the NumberOfRefills to zero and leave all other data as is in the RxRenewalResponse.
    - Replace: Data is allowed to be changed except the patient DateOfBirth. If patient DateOfBirth changes, a Denied response would be sent, and then a NewRx would follow.
    - The receiving pharmacy might handle each of these responses differently. Approved, ApprovedWithChanges, and Replace responses might be directed to a fulfillment queue, where a Denied response might be directed to a review queue.
    - The Replace response should be used if there are any changes beyond what is outlined in the Response Element.
  - RxRenewalRequest should never be responded to with a NewRx, as this would result in duplicate valid prescriptions.
  - DeniedNewPrescriptionToFollow response is not to be sent in an RxRenewalResponse for this version of SCRIPT. However, the DeniedNewPrescriptionToFollow response could be received in an RxRenewalResponse from a previous version of SCRIPT and is included for backwards compatibility. DeniedNewPrescriptionToFollow response only exists for entities that need to map this version to a previous version of SCRIPT that does not support a Replace.
Both the pharmacy and the prescriber 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.

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 2022-09-30

NCPDP Comments

NCPDP recommends to sunset NCPDP SCRIPT Standard Implementation Guide Version 10.6

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

Update the following:

Type-Implementation Specification Standard Implementation/Specification- NCPDP SCRIPT Standard, Implementation Guide, Version 2017071 Adoption Level - 5

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

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

NCPDP Comment

Add the following:
1. RxRenwalResponse Transaction
2. RxRenewalRequest Transaction

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

About the ISA

ISA Content

ISA Sections

Appendices

Specialty Care and Settings

ISA Publications

Recent ISA Updates

Allows a Pharmacy to Request Additional Refills

Comment

NCPDP Comments

NCPDP Comments

NCPDP Comments

NCPDP Comment

NCPDP Comment

NCPDP Comment

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

Connect with us: