Pharmacists may now record a signature in Paladin that is tied to their employee record. Anytime a pharmacy consultation is accepted or declined by the customer, the salesperson may identify the pharmacist assisting the customer, and Paladin will automatically associate the pharmacist’s signature with the consultation results.

Results are very easy to monitor or prove to auditing agencies. Transaction reports may be generated by all the normal methods. Included with every consult offered is the statement of Consult Accepted (or Declined), and if pharmacist’s signature is enabled, the pharmacist’s name and ID are printed with the transaction.

To enable this feature:

  1. In Paladin, from the main menu, select File > Setup.
  2. Select the Employees tab.
  3. Click Set Signature, and if the terminal has a Topaz brand signature capture device accessible, you will see a checkout wizard style signature box displayed.
  4. Enter the signature and click OK. Do this for all personnel responsible for consultations. Do not store signatures for employees that do not have this privilege. Any employee with a signature stored will display a message on this screen stating “Signature Currently Exists”.
  5. Select the Pharmacy tab.
  6. In the Consult pane, check Enable Pharmacy Consult. If signatures have been stored, check Enable Pharmacist Signature.
  7. Click Save, and then click Close.

The Consultation message and options are in the the invoice checkout wizard as the last step to complete before receipts are generated. A panel is displayed with the label of “Pharmacy Consult Wizard”. The default option displayed is Consultation (is) Not Required. Two other options may be selected by the salesperson: “Required and Accepted” or “Required and Declined”. If the pharmacist’s signature is enabled, a list of all available pharmacists is displayed for the salesperson to select from.

If you have questions or suggestions about this information, contact support@paladinpos.com.

*Content is subject to change. For the most recent version, visit the Help Portal.
Printed on: 5/18/22