ScriptCheck Workflows

This content is currently in draft pending review before publishing to customers.

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

We have put together some guidance on suggested implementation ideas.

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.

---

A. Clinically check scripts from ScriptCheck Manager

ScriptCheck will retain a clinical check for a patient from a previously dispensed prescription, where all items have previously been clinically checked. When the repeat prescription is next dispensed, the clinical check is automatically retained, subject to no changes having been made to the prescription. Those scripts that have retained a clinical check (up to 6 months) are displayed with a tag on the ScriptCheck Manager screen.

User instructions for this workflow. 

 

1. Prescriptions are downloaded, a batch of tokens printed, and the batch of scripts processed in the usual way.
2. Items are marked by default as .
3. The processed prescriptions are automatically added to the ScriptCheck Manager screen by default.

   

   By default, no 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. On the ScriptCheck Manager screen, those scripts that have retained a clinical check are displayed with a tag, along with the date of the previous check and the previous checking pharmacist’s name.
5. The pharmacist can filter their view to display only those scripts requiring to be clinically checked now. You can also filter by date and patient name.
6. The pharmacist completes the required clinical checks via the Clinical Check screen for each patient. This screen provides the information to support the pharmacist to carry out the clinical check, including access to the PMR.
7. The pharmacist can edit a script, using the F10 – Edit Script on the ScriptCheck Manager screen.
8. Once the clinical check is confirmed by the pharmacist, their name is added against each script along with the tag.
9. Once the scripts have been clinically checked by the pharmacist, using the batch of tokens, other members of the pharmacy team can access ScriptCheck Manager to print and apply the drug labels to the drug packs.
10. Accuracy Checking Technicians can complete the accuracy check.

---

B. Clinical check done when processing scripts

User instructions for this workflow.

1. Prescriptions are download, a batch of tokens printed, and the batch of scripts processed in the usual way.
2. During the processing of each prescription, ProScript Connect will generate any applicable drug interactions and warnings. From the PMR the drug history and label preview are visible. 
3. The pharmacist completes any changes and the necessary checks, then selects F8 – Last Item.
4. On the prescription Type screen, the pharmacist confirms the clinical check is complete by selecting the Prescription is clinically checked box.
   Endorsing – depending upon your pharmacy Application Setting (ETP category) (EPS prescriptions are endorsed by default) you may want to switch this off at this stage.
5. Items are marked by default as .

By default, no 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.

6. The script is added to the ScriptCheck Manager screen tagged as with the pharmacist’s name against the script.

7. Once the scripts have been clinically checked by the pharmacist, using the batch of tokens, other members of the pharmacy team can access ScriptCheck Manager to print and apply the          drug labels to the drug packs.

8. The ACT completes the process with the accuracy check.

 

C. Accuracy Checking Technician’s workflow

In this workflow, the dispensing staff download the EPS prescriptions, print the tokens and process the prescriptions. The prescriptions are automatically added to the ScriptCheck Manager queue. From there, the pharmacist can batch clinically check scripts in the queue.

Once clinically checked, the dispensing staff complete the dispensing process and print the item labels and bag labels. Once the stock has been picked and labelled, the Accuracy Checking Technicians can do the accuracy checks.

User instructions for this workflow.

1. The dispenser downloads the EPS prescriptions in batches and prints the required tokens.
2. The dispenser processes the prescriptions. The scripts are marked by default to be dispensed via and are added to the ScriptCheck Manager screen.

   By default, no 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.

3. The pharmacist carries out the clinical check of the batches downloaded EPS scripts, using the ScriptCheck Manager screen, which will add the tag. Some scripts may already have a retained clinical check from a previous check and are displayed with a tag, the date of the retained clinical check and the pharmacist’s name who carried out the check.

      The clinical checking process can be done by the pharmacist away from the main dispensing area, e.g. in the consultation room.

4. The dispenser is either informed by the pharmacist or sees that the clinical checking process is complete for the batched scripts ( tags are displayed on the ScriptCheck Manager screen).
5. The dispenser selects all the scripts for a selected patient and clicks Manual Complete to produce the dispensing labels per patient. The labels are added to the basket with the relevant token. The script is now moved to the Completed tab on the ScriptCheck Manager screen.
6. The dispenser picks the stock and labels the items.
7. The ACT completes the process with the accuracy check.

KB5002021