This functionality is only available to customers using the Electronic Prescription Service in England and Wales.
In this article:
- Accessing ScriptCheck Manager
- Managing your scripts
- Managing the clinical check
- Frequently asked questions
Before implementing ScriptCheck in the 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.
Ensure your staff have been briefed on new SOPs.
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.
- Use RBAC 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 about editing job roles.
Managing your scripts
Careful management of your prescription tokens is essential to ensure that labels printed from ScriptCheck Manager are associated to the correct patient’s script
- Use the filters within the ETP (Electronic Transmission of Prescriptions) module to create manageable batches of alike scripts, for example delivery patients, 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. 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 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 a SSP, use the Dispense Now option on the ScriptCheck Manager screen.
Managing the clinical check
ScriptCheck retains clinical checks for individual patients and prescription items, 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
Frequently asked questions
We have collated some of your frequently asked questions with the answers.
KB5001985