ScriptCheck Implementation using the scanning app

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

Before implementing ScriptCheck using the scanning app to create stock picking lists in your pharmacy, there needs to be careful consideration of how to manage the change in workflow and the associated processes. Your SOPs will need to be amended to reflect any agreed changes in processes.
.
We have put together some guidance and points for you to consider, helping with your new SOPs, for example managing scripts to include the clinical checking process and which role(s) can create the pickling lists.
.
Ensure your staff have been briefed on new SOPs.

Workflows for using ScriptCheck scanning app

Accessing ScriptCheck Manager

  • Pharmacy team members can be given their own ProScript Connect login credentials.
  • Role Based Access Control (RBAC) can be applied to each user depending upon their job role.
  • RBAC can be used to limit access to the Clinical Check screen to pharmacists only. This ensures the clinical check can only be done by a pharmacist.

Find out more on editing job roles

Managing your scripts

Careful management of your prescription tokens is essential to ensure that any labels printed from ScriptCheck Manager prior to a picklist being created are kept with the correct patient’s script. Most labels will be printed as part of the basket checking process.

  • Use the filters within the ETP module to create manageable batches of alike scripts, for example delivery patients, by script types, by MDS status, with CDs included.
  • Instead of auto printing all tokens upon download, consider printing the tokens in more manageable batches based on script type and patient name.
  • Phase 4, Acute and other patient walk-in EPS prescriptions may need to be prioritised as patients attend the pharmacy. You may want to consider dispensing these locally rather than adding them to the ScriptCheck queue.
  • Consider making one member of staff responsible for helping walk-in patients.
  • Consider making one machine as default dispense locally to deal with walk in patients.
  • Consider processing scripts marked for delivery as a separate batch.
  • MDS and eMAR items will be processed locally by default and can’t be added to the ScriptCheck queue. Consider also dispensing locally any non-MDS items for MDS patients. This will ensure their prescriptions do not get added to different workflows.
  • SDM scripts will be processed locally by default and will not be in the ScriptCheck queue.
  • For pharmacies with a dispensing robot, ScriptCheck will not be a suitable method of dispensing.
  • Consider configuring in Application Settings to allow Controlled Drugs to be processed using ScriptCheck according to their schedule.
  • Consider configuring in Application Settings to allow fridge lines to be processed using ScriptCheck.
  • Any scripts being dispensed with an ODS partner, we recommend keeping scripts within that current SOP workflow.
  • Any items with an Owing will need to be dispensed locally.
  • Dispensing a Serious Shortage Protocol (SSP) via ScriptCheck is not available, therefore SSPs should be dispensed locally. If a prescription in the ScriptCheck process requires an SSP, use the Dispense Now option on the ScriptCheck Manager screen.

ScriptCheck and ODS switching scenarios

Managing the Clinical Check

ScriptCheck will retain a clinical check for a patient from a previously dispensed prescription, where all items have previously been clinically checked, subject to no changes having been made to the prescription. The clinical check retention is set for 6 months by default.

Once ScriptCheck is activated, all scripts will need to go through a clinical check the first time they are dispensed. This means that in the first few weeks the pharmacist will clinically check scripts via ScriptCheck Manager. After 28 days the pharmacist will only need to clinically check repeat prescriptions where the clinical check is not retained (for example, if there have been changes to the prescription or the retention period has expired). This will free up the pharmacist’s time for other activities within the pharmacy.

About the clinical check retention logic

Note that:

  • The clinical check must be carried out before picklists for stock can be created – time will need to be allocated and a suitable computer terminal made available for the pharmacist to use, for example a consultation room terminal.
  • The pharmacist can be changed from the default signed in Responsible Pharmacist in ScriptCheck Manager.
  • The clinical check screen provides information/access to information that will assist the pharmacist with the clinical check.
  • If a script is edited post clinical check, the clinical check will need to be confirmed again, thus removing that patient’s scripts from the picklist process.

Picklist process

  • Create a shortcut in ProScript Connect, to access the scanning app quickly.
  • Consider only utilising one machine for creating and printing picklists.
  • Consider which pharmacy staff can be utilised in creating the picklists.
  • Pharmacy team members can have their own scanning app login, with appropriate access.
  • Based on your pharmacy space available to manage the assembly process, think about limiting the number of packs allowed and/or the maximum number of baskets per picklist.  You can set up these settings for your pharmacy from the scanning app settings.
  • Observe good housekeeping around new and used picklists, keeping batched scripts and any labels printed together.

Frequently asked questions

We have collated some of your frequently asked questions on picking lists, barcode scanner messages with guidance.

ScriptCheck Picklist FAQs

KB5002828