Dispensing ePrescription Webinar Questions

During our Dispensing ePrescriptions Webinar, which was attended by over 2,000 customers, we received close to 500 questions. These included a number of similar or duplicate questions as well as comments. Many of these questions are included in the ePrescribing FAQs previously published. The remaining questions have been summarised into the key themes and are listed below.

This area will continue to evolve as learnings continue to be identified through the rollout of ePrescriptions within the Communities of Interest.

What is MedView Flow and how does it work?

MedView Flow is a pharmacy workflow management tool which enables patients to choose how they would like to submit their electronic prescription, either in person or electronically.
The tool seamlessly blends your existing paper prescription workflow with the new electronic prescription workflow.
For a full description and video demonstration on how to configure MedView Flow in your pharmacy, as well as the end to end ePrescription process using MedView Flow, click here.

How do pharmacies handle both paper and ePrescriptions?

We are very conscious of providing pharmacies with a single queue for all prescriptions, which is why MedView Flow was created.
Both paper prescriptions and ePrescriptions can be queued in MedView Flow by scanning the barcode at your Scripts In counter or by the patient sending the ePrescription to the pharmacy’s MedView Flow.
To find out more click here.

What happens with ePrescriptions if the internet is down?

If the internet is unavailable, it will be up the pharmacy to dispense under emergency supply provisions and/or by contacting the prescriber to request a paper prescription.
There has been the suggestion that manually entering the barcode will bypass the process and provide access to the ePrescription. This is not that case as typing in the barcode is the same as scanning the barcode.

Do ePrescriptions change the way we deal with Drugs of Dependency and Schedule 8 drugs?

The introduction of ePrescriptions does not significantly change the way pharmacies handle Drugs of Dependency (DDs). DD “duplicates” or records of the script will be stored electronically in the Prescription Delivery Service Exchange (eRx or MediSecure), rather than as paper copies. Inspectors will be able to view your electronic records alongside your paper DD duplicates for audit purposes.
It will no longer be possible to handwrite on the ePrescription so this requirement will be addressed by the ability to annotate the ePrescription and repeats (via the prescribing and dispensing systems) when they are prescribed and dispensed.
It remains the responsibility of the Pharmacist to ensure they are fully aware of the jurisdiction specific regulations regarding DDs.

How does MedView Flow support deliveries and can pharmacies configure their available delivery times or disable deliveries to patients?

Patients are able to request delivery when they submit their ePrescription to their pharmacy. This includes the ability to specify their preferred delivery date and any other items they may want included as part of the delivery. At this stage the pharmacy is not able to configure pharmacy specific days or times that delivery is available in MedView Flow. However, the pharmacy is able to use MedView Flow to communicate directly with the patient with regards to delivery requests. There are also a number of innovative delivery systems being developed to support the ePrescribing system.

What are the Communities of Interest, can I participate and how long will they last?

The ePrescriptions Project has now progressed to its next stage of expanded testing and workflow integration through the establishment of the Community of Interest (COI) testing hubs. The COI testing hubs will continue to develop to ensure both modes of ePrescriptions (Token and ASL) are thoroughly tested to inform the progressive and broader rollout across the community pharmacy network planned for later in the year.
The COIs are being led by the Prescription Delivery Services (eRx and MediSecure) in coordination with software providers who are establishing initial COI sites that they routinely use for testing. As stated by Australian Digital Health Agency (ADHA), testing of the ePrescription end-to-end process requires collaboration and coordination across all participating software providers. The implementation of any new software requires initial testing in real environments to confirm not only the technical functionality of the software, but also that it is fit for purpose for community pharmacies, prescribers and patients.
For further information on the ePrescribing Communities of Interest, click here to visit the ADHA website.

When will ePrescriptions be rolled out nationally?

The COI process is expected to run from June through to late August 2020. The feedback you provide during this period will help to shape the next steps towards national availability of ePrescriptions.
Leading up to the broad deployment of ePrescriptions, it is important that you ensure your pharmacy is ready. Please refer to our ePrescribing checklist and guide to assist you in preparing your pharmacy.

What hardware do pharmacies need to process ePrescriptions?

