- The “Fill Status” transaction is best suited for this interoperability need.
- Both the prescriber and the receiving pharmacy must have their systems configured for the transaction in order to facilitate successful exchange.
- Allows the pharmacist to notify the prescriber about the status of a prescription in three cases: (1) To notify the prescriber of a dispensed prescription, (2) to notify the prescriber of a partially dispensed prescription, and (3) to notify a prescriber of a prescription not dispensed
- Opt-in functionality available in SCRIPT versions 2014+ allow prescribers to specify which prescriptions and which dispense status to receive fill notifications for.
- 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.