Orchid Knowledge Base Home

Home What's New Docs

Filter:
Submit Search

Using My Script List (MySL)

Quick Reference Guide

IMPORTANT   The Australian Digital Health Agency is phasing out older versions of the Electronic Prescribing Conformance profile. To ensure that eScripts continue to work after 30 September 2024, your practice must have upgraded to Bp Premier version Orchid SP1 or later.

This article describes how to enable and utilise My Script List (MySL) in Bp Premier. My Script List (MySL) is an optional service that allows Patients and their chosen health professionals to view a list of all their available prescriptions.

My Script List or MySL is a Department of Health conformant Active Script List (ASL) Registry that consolidates a patient's active prescriptions into a single, easily accessible list. It has been developed to comply with the Australian Digital Health Agency (ADHA) Conformance Profile and ePrescription Architecture. See My Script List (MySL) FAQ for more information.

For Bp Premier to support MySL functionality, your practice must be using a supported operating system and environment:

  1. Microsoft .NET Framework 4.8 is required.
  2. In accordance with eRx's security policy, your Windows OS must be Windows 10 or Server 2016 or later.

The following table lists the operating systems that are compatible with MySL.

Operating System

Is MySL supported?

Windows 7

No.

Windows 8 / 8.1

No.

Windows 10

Yes — .NET Framework 4.8 is supported from the May 2019 Update, or later.

Windows 11

Yes.

Windows Server 2008 / 2008 R2 / SBS 2011

No.

Windows Server 2012 / 2012 R2

No.

Windows Server 2016

Yes — .NET Framework 4.8 must be manually installed.

Windows Server 2019

Yes — .NET Framework 4.8 must be manually installed.

Windows Server 2022

Yes.

1Visit the Microsoft website for more information on .NET Framework versions and dependencies.

2Visit the Microsoft website for more information on the supported TLS 1.2 Ciphers.

MySL Token Information

To create MySL tokens successfully, either the Bp Premier Server or the Bp Premier Client must support .NET Framework 4.8 and the required TLS Ciphers. If neither the Bp Premier Server nor the Bp Premier Client meet the system requirements, MySL functionality will be unavailable.

The following prerequisites must be correctly configured in Bp Premier to access MySL:

Automatically check patient MySL status upon opening the patient record.

To have Bp Premier check the MySL status of a patient upon opening the Patient Record, navigate to Main screen > Setup > Preferences > Prescribing and tick Enable MySL status check on opening patient record.

Options for Medication Management

Orchid SP1 has introduced new options for specifying whether a pharmacy should retain a prescription.

  • Dosing Point refers to a doctor nominating or arranging for a patient's medication to be held in the pharmacy instead of allowing the full supply to be taken.
  • Staged supply is used when the medication needs to be dispensed in stages, such as when the patient is receiving chemotherapy or has a complex medication regimen.
  • Direction is a requirement for jurisdictional regulatory teams and was only available for MediSecure.
  • Repeats on file is used to indicate that repeats should be kept on file for monitored drugs in compliance with Tasmanian requirements.

See Add or cease Rx for more information.

Prescriptions created before upgrading to Saffron will not have any values for the ASL Consent flag (Consent to upload to ASL) recorded in the database and will not be displayed in MySL when the drugs are represcribed.

The Consent to upload to ASL checkbox was added in Bp Premier version Saffron. The checkbox is set as opt-in by default; therefore, to prevent the drug from being uploaded to ASL, the user must untick this checkbox.

Prescriptions created before upgrading to Saffron will not have any values for the ASL Consent flag (Consent to upload to ASL) recorded in the database and will not be displayed in MySL when the drugs are represcribed.

In Orchid SP1 Revision 1, prescribers will have the option to Consent to Upload to ASL when represcribing drugs that were created before upgrading to Saffron. The ASL Consent flag will be updated in the database, and drug will be visible in MySL when represcribed.

For prescribers using Bp Premier version Orchid SP1 and below, click here to view a manual workaround to update the ASL Consent flag that will be applied to all future repeats from this drug record.

  1. From inside the patient record, select Current Rx from the left-hand tree.
  2. Tick the checkbox next to the drug that you want to represcribe. You can select multiple drugs.
  3. Click Print or select the method for sending the electronic prescription token from the Token: drop-down menu and click eScript.
  4. The Upload to ASL window will be displayed for drugs with no ASL Consent flag options recorded in the database.

  5. Tick the checkbox next to any drugs that you Consent to Upload to ASL. The ASL Consent flag will be updated for any future repeats of these drug records.
  6. Click Upload. The drugs will be printed or sent by eScript.