With the introduction of ePrescriptions and MedView Flow it is important to consider how you will begin processing ePrescriptions and specifically what, if any, enhancements you will make to your store layout and computer hardware requirements.
This will vary from pharmacy to pharmacy, depending on your own personal preferences, customer demand, existing hardware and the physical layout of your pharmacy.
For detailed information on possible hardware options for handling ePrescriptions with MedView Flow at your pharmacy click here.
The other important consideration is ensuring your cyber security protection is adequate. This is not specific to ePrescriptions, however it is vital to ensure you have sufficient cyber security in place. For information on Fred Protect, a real time service tailored for pharmacies, dispensing and POS software, click here.

How secure is the ePrescription service?

Significant work has gone into the design of the ePrescription architecture, including the security model, to ensure it is as secure as possible.

Once a patient has submitted an ePrescription to their pharmacy for dispensing, can they cancel that request?

Should a patient wish to cancel the order sent to the pharmacy, the patient would be required to contact the pharmacy directly and request the order be deleted from their MedView Flow queue.
Once the pharmacy has commenced or completed the dispense of the ePrescription, the legal ePrescription has been pulled down from the PDS (eRx or MediSecure) and locked to ensure it cannot be dispensed a second time. Should the patient wish to cancel that order, the pharmacist will cancel the dispense in their dispensing system which will reactivate the ePrescription in the PDS (eRx or MediSecure) and re-issue the token to the patient. Under the ASL model, cancellation of the order will result in the ePrescription being added back to the patient’s ASL.

Can ePrescriptions be cancelled to remove from the Prescription Delivery Services (eRx and MediSecure)?

ePrescriptions can be cancelled by the original prescriber only. The prescriber can perform the cancellation through their prescribing software which will result in the cancellation being reflected in the Prescription Delivery Service (eRx or MediSecure).

How does the pharmacy scan check with ePrescriptions?

Scan checking is performed the same way with ePrescriptions, as it is with a paper prescription. The introduction of ePrescriptions is simple a way of injecting the prescription data into the pharmacy dispensing software, which continues to be used to dispense the prescription.

How is the Active Script List different to the Token model and when will it be available?

The Active Script List (ASL) is an optional extension to provide an enhanced patient experience. As with the token model, the ASL relies on conformant electronic prescription messages instead of paper prescriptions.
The key difference between the ASL and the Token model is that if a patient registers for the ASL they no longer require a token to access their prescriptions. The ASL enables patients to provide relevant pharmacies, doctors and third-party intermediaries of their choice with access to their personal list of active scripts for dispensing. This access is revocable but may otherwise be ongoing or temporary depending on the access granted by the patient to each viewing party.
It is important to note that this is purely a list of the patient’s active scripts for future dispensing and not their full medication profile. Once access is granted, a pharmacy may dispense the items requested by the patient and doctors and third-party intermediaries may view the list.

Do ePrescriptions change how PBS claims are made?

PBS claiming is a function of the dispensing software. As a result, the introduction of ePrescriptions does not change the way the PBS claims are made.

How will patient apps interact with ePrescriptions, both Token and ASL models?

Patient apps will provide an important service as part of the Token and ASL models. In the initial stages patient apps will be able to store the patient’s tokens to provide the patient with the ability to forward the token to their chosen pharmacy. This will also allow the app to provide their usual services for the patient such as script reminders.
The integration of patient apps to the ASL will provide a number of important features including the ability of the patient to:

  • Sign up for an ASL and subsequently opt out of having an ASL
  • Manage the consent process, allowing their chosen health practitioners to access their ASL and subsequently remove access should they choose
  • View their ASL via the app. It is not initially possible for patients to view their ASL directly, so the use of a patient app is required to have this access.

Will ePrescriptions finally remove the need for owing prescriptions?

The introduction of ePrescriptions will begin to remove paper from the process, but it is not currently government policy to remove the option for patients to receive paper prescriptions. It’s anticipated that paper prescriptions will continue to exist for some years to come.
As a result, MedView Flow is designed to enable paper prescriptions (with or without an eRx or MediSecure barcode) to be added to the same queue as ePrescriptions for more efficient workflow management.
To find out more click here.

ePrescription FAQ’s for Pharmacy