Scanned eRx failed with a BUS002

If a scanned eprescription (eRx) barcode fails and specifically reports a BUS002 error, the eRx cannot be found to download at the NZePS broker.

So why aren’t these eRx’s at NZePS?

Something is wrong with the system that send eRxs from practice systems to the NZePS broker. It could be isolated to a specific doctor or medical practice, to a health network or internet provider, or could be a nationwide outage.

This error is external to the pharmacy - is not caused by an issue with NZePS at the pharmacy.

What can I do?

Manually process the eRxs and link the SCID (barcode). 

Depending on the cause of the issue, it may take a few minutes or a few days for the problem to be resolved.

What if I want to get things going again ASAP?

If waiting is disruptive, reporting the problem may help. Specifically, where all barcodes from a particular medical centre are failing to scan, advising the NZePS helpdesk [e-mail] may help.

The online helpdesk will require an example SCID (barcode), the name of the medical centre that issued it, and the date and time the problem started.

Consider using an email template to email onlinehelpdesk

• Add a dummy patient to the system called Online Helpdesk and add [e-mail] as its email.
• Setup a template (see Setting up text and email templates), e.g.:
  

• Then, when several eRxs have failed download with BUS002 errors:
  1. Select the patient Online Helpdesk.
  2. Select F10 Other, Quick Contact patient, and use F8 Message Tmplts.
  3. Select the relevant template, e.g.:
     
  4. Scan one of the failed eRx barcodes into the message, add the practice name as well as the date and time of the first failure, and send.
  5. Save as a note in patient (online helpdesk) history if required.

The pharmacy could also notify the medical centre, who in turn could notify their support services.