ScriptCheck Workflows using the scanning app

This functionality is only available to customers using the Electronic Prescription Service in England and Wales.

As part of your pharmacy implementation of the ScriptCheck scanning app, you’ll need to consider new workflows and local SOPs. To assist in that implementation, we have detailed some suggested workflows and guidance notes.

In these workflows, ScriptCheck has been activated by the Service Desk, with the default Application setting – all script items to be dispensed via ScriptCheck Manager.


Workflow A

In this workflow, the dispenser downloads EPS prescriptions and prints tokens in batches. The scripts are processed and are added to ScriptCheck Manager by default.

The pharmacist does the clinical checks for the scripts in batches from the ScriptCheck Manager screen. After the first 28 days, repeat scripts will be retaining a clinical check if no changes have been made since the last clinical check. Thus, saving pharmacist’s time as the number of scripts requiring a clinical check will be reducing.

A member of the pharmacy team then creates a picklist using the scanning app for a batch of clinically checked scripts, collates the required stock and uses the scanning app to allocate the stock to patient baskets. A member of the pharmacy team to completes the basket accuracy checks, confirm the checks, then the bag labels are printed.

  1. The dispenser downloads, prints tokens and processes the scripts following current local workflow. Items will be marked by default as .

    By default, no drug or bag labels will be printed at this stage for ScriptCheck items. However, the following labels may print if configured to do so – alerts and drug warnings, NMS and DMS labels, Prescription Collection Point (PCP) and Pro Delivery Manager (PDM) barcodes. We recommend that these labels are kept with the patient’s dispensing token. If configured, Order basket confirmation and SMS/email notifications may also appear on screen.

  2. The system checks if each script had a clinical check retained from the last 6 months. If a clinical check is found, the script is added to the ScriptCheck Manager Queue tab with the pharmacist’s name and the date of the previous clinical check.
  3. Any script without a clinical check retained must be clinically checked by a pharmacist.
  4. Using the scanning app, a member of the pharmacy team scans in the clinically checked scripts to create a picklist.
  5. The picklist is printed and used to gather the stock required.
  6. The QR code on the picklist is scanned to print the numbered basket labels, which are then placed on the pharmacy baskets.
  7. Each drug pack barcode from the gathered stock is scanned and ScriptCheck displays the basket number the pack belongs in. The drug label is printed, added to the pack and placed in the correct basket. The dispensing token is also placed in the appropriate basket.
  8. Once all the stock has been added to the appropriate baskets, the basket accuracy check can be done.
  9. The scanning app aids the pharmacy team with ensuring the correct labels are on the correct drugs and are going to the correct patients.
  10. When a basket checks is complete, a member of the pharmacy team confirms the check and the bag label is printed.

Workflow B

In this workflow, the pharmacist downloads EPS prescriptions, and prints tokens in batches, then opts to complete and confirm the clinical check during this process. The scripts will be added to ScriptCheck Manager with the status already applied.

A member of the pharmacy team then creates a picklist using the scanning app for a batch of clinically checked scripts, collates the required stock using the picklist, then uses the scanning app to allocate the stock to the appropriate patient baskets. A member of the pharmacy team completes the basket accuracy check, confirms all is correct and the bag labels are printed.

  1. The pharmacist downloads, prints tokens and processes a batch of scripts.
  2. During the processing of each prescription, the pharmacist completes the necessary checks, then selects F8 – Last Item.
  3. On the Prescription Type screen, the pharmacist confirms the clinical check is complete by selecting the Prescription is clinically checked box.

    Tip: Endorsing – depending on your pharmacy Application Setting (ETP category) (EPS prescriptions are endorsed by default) you may want to switch this off at this stage.

    By default, no drug or bag labels will be printed at this stage for ScriptCheck items. However, the following labels may print if configured to do so – alerts and drug warnings, NMS and DMS labels, Prescription Collection Point (PCP) and Pro Delivery Manager (PDM) barcodes. We recommend that these labels are kept with the patient’s dispensing token. If configured, Order basket confirmation and SMS/email notifications may also appear on screen.

  4. The scripts are added to the ScriptCheck Manager screen tagged as with the pharmacist’s name against the scripts.
  5. Using the scanning app, a member of the pharmacy team scans in the clinically checked scripts to create a picklist.
  6. The picklist is printed and used to gather the stock required.
  7. The QR code on the picklist is scanned to print the numbered basket labels, which are then placed on the pharmacy baskets.
  8. Each drug pack barcode from the gathered stock is scanned and ScriptCheck displays the basket number the pack belongs in. The drug label is printed, added to the pack and placed in the correct basket. The dispensing token is also placed in the appropriate basket.
  9. Once all the stock has been added to the appropriate baskets, the basket accuracy check can be done by a member of the pharmacy team.
  10. The scanning app aids the pharmacy team with ensuring the correct labels are on the correct drugs and are going to the correct patients.
  11. When a basket check is complete, a member of the pharmacy team confirms the check and the bag label is printed.

KB5002343