You have the flexibility to manage how a patient receives their repeats for eScripts from the Save and Process window at the end of dispensing. 

Issue Repeat Token field

This field manages how the patient receives the token for a repeat. If a patient has an Active Script List (ASL), this is not required, but they can still be provided with a token.

The default status depends on what is set by the Prescriber in the eScript. You can change from the default option. If changed, this will apply for the repeat being dispensed, and will apply for subsequent repeat dispensing’s of that eScript.

Click the dropdown list and select how the patient wants to receive the token:

  • 0. Do not send token
  • 1. Do not send, print token
  • 2. Email
  • 3. Mobile 

For both Email and Mobile options, if the patient has this contact information recorded in their patient profile, the field will auto populate. You can change the information in the field, and Minfos will validate it on entry.

Update Patient’s Profile checkbox

If you change the email or mobile, this checkbox will be enabled and checked by default. When OK is clicked, the new contact information will be updated in the patient’s profile.

If you do not want the contact information to be updated to the patient’s profile, uncheck the Update Patient’s Profile checkbox. This will send the token to the email or mobile entered in the Save and Process window, but will not update the patient’s profile with this information.  This may be useful, for example, when the contact information is for a carer, not for the patient.

Patient has an ASL

Two checkboxes that display on the Save and Process window control whether the repeat will be uploaded to the patient’s ASL.

Patient wants script added to their ASL checkbox:

  • Un-check if the patient does not want this script added to their ASL
  • If dispensing an original script with repeats from the patients ASL, this will be checked by default. In this case the Issue Repeat Token will default to Do not send token
  • If dispensing a repeat, the checkbox status is the same as the previous dispensing of that script
  • The checkbox is disabled if the Script will be retained by the pharmacy checkbox is selected, as shown below

A white rectangle with black text Description automatically generated

Script will be retained by the pharmacy. Reason for retaining <reason inserted here> checkbox:

  • This checkbox is controlled by the prescriber and cannot be changed by the dispenser
    • If checked, the Issue Repeat Token field will be disabled, with Do not send, print token selected. On saving and processing the script, the repeat token will print and display Retain at <store name inserted here> Pharmacy


Patient does not have an ASL (or has previously not had the script uploaded to their ASL)

Note    When a patient is not registered for ASL, the option to upload the dispense record to ASL is still available. This is to ensure that the history of the patient is up to date if they decide to register for ASL in the future.

If the patient does not have an ASL, or the default status of the Patient wants scripts added to their ASL checkbox is unchecked, then the default status of the Issue Repeat Token option depends on:

  1. The Scripts on File status of the patient.
  2. The method the eScript was originally sent to the patient, by the prescriber.


Scripts on File Patients

Minfos will default the Issue Repeat Token option to match the eScript Repeats for SOF setting in the Dispense/Customer tab of the Configuration window. For further information, see Manage eScript tokens for Scripts on File customers.

Graphical user interface, text, application Description automatically generated

Where 2. Send is selected, Minfos will electronically send the token using the method that the prescriber set in the eScript.