ScriptCheck Implementation

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

In this article:

  • Workflows
  • Accessing ScriptCheck Manager
  • Considerations for managing your scripts
  • Restrictions
  • Managing the Clinical Check
  • Picklist process
  • Frequently asked questions

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

To help you select the correct workflow suitable for your pharmacy, we have guidance and a quick comparison table, click the links below for details.

Single patient workflows

Multi-patient Workflows

Accessing ScriptCheck Manager

  • Pharmacy team members can be given their own ProScript Connect login credentials.
  • Each user can have a specific Role Profile assigned to their user profile, depending on their job role. This 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 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
  • 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 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.

Restrictions

ScriptCheck would not be a suitable method of dispensing if you are using one of the following modules or 3rd party products:

ProScript Connect module or 3rd part product Description Notes
Monitored Dosage System Care home and community module for managing weekly MAR charts etc MDS and eMAR items will be processed locally by default and can’t be added to the ScriptCheck queue. Consider dispensing locally any non-MDS items for MDS patients. This will ensure their prescriptions do not get added to different workflows.
Electronic MAR charts (eMAR) Data is exported from ProScript Connect into 3rd party partner to create electronically administered MAR charts
Automation Full pack, blister or strip dispensing robots used in pharmacy Any scripts being dispensed with an Offsite Dispensing Solution partner, we recommend keeping scripts within that current SOP workflow.
Pick to Patient script solutions Scanning solutions that allow customers to order based on scripts processed, and then scanned into bags
Collection Points Hole in the wall collection points allowing patients to collect their medications out of hours
Substance Dependency Module (SDM) Allows scheduling and recording of SDM prescriptions with reminders for pharmacy staff SDM scripts will be processed locally by default and will not be in the ScriptCheck queue

Managing the Clinical Check

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 or additions to the prescription). This will free up the pharmacist’s time for other activities within the pharmacy.

ScriptCheck is used to action clinical checks for individual patients and prescriptions, that can be retained for up to 6 months. However, if any parameter changes or if the 6 month period has expired, the next time a prescription containing those items is dispensed it will not retain the clinical check, requiring a pharmacist to complete and record the clinical check again.

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 process.

Other considerations

  • 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
  • Consider your pharmacy space available to manage the assembly process – if you decide on on the multiple patients workflow think about limiting the number of packs allowed and/or the maximum number of baskets per picklist. If you are using a single patient flow, you will still need some workspace for a single basket beside your PC and scanner.  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 multi patient picklist FAQs

KB5002828