Allows the Pharmacy to Respond to Prescriber with a Change on a New Prescription

Printer Friendly, PDF & Email
Type Standard Implementation/Specification Standards Process Maturity Implementation Maturity Adoption Level Federally required Cost Test Tool Availability
Implementation Specification
Final
Production
Rating 2
Yes
$
Yes
Limitations, Dependencies, and Preconditions for Consideration Applicable Security Patterns for Consideration

 

  • The RxChange message allows a Pharmacist to request a change of a new prescription or a “fillable” prescription.
  • Both the prescriber and the receiving pharmacy must have their systems configured for the transaction in order to facilitate successful exchange

  • See NCPDP projects in the Interoperability Proving Ground.

 

  • Secure Communication – create a secure channel for client-to- serve 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

Comments