Allows a Pharmacy to Request, Respond to or Confirm a Prescription Transfer

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 2013101	Final	Production		No	$	No
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 2017071	Final	Production		No	$	Yes
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 2022011	Final	Feedback requested	Feedback Requested	No	$	No
Implementation Specification	NCPDP SCRIPT Standard, Implementation Guide, Version 2023011	Final	Feedback requested	Feedback Requested	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: RxTransferRequest: Used when the pharmacy is asking for a transfer of one or more prescriptions for a specific patient to the requesting pharmacy. The transfer is for a fillable prescription which may be: Yet to be filled. On hold. Open (active) fills. Current therapy (defined as drug therapy that, based upon the most recent fill date, quantity and instructions, should still be active). Allowed to be transferred by law/regulation. If multiple specific prescriptions are to be transferred, but not all prescriptions, a separate RxTransferRequest must be sent for each specific prescription. RxTransferResponse: The response from the transferring pharmacy to the requesting pharmacy to the RxTransferRequest, which includes the prescription(s) being transferred or a rejection of the transfer request. RxTransferConfirm: Used by the pharmacy receiving (originally requesting) the transfer to confirm that the transfer prescription has been received and the transfer is complete. The RxFill Transaction <FillStatus><Transferred> is originated by the transferring pharmacy once the <RxTransferConfirm> is received from the transfer to pharmacy. This transaction is used to notify the prescriber when a prescription has been transferred to another pharmacy and can no longer be filled at the original pharmacy. The RxTransfer transaction will identify if the receiving pharmacy supports RxFill. Both pharmacies 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 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:
- RxTransferRequest: Used when the pharmacy is asking for a transfer of one or more prescriptions for a specific patient to the requesting pharmacy.
  - The transfer is for a fillable prescription which may be:
    - Yet to be filled.
    - On hold.
    - Open (active) fills.
    - Current therapy (defined as drug therapy that, based upon the most recent fill date, quantity and instructions, should still be active).
    - Allowed to be transferred by law/regulation.
  - If multiple specific prescriptions are to be transferred, but not all prescriptions, a separate RxTransferRequest must be sent for each specific prescription.
- RxTransferResponse: The response from the transferring pharmacy to the requesting pharmacy to the RxTransferRequest, which includes the prescription(s) being transferred or a rejection of the transfer request.
- RxTransferConfirm: Used by the pharmacy receiving (originally requesting) the transfer to confirm that the transfer prescription has been received and the transfer is complete.
The RxFill Transaction <FillStatus><Transferred> is originated by the transferring pharmacy once the <RxTransferConfirm> is received from the transfer to pharmacy. This transaction is used to notify the prescriber when a prescription has been transferred to another pharmacy and can no longer be filled at the original pharmacy. The RxTransfer transaction will identify if the receiving pharmacy supports RxFill.
Both pharmacies 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 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 2013101

Submitted by pwilson@ncpdp.org on 2021-09-29

NCPDP Comments

NCPDP SCRIPT Standards, Implementation Guide, Version 2017071 update adoption level to 1.

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

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. RxTransferConfirm Transaction
2. RxTranferResponse Transaction
3. RxTransferRequest 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. We also recommend including NCPDP SCRIPT Standard Implementation Guide Version 2013101.

About the ISA

ISA Content

ISA Sections

Appendices

Specialty Care and Settings

ISA Publications

Recent ISA Updates

Allows a Pharmacy to Request, Respond to or Confirm a Prescription Transfer

Comment

NCPDP Comments

NCPDP Comments

NCPDP Comment

NCPDP Comment

NCPDP Comment

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

Connect with us: