ScriptCheck: Completing the clinical check when processing the prescription

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

If a pharmacist chooses to dispense prescriptions from ETP, the clinical check can be completed as part of that process, meaning the scripts will be added to ScriptCheck Manager already tagged as . Only the pharmacist can complete the clinical check. Access can be restricted using RBAC.

Whist processing scripts ProScript Connect will generate any applicable interactions and warnings. From the PMR, where the drug history is visible, any patient notes are accessible, and the preview of the label is available, the clinical check is completed and confirmed. The Responsible Pharmacist logged into ProScript Connect will be stamped against the Clinical Check. Other members of the pharmacy team can access ScriptCheck Manager to print and apply the drug labels using the tokens for the processed scripts. Accuracy Checking Technicians can complete the accuracy check. 


Dispensing the EPS Prescription

In the following steps, ProScript Connect is configured to dispense items via ScriptCheck by default. This workflow requires the pharmacist to be dispensing the prescriptions.

  1. Edit the Responsible Pharmacist if required.
  2. From the ETP module, download the EPS scripts. Newly prescribed items are tagged as .

    Consider printing tokens and dispensing scripts in manageable batches, keeping the tokens for each batch together for completion of the labelling from the ScriptCheck queue. You can use the filters in ETP to view batches based around patient name, script type and more. You may want to disable the Auto Print Dispensing Tokens function from the ETP category of Edit Application Settings. You can print tokens individually, click F8 – Print on the View/Process Prescription screen. A batch of tokens can be printed from F10 – Batch Functions.

  3. Process the scripts following your local SOP in the usual way: processing EPS scripts.

    During the dispensing process, any warnings and Flash Alerts associated with the item(s) are displayed. These are colour-coded, classed by severity and will contain additional details for the items you are dispensing. Once you have read these messages, to close the screen, click F10 – Confirm. 

  4. From the PMR, prior to endorsing, notice the prescribed item(s) ready for dispensing are marked by default as .
  5. From the PMR, a script can be locally dispensed, using Dispense Locally. You will need to dispense locally when:
    • An owing is created.
    • An item requires an additional endorsement being added eg. SSP.
    • An item is an MDS item.
    • An item is a CD schedule 1 or 2. The acceptance of schedule 3, 4 and 5 is configurable in the ETP category of Edit Application Settings.
  6. Endorse the script, click F8 – Last Item. The Prescription Type preview is displayed.
  7. After completing the necessary checks, the pharmacist ticks the Prescription is clinically checked box.
    ProScript can be configured not to print the endorsement by default using the Endorse R2 Prescriptions configuration in the ETP category of Edit Application Settings.
  8. Enter any Prescription notes if required, then click F10 – Save. 

    By default, no drug labels will be printed at this stage for ScriptCheck items, but interaction labels, NMS (New Medicines Service) eligibility labels and other alerts may be printed. We recommend that these labels are kept with the patient’s dispensing token.

  9. The prescription is added to ScriptCheck Manager tagged as with the pharmacist’s name.
    If a clinical check had been retained, the date and name of the pharmacist who completed the check is displayed in the Check Retained column.

    The retention of the clinical check has been registered as a Medical Device and is marked with the UKCA certification.

  10. From the queue, a script can be edited, click F10 – Edit Script (subject to the edit being allowed when using ScriptCheck, e.g. creating an owing is not allowed). Once the edit is complete, the script will be tagged as . Remember, that in editing the script, the clinical check will be removed and will need to be clinically checked again.

    If the required edit is not allowed the item can be removed from the queue and dispensed locally, using F3 – Dispense Now.  The clinical check will be removed for any remaining items on the script and will need to be reconfirmed before labels can be printed.

    If a patient has several scripts that were clinically checked together, then one of these scripts was edited, all scripts for this patient will have the clinical check reset.

  11. With the script clinically checked, using the token, other members of the dispensing team can access ScriptCheck Manager and use F9 – Manual Complete to print and apply the drug labels to the drug packs. Accuracy Checking Technicians can complete the accuracy check.

Owings

Owings can’t be created for items in the ScriptCheck queue. Owings are only permitted for items dispensed locally. Therefore, the required item needs to be dispensed now for an owing, which removes the item from the ScriptCheck queue. In the following steps, the selected item is dispensed locally to create the owing.

  1. Process the prescription as ScriptCheck. Before completion of the script, select F2 – Create Owing. 
  2. The Create Owing message is displayed advising that an Owing cannot be created.
  3. To continue, click Cancel. 
  4. On the PMR screen, click Dispense Locally, then click F2 – Create Owing. 
  5. Complete the Edit Owing screen as required.
  6. To complete the prescription and create the Owing, click F8 – Last Item. 
    If an Owing has been created during the processing of a script using Dispense Locally, the item cannot then be marked as a ScriptCheck item prior to completing the prescription. The Send Item to ScriptCheck message is displayed. Click OK to continue processing locally.

Owings can also be created from Reprints.

We have more guidance on creating an Owing when using ScriptCheck for various scenarios.


Printing labels using Manual Complete

Manual complete gives you the ability to produce labels per patient in batches, for scripts directly from the ScriptCheck queue without the need to revert to locally dispensing. Completed scripts using this option move to the Completed tab retaining the clinical check, audit and clinical check retention.

    1. Select all the scripts for the selected patient that have been clinically checked, then click F9 – Manual Complete.
        

      Manual Complete is only available for one or multiple scripts for the same patient that have been clinically checked. If you select a single script to complete manually when the patient has additional scripts in ScriptCheck Manager, a warning message is displayed.

    2. Click Yes to complete all scripts for this patient. Click No to just complete the single script originally selected.

      Drug labels, the patient bag labels and PTS labels (if configured) are printed for the selected scripts.

    3. The completed scripts now move into the Completed tab on the ScriptCheck Manager screen with a full audit.The logged in user is recorded as the accuracy checker when using Manual Complete (the user is displayed in the Accuracy Checked column).

KB5002246