FAQ

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 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. 

Purpose of this form

This form is for mobile app developers to enable you to:

This guide explains how a requesting clinician can communicate to a pathology or diagnostic imaging provider that they should not upload a report to the patient’s My Health Record.

The intended audience includes developers and vendors of digital health systems that generate pathology and/or diagnostic imaging requests.

Background

OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.

My Health Record integration is typically done in two tranches. Connecting to the Healthcare Identifiers Service and the My Health Record system.

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.

More information:

Specialists Software Industry Offer

  • 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,

If you are developing GP desktop software, please read about the Practice Incentives Program (PIP) eHealth Incentive.

This aims to encourage practices to keep up to date with digital health and adopt new digital health technology as it becomes available: 

If you are developing GP desktop software, please also read more about the Practice Incentives Program:

Testing

There are two types of testing required to validate your software product for connection to the My Health Record system. These are:

Please follow these steps to register your software product with the MHR SVT environment. This is applicable for new products connections or conformant software enhancements.

Complete the following steps in this section to start developing new products that connect to the Healthcare Identifiers (HI) Service, or to modify existing ones.

It is recommended that the following usability guidelines, referenced in the My Health Record Usability Recommendations on the Agency website, be considered: (Click on the Green Button to download the document).

https://developer.digitalhealth.gov.au/specifications/clinical-documents/ep-2231-2016/nehta-2210-2016 

The relevant sections are:

The detailed specifications for all clinical documents are available from the Agency's website at: 
https://developer.digitalhealth.gov.au/specifications/clinical-documents

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 views are also specified on the Agency's website at:  
https://developer.digitalhealth.gov.au/specifications/clinical-documents

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

Implement the following web services:

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:

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:

1. Healthcare Identifiers Notice of Connection (HI NoC) Testing

2. Healthcare Identifiers Conformance Compliance and Accreditation (HI CCA) testing

The purpose of this page is to provide guidance to developers who are implementing the new interoperability standards for secure messaging thus enabling clinical information systems (CISs) and secure messaging (SM) systems to find healthcare providers as well as accurately address and securely exchange standards-based messages.

Pages

By operation of the Public Governance, Performance and Accountability (Establishing the Australian Digital Health Agency) Rule 2016, on 1 July 2016, all the assets and liabilities of NEHTA will vest in the Australian Digital Health Agency. In this website, on and from 1 July 2016, all references to "National E-Health Transition Authority" or "NEHTA" will be deemed to be references to the Australian Digital Health Agency. PCEHR means the My Health Record, formerly the "Personally Controlled Electronic Health Record", within the meaning of the My Health Records Act 2012 (Cth), formerly called the Personally Controlled Electronic Health Records Act 2012 (Cth).

Back to Top