Allows a Pharmacy to Request a New Prescription for a New Course of Therapy or to Continue Therapy

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 2022011	Final	Feedback requested	Feedback Requested	No	$	No
Implementation Specification	HL7® FHIR® Medication Request	Final	Feedback requested	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 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 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 2021-09-29

NCPDP Comments

NCPDP supports ONC’s recommendations.

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 mattreid on 2019-09-23

HL7 FHIR Medication Request

The American Medical Association appreciates the opportunity to comment. “HL7 FHIR Medication Request” is listed as an emerging standard for a pharmacy. Presumably this is to replace the SCRIPT standard. While HL7 FHIR Medication Request may have potential, we would have concern with the adoption of two different standards creating multiple methods to doing the same thing.

Submitted by carmensmiley on 2019-10-21

HL7 FHIR Medication Request

Thank you for your comment. The ONC Interoperability Standards Advisory is meant to be a reference of available, recognized interoperability standards and implementation specifications, and therefore contains a number of standards for each use case that developers may choose from according to their needs and capabilities.

About the ISA

ISA Content

ISA Sections

Appendices

Specialty Care and Settings

ISA Publications

Recent ISA Updates

Allows a Pharmacy to Request a New Prescription for a New Course of Therapy or to Continue Therapy

Comment

NCPDP Comments

NCPDP Comment

HL7 FHIR Medication Request

HL7 FHIR Medication Request