Access to MySL depends on whether the Patient has registered for MySL and has granted access to the Provider. Select one of the links below to view additional information:

  1. From inside the patient record, select Current Rx from the left-hand tree.
  2. Click the View MySL button to establish a connection to MySL.
  3. If the patient's IHI number matches an active MySL account, but the Prescriber does not yet have access, a prompt will appear'. Click Yes.

  4. MySL will send the patient an SMS or email requesting permission for the Practice to view their prescriptions in MySL. The patient must then reply to the SMS or email with their consent preferences.

    5. Patient Replies With

    Description

    1

    Consent given to the Provider to view the Patient's MySL Record.

    2

    Consent given to the Provider to view the Patient's MySL Record for 24 hours only.

    3

    The Patient has declined to provide the Provider with access to their MySL record.

  5. After the Patient has responded to MySL, there may be a slight delay in MySL receiving the response and updating the MySL consent status.

    The Prescriber should wait a few minutes and then click View MySL again.

    Bp Premier will connect to MySL; if successful, the border of the View MySL button will turn from red to green. The View MySL screen will open, and the Patient's active prescriptions will be displayed.

    6. This screen provides a comprehensive summary of the prescriptions, which includes the prescription date, medication name and strength, number of repeats remaining, prescriber name, and token availability. See Send eScript directly to MySL for more information.

    NOTE  The View MySL interface is a read-only window with no clickable fields.

  6. The patient has the option to request that eScript tokens be delivered straight to their MySL account. To do this, the Prescriber must have access to view the Patient's MySL record. See Send eScript directly to MySL for more information.
  1. From inside the patient record, select Current Rx from the left-hand tree.
  2. Click the View MySL button to establish a connection to MySL.
  3. Bp Premier will connect to MySL and the Patient's active prescriptions will be displayed.

    4. This screen provides a comprehensive summary of the prescriptions, which includes the prescription date, medication name and strength, number of repeats remaining, prescriber name, and token availability. See Navigating the MySL window for more information

    NOTE  Note the View MySL interface is a read-only window with no clickable fields.

  4. The patient has the option to request that eScript tokens be delivered straight to their MySL account. To do this, the Prescriber must have access to view the Patient's MySL record. See Send eScript directly to MySL for more information.
  1. When the Provider clicks the View MySL button, the following message will be displayed if the Patient has not registered for MySL or their account cannot be matched using the information provided in the Patient's demographics.

  2. If the Patient has not yet registered for MySL, you should provide them with information about the initiative and advise that they can register at their local pharmacy.
  3. If the Patient has registered for MySL, validate the Patient's health identifier (HI) number and demographic information. See Look up a single patient's Health Identifier for more information.

    4. If the Patient's MySL record cannot be matched after verifying their HI number, the Patient must contact the Pharmacy that registered them for further assistance.

Look up a single patient's Health Identifier

  1. From the Bp Premier main screen, select View > Patients or press F10. Search for and double-click the patient whose health identifier (HI) number you want to look up. The Edit Patient screen (also called 'patient demographics') will appear.

    2. If the HI Status is set to Active and Verified, you do not need to look up or validate the number.

    If the HI status is not set to Active and Verified, you must lookup or validate the HI number.

    In the top right of the screen, a Lookup or Validate button will be present.

  2. If the Health Identifier field is blank, a Lookup button will be present. Select the method by which you wish to look up the HI number: Medicare No, or DVA no. Click Lookup to connect to the HI service to look up the patient's identifier.

    3. If the patient's information is found by the HI server, the Health Identifier and HI Status fields will be automatically populated.

    NOTE  The patient's Family Name, Given Name, Sex, DOB, and Medicare or DVA number must be completed and saved in the patient's demographics, because this information is passed to the HI service to perform the lookup.

  3. If a HI number is already in the Health Identifier field, the Validate button will be present. Select the method by which you wish to look up the HI number: Medicare No., DVA no. or HI no. Click the Validate button. Bp Premier will validate the HI number and update the HI Status fields if the HI number is valid.
  4. Click Save to save the patient demographic.

See Validate Health Identifiers for more information.

