Go to top of page

Electronic Prescribing – Frequently Asked Questions

The following Electronic Prescribing Frequently Asked Questions (FAQs) are categorised into the following topics: General, Dispensing and Technical Questions along with a Glossary and links to more information. 

Sample Code for connecting to the My Health Record system’s B2B Gateway

The Australian Digital Health Agency provides sample code to assist software development and integration with the Healthcare Identifiers Service and the My Health Record system. Most sample code is available in .NET and Java. To see the full list, please visit the eHealth Reference Platform section on the Australian Digital Health Agency website or GitHub. Read more....

Electronic prescribing – implementation via communities of interest

  • Australia’s first electronic prescription in primary care was successfully transmitted in Anglesea, Victoria on May 6 2020.
  • This involved testing the end to end process from generation of the electronic prescription by a general practitioner, provision of its associated token digitally to a consumer, supply of medicines via a pharmacy and subsequent PBS claim.
  • 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 the health professionals and the consumers that will use the end product.


Secure Messaging Proof of Concept

The Agency's Secure Messaging Program aims to work collaboratively with industry and suppliers of secure messaging solutions and clinical software to reduce existing barriers to adoption and provide implementable solutions.  Early proof of concept projects completed in late 2018, comprising secure messaging suppliers and clinical information system developers, focused on developing standardised payloads and a FHIR©-based API supporting the federated look up of healthcare provider details when addressing electronic communications.

Mobile known issues

Issue: Test myGov authentication endpoint does not present valid certificate

The certificate presented by the test myGov authentication endpoint is not signed by a valid Certificate Authority. When you first authenticate to the test myGov server with your test patient credentials, your browser may warn you of non-private connection. You have to proceed to enter your credentials in order to authenticate the test patient.

Environment: Test (SVT) 

The production endpoint is signed by a valid Certificate Authority.


Secure Messaging Industry Offer - FAQs

The following frequently asked questions relate to the Secure Messaging Industry Offer webinars. Items a categorised into the following topics: Provider Directory Service, Local Address Book, Message Payloads, NASH PKI Organisation Certificates and Testing.

Specialists Software Industry Offer - Webinar FAQs

Can we search for a HPI-I using a doctor's provider or prescriber number? 
No, To retrieve a providers HPI-I you will require the following,

1. Clinician demographics (name, sex, dob)

2a. Identifier (AHPRA number, HPI-I)


My Health Record Initial Registration

Please follow these steps to register your software product with the My Health Record system vendor (SVT) test environment. This is applicable for new products connections or conformant software enhancements.

My Health Record Usability Guidelines

It is recommended that the following usability guidelines, referenced in the My Health Record Usability Recommendations on the Agency website, be considered

My Health Record Views

There is a requirement that authorised users of the diagnostics services (pathology or DI) system have the capability to view patient information in the My Health Record system.

My Health Record Detailed Functionality

To enable the uploading of clinical documents and the viewing of a patient's My Health Record, the following functionality and supporting material is recommended.

Integrating Diagnostic Imaging Software with My Health Record

High Level Scope

The software will enable the upload of pathology or diagnostic imaging reports to the My Health Record system, and the viewing of the My Health Record system by authorised representatives of the diagnostic services organisations. This means that the software should:

  • Integrate to the HI Service for the purpose of sourcing and validating healthcare identifiers;
  • Support the use of NASH digital credentials for the purpose of authentication to the My Health Record system;


HI Test and Go Live

All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.

There are two mandatory testing processes that you will need to complete:

HI scope and use cases

Healthcare Identifiers licensed materials and software requirements for the use of healthcare identifiers

Diagnostic Services Project Plans and Status Reports

We have created the following templates to assist you in achieving a successful project outcome. While they are based on our experience in project of this type, we can't guarantee their completeness or relevance to your organisation.