Allows a Prescriber or a Pharmacy to Request a New Prescription

Printer Friendly, PDF & Email
Type Standard / Implementation Specification Standards Process Maturity Implementation Maturity Adoption Level Federally required Cost Test Tool Availability
Emerging Implementation Specification
Feedback requested
Feedback Requested
Implementation Specification
Rating 5
Limitations, Dependencies, and Preconditions for Consideration
Applicable Security Patterns for Consideration
  • The following transactions need to be implemented for interoperability purposes:
    • 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.