Allows a Prescriber to Cancel 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 2
Yes
$
Yes
Limitations, Dependencies, and Preconditions for Consideration Applicable Value Set(s) and Starter Set(s)
  • The following transactions need to be implemented for interoperability purposes:
    • SCRIPT 10.6 -
      • CanRx: a request from a prescriber to a pharmacy to not fill a previously sent prescription.
      • CanRes: a response from a pharmacy to a prescriber to acknowledge a cancel request; the response to a CanRx.
    • SCRIPT 2017071 -
      • CancelRx: a request from the prescriber to the pharmacy to not fill a previously sent prescription
        • must contain pertinent information for the pharmacy to be able to find the prescription in their system (patient, medication (name, strength, dosage form), prescriber, prescription number if available)
        • changes can be indicated in the MessageRequestCode in the CancelRx transaction
      • CancelRxResponse: a response from the pharmacy to the prescriber to acknowledge a CancelRx
        • used to denote if the cancellation is Approved or Denied
        • DenialReasonCode should be sent when a CancelRx is denied
      • When a Long Term care (LTC) prescriber has the need to modify an order and notify the pharmacy, the prescriber system will always send a CancelRx and a NewRx, regardless of the type of change

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