ScriptCheck single patient workflow

In this article:

  • Introduction
  • Single patient flow
  • Scanning token and printing labels
  • Basket Check
  • No More Packs (Owings)
  • Skip Basket Check
  • Verification settings

Introduction

ScriptCheck has been developed to allow pharmacists to carry out clinical checks for EPS prescriptions in batches. The clinical check will be retained for up to 6 months, subject to no changes being made to the repeat prescription. Tokens with that clinical check can then be assembled and accuracy checked using the scanning application.

This new feature for ScriptCheck allows just a single token to be quickly assembled and clinically checked ready for patient collection, without the need to process many tokens in batches to create a picklist for assembly.

This functionality is only available with ProScript Connect v 1.30.7 onwards.


Single patient flow

The patient token(s) must already be in the ScriptCheck queue and have a retained clinical check or have been clinically checked by a pharmacist before this workflow can start.


How to clinically check items

To be completed by the pharmacist.

  1. On the ScriptCheck Manager screen, in the Queue tab the list of scanned scripts is displayed. Filters can be applied including CC Status (Clinically Checked Status).

    Tip: Use the filters to view only the scripts required to be processed at this time, for example Today.
    An image of the queue tab in ScriptCheck Manager with the period filter highlighted (set to Today).

  2. The Responsible pharmacist logged in will be the default pharmacist for completing the clinical checks. Their name is visible on the top ribbon. To amend, click Change to select the required pharmacist, then click  F10 – Save.
    The checking pharmacist does not have to be the Responsible Pharmacist.
    An image of the ScriptCheck Manager screen, with the Responsible Pharmacist option highlighted.
  3. Select the scripts to be clinically checked, then click F2 – Clinical Check.

    Tip: To select all scripts in the current filter, tick the top box beside Date Added.

  4. On the Clinical Check screen, the first selected script is displayed with the PMR History in the left pane, the script(s) in the centre pane and the highlighted script details in the right-hand pane. (N.B. this window is best viewed expanded and you may need to adjust the vertical bars to suit how you wish to view the information)
    An image of the clinical check screen, with the script details highlighted in the centre pane.

    • If the same patient has multiple scripts, they will be displayed together to be reviewed and clinically checked together.
    • In the left pane:
      • Any prescribing history is displayed
      • If there are Patient Notes and/or Allergies/Conditions recorded, Yes is displayed against each accordingly – to view these details and the full PMR history, click View PMR
    • In the top-centre pane:
      • An Edit Prescription option if you need to edit the prescription before the clinical check is completed
      • Each script for the patient is listed, with any blue hyperlink warnings against the medication – click the blue link to view the warning (This is dependant on the ProScript warning Severity level)
      • If there is more than one script, use the arrow icon, to open and close the details
    • In the bottom-centre pane:
      • The currently selected pharmacist is displayed – Click F2 – Select Pharmacist to add or change: a pharmacist must be selected before the clinical check is completed
      • If the script has retained the clinical check, the details will be displayed under Last Clinical Check with the pharmacist’s name, their Registration Number, and the date of the clinical check
    • In the right pane, the Label Details and Script Details are displayed.
  5. Once a script has been clinically checked, select Clinically Checked, or click F4 – Select All CC, if there are multiple scripts for this patient.
  6. Click F10 – Confirm.
  7. On the ScriptCheck Manager screen, those scripts that have been clinically checked are displayed with a tag, along with the pharmacist’s name. If the clinical check has been retained, the date of the retention is displayed.
    An image of the ScriptCheck Manager screen, showing scripts that have been clinically checked (showing the green tag).

    At any time, a script can be edited, click F10 – Edit Script (subject to the edit being allowed when using ScriptCheck, for example creating an owing is not allowed). Once the edit is complete, the script will be tagged as Script Edited. 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 prescriptions that were clinically checked together, then one of these prescriptions was edited, all prescriptions for this patient will have the clinical check reset.


ScriptCheck allows users to assemble and pack a single patient token, starting by either:

  • Scanning a single patient token directly into a blank picklist OR
  • Selecting a single patient already scanned into the app (on the Pending Patients screen)

Scanning token and printing labels

  1. Login to the scanning app.

    How to login
    1. Click the ScriptCheck app shortcut on your desktop.
    2. Login to the scanning app.
      An image showing the ScriptCheck scanning app login screen.
      If you enter your username/password incorrectly four times in a row, you’ll be locked out of the app for 5 minutes.

      Tip: Use the Show/hide icon to the right of the password to view your password entry.

      Warning: Both ProScript Connect and the scanning app must be open together to ensure the latest data can be transferred between them.


  2. Depending upon your preferred choice of workflow, select one of the following options:

    Scan a single token not already in the app


    Scenario:
     You want to process a single patient token to assemble and pack, instead of processing a batch of tokens to create a picklist for assembly and packing.

    • On either the Pending Patients screen OR the Pending Picklists screen, click Scan Now (F11).

      You can use an Application Settings to set up your ScriptCheck to load a blank picklist screen as your default to just process single patient tokens, provided there are no outstanding picklists waiting to be processed. For more information, see the Application settingGeneral Default Menu > Scan Now screen.

    • The option to scan a token is displayed.
    • Scan the single token.
    • The scanned token is displayed in the ‘Patients in Progress’ section.

    You can at this stage scan in a few prescriptions/tokens to be processed together, either for the same patient or for multiple patients.


    Select a single token already scanned in the app


    Scenario
    : a token has already been scanned into a Pending Patients list; the patient has arrived at the pharmacy and their prescription needs to be “pulled out” of the picklist and moved into the single patient flow. The pending token can be removed from the Pending Patients list for quick completion using the single patient workflow.

    • On the Pending Patients screen, use the Search for Patient Name box to find the required patient.
    • Against the selected patient, click the Single Patient icon.
    • The patient is displayed in the ‘Patients in Progress’ section.

      If, at this stage, you wish to scan in another prescription/token to be processed at the same time, a warning message is displayed.

    • Click Confirm (F10) to continue.
      This is a useful feature to quickly add a new patient token to an existing picklist, and to continue with the quick assembly.

  3. On the Patients in Progress screen, click the print icon.
  4.  The patient is now moved into the Assembled Patients section, and all labels are printed (including any supplementary labels, such as alerts, warnings, NMS and DMS).

    If required you could print a paper picking list for stock required – for example, if you had scanned in several tokens in at this point, click Print Picking list.

  5. Pick the stock using the printed token and labels, ensuring the correct generic/brand is picked to match your product choice that was chosen during the prescription dispensing process in Proscript connect N.B the display on the screen will also display any brands selected.
  6. Apply the labels to the drug packs, taking care not to cover the drug pack barcode. Store any supplementary labels with the packs in the basket.

    The drug labels have a QR code on the label that will be used for the basket check.


