Allows a Pharmacy to Request a Change to a 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
Final
Feedback requested
Feedback Requested
No
$
No
Implementation Specification
Final
Production
Rating 3
Yes
$
Yes
Limitations, Dependencies, and Preconditions for Consideration
Applicable Security Patterns for Consideration
  • The following transactions need to be implemented for interoperability purposes:
    • SCRIPT 10.6 -
      • RxChg, originated from the pharmacy to request a change in the original prescription.
      • Chgres, originated from the prescriber in response to the RxChg message.
    • SCRIPT 2017071 -
      • RxChangeRequest, originated from the pharmacy to request:
        • a change in the original prescription (new or fillable)
        • validation of prescriber credentials
        • a prescriber to review the drug requested
        • obtaining a prior authorization from the payer for the prescription
      • 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
      • RxChangeResponse, originated from the prescriber to respond:
        • to a prescription change request from a pharmacy
        • to a request for a prior authorization from a pharmacy
        • to a prescriber credential validation request from a pharmacy
      • Options allowed when generating an RxChangeResponse in response to an RxChangeRequest from a pharmacy:
        • Approved: Grant the RxChangeRequest when the prescriber concurs with the request. The prescriber must submit an RxChangeResponse equal to what the pharmacy requested.
        • ApprovedWithChanges: When the information submitted in the RxChangeRequest does not include all elements constituting a fillable prescription; the prescriber should include all information.
        • Denied: Denies the RxChangeRequest with information that explains the denial.
        • Validated: Sent by the prescriber system in response to an RxChangeRequest for prescriber authorization.

The receiving pharmacy should handle Approved, ApprovedWithChanges, and Validated responses as a fillable NewRx where the original linked prescription/order is discontinued. A Denied response should be directed to a review queue where the Denial reason code is displayed.

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.

See NCPDP projects in the Interoperability Proving Ground.

  • 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