The patient has the option to request that eScript tokens be delivered straight to their MySL account. To do this, the Prescriber must have access to view the Patient's MySL record.

  1. Select Rx from the patient record and create a prescription as per usual. You can also send an existing repeat Rx by electronic script. See Add or cease Rx for more information.
  2. Tick the check box next to the drug that you want to send an electronic prescription token for. You can select multiple scripts; all selected scripts will be sent by the same method.
  3. Select the method for sending the electronic prescription token from the Token: drop-down menu.

    4. If the patient has requested that their eScript token be sent directly to MySL, select MySL as the token method.

    The token is sent to the patient's MySL record. This option is only available if the Prescriber has existing access to view the MySL record of the patient. When the MySL token is selected from the token drop-down menu and the eScript button is clicked, no evidence of the prescription is created— this means no paper, email, or SMS tokens are sent to the Patient. See Send eScripts directly to MySL for more information.

  4. Click eScript to send.

    5. If electronic prescribing has not been correctly configured, an alert will appear indicating which information is required in order for electronic prescribing to work.

  5. If you have prescribed a schedule 8 drug, you will be prompted to re-enter your Bp Premier password. Re-enter your password and click OK.
  6. The Verify eScript screen will appear. Check that the information provided for the script or scripts being sent is correct, then click Send.

    7. When sending eScripts directly to MySL, no evidence of the prescription is created— this means no paper, email, or SMS tokens are sent to the Patient.

  7. If the electronic prescription is successfully received by the prescription exchange service, Bp Premier will show a success alert.

    8. If the electronic prescription was not successfully sent, or the attempt times out, Bp Premier will report an error.

    Failed to send the escript

  8. To confirm that the eScript has been sent to MySL, click the View MySL button. The Available status indicates that the Patient's prescription has been received via eScript and that the medication is ready for dispensing.

    9. IMPORTANT   If an error occurs when sending the electronic prescription, Bp Premier will automatically print the script to preprinted paper by default and mark the script as printed.

When the View MySL button is clicked, Bp Premier will establish a connection with MySL and retrieve the Patient's Active Script List.

If the Patient was registered for MySL by a carer or agent acting on their behalf, their information will be recorded in the Carer/Agent section of the MySL interface.

The Active Script List section will provide a comprehensive overview of the Patient's currently available prescriptions, including information such as the date created, medication name and strength, number of repeats remaining, prescriber name, and token availability.

MySL Date Created

The Date Created column in MySL caters for two different scenarios.

For new prescriptions, the Date Created will generally be the Date the medication was initially prescribed. However, if the doctor prescribed the medication with repeats, the Date Created will be updated to reflect the Date the repeat was last dispensed from the pharmacy. This is because the record currently displayed in MySL is the repeat, not the original script.

Description of Token availability statuses

Token Availability

Status

Available

The Available status indicates that the Patient has received their prescription via eScript and their medication is available to be dispensed.

Not Available

The Not Available status indicates that the Patient has a paper-based prescription, there are no tokens available, and the Patient must present a physical copy of their prescription in order to have their medication dispensed.

Issue

Solution

A green outline on the MySL button indicates that the Patient has granted access to their MySL record to the Provider.

A red outline on the MySL button may indicate that the Patient does not have a MySL account or has not given the Provider permission to access their MySL account.

If the MySL button remains grey, either a prerequisite is missing, or the user is not authorised to access MySL.

 

Users who try to access MySL but do not meet the prerequisites will receive an alert that shows which requirements are missing.

This section contains troubleshooting tips for issues encountered while connecting to MySL.

Issue

Solution

This error could indicate a problem connecting to your prescription exchange service. Verify that eRx Script Exchange is configured correctly and that your NASH certificate has been imported successfully. See Configure eRx Script Exchange for more information.

MySL may experience connection timeout issues, resulting in a message being displayed to alert the user. This issue may occur if MySL takes longer than the default timeout period to retrieve the necessary information, especially in cases where the internet connection is weak.

The eScript Timeout Period in Setup > Configuration > General can be adjusted to extend the timeout period for MySL. By default, the eScript timeout period is set to 15 seconds, which should be sufficient for practices with average or better internet connections. However, if your practice is experiencing issues with MySL timing out, you can increase this value.

See Set up Electronic Prescribing for more information.

TIP   If you set the eScript Timeout value to 30 seconds, it will take 60 seconds for MySL to timeout as two requests are sent, one to retrieve the Agents/Carers list and one to retrieve the Active Script List.

The Consent to upload to ASL checkbox was added in Bp Premier version Saffron. The checkbox is set to opt-in by default; therefore, to prevent the drug from being uploaded to ASL, the user must untick this checkbox.

An issue has been identified when represcribing drugs from the Current RX that were created before the upgrade to Bp Premier version Saffron. These drugs are not being uploaded to ASL when the script is printed or sent by eScript.

This issue will be resolved in Orchid SP1 Revision 1. In the meantime, before represcribing the drug in Current Rx:

  1. Right-click the drug's name and select Change Quantity/Repeats.
  2. Untick the Consent to upload to ASL checkbox and click Save if the drug is not to be uploaded to the patient's ASL.
  3. Leave the Consent to upload to the ASL checkbox as ticked and click Save if the drug is to be uploaded to the patient's ASL.

This will update the ASLConsent field to indicate whether the provider consented to upload to ASL. When represcribing the drug, the correct ASL Consent flag will be applied to all future repeats from this drug record.

Information correct at time of publishing (28 November 2023).

Forums

Webinars

Videos

Training

Subscribe