Basket Check

The basket check is to aid pharmacy staff to ensure the correct labels are on the correct drugs, going to the correct patient. Once the basket check has been confirmed, the bag label will print.

  1. Click Basket Check (F12).
  2. On the script review screen, double-click the required basket, to start the check.
  3. Then complete the accuracy check:
    a. Scan the QR code on the drug label     b. Scan the drug pack barcode
  4. Place each item into the pharmacy bag as they are approved.
  5. Click Confirm (F10).
    To the right of the screen, each script is marked as complete.
  6. Place the bag label on the assembled bag and seal ready for patient collection. (If no bag label is produced then the system will indicate that a verification is required, please then follow the Verification process)

If you find a drug pack is not currently in stock, you can use the No More Packs option, to create a manual Owing(s). See the section No More Packs (Owings).


No More Packs (Owings)

You can force a token through the Basket check stage because of an Owing. Leave the label in the basket with the open bag, until the product is back in stock, then process using your local manual Owings process. In the meantime, follow these steps:

  1. To opt a token out of the basket check stage whilst the stock arrives, click No More Packs.
  2. A confirmation message is displayed.
  3. Click Confirm (F10).
  4. A message is displayed on screen, showing the details of the drug product(s) missing.
  5. Click the ‘Click to confirm’ button, to continue with items becoming Owings. A bag label is printed (if no verification is required).

    If verification is required to complete a basket accuracy check, this can only be done by a pharmacist or ACT with Accredited Access. Whether verification is required at this stage, can be set by your pharmacy, using the Application settings in the scanning app (see details below).  However, if the item is a standard verification item, such as a spilt pack or a non-ScriptCheck item, it will still trigger the verification process, irrespective of your settings.


    No More Packs verification settings in the scanning app

    To access the ScriptCheck app settings, double-click the ScriptCheck app icon on your desktop.

    • On the login details screen, enter your administrator login details and password, then click Login.
    • Within the app, in the left-hand pane, click Settings.
      The App Settings screen is displayed.
    • Select the Process tab.
    • The No More Packs settings that apply to verification are detailed in the following table.

      If the item is a standard verification item, such as a spilt pack or a non-ScriptCheck item, it will still trigger the verification process, irrespective of your setting.

      Display “No More Packs” button during Basket Check When selected the No More Packs button is displayed on screen during the Basket Check

      To enable this option, tick the box to the left of the ? icon.

      Default is Yes.

      Require use of “No More Packs” button to be verified When ticked if the No More Packs button is used, all packs must be verified.

      To enable this option, tick the box to the left of the ? icon.

      Default is Yes.

    • To save any changes, click the Save icon in the top-left corner.

  6. The incomplete picklist will remain on the Pending Picklist screen, to be returned to when ready.
  7. When the stock is back in, the pharmacist or ACT with Accredited Access, on the Pending Picklist screen, select the required picklist that requires verification.
  8. Click the three vertical dots against the picklist, then select Verification.
    An image showing the Verification option within the ScriptCheck scanning app.
  9. The basket awaiting verification is displayed. Once the information has been verified, click Verify. 

Skip Basket Check

Scenario: you may need to pull a token out of a picklist to complete a manual complete in ProScript Connect, Skip Basket Check is a way to do this, but it will force a verification check. A pharmacist or ACT will be required to complete the verification.

  1. Click Skip Basket Check. 
  2. A warning message is displayed on screen.
  3. Click Confirm (F10) to continue.
  4. The basket is closed and a verification message is displayed.
  5. Completed by the pharmacist or ACT with Accredited Access. On the Pending Picklist screen, select the required picklist that requires verification.
  6. Click the three vertical dots against the picklist, then select Verification.
    An image showing the Verification option within the ScriptCheck scanning app.
  7. The basket awaiting verification is displayed. Once the information has been verified, click Verify.
  8. A warning message is displayed. Please read and confirm the items have been checked by a qualified person. Click Confirm (F10).
  9. The bag label is then printed.

Verification settings

In the Application settings for the scanning app, you can set when verification will be triggered depending on your local procedures.

The standard verifications reasons such as spilt packs, a non-ScriptCheck item will still trigger the verification process.

KB5004262