Skip to Content
Home

Developer Centre

  • Log in
  • Register
  • Products
  • What's happening
  • Feedback
  • Register
  • Home
  • Testing & Conformance

Testing & Conformance

Go to top of page
  • Featured
  • Products
  • Specifications
  • FAQs
  • News

Featured content

My Health Record SVT System - Notifications

System Notifications

ACTION IS REQUIRED: My Health Record B2B and Mobile Gateway SSL Certificate Renewal & Release 11.2 - SVT Environment

Friday, 15 January 2021

Healthcare Identifiers Service - Support Documents v1.3

Products, Specifications | EP-3362:2020
These documents provide background and guidance for healthcare provider organisations, and conformance, compliance and accreditation requirements for vendors, regarding the Healthcare Identifiers Service.
Login to download

Transitioning HI CCA Testing to the Australian Digital Health Agency

News

From the 1st of November 2020, the Australian Digital Health Agency (the Agency) will be conducting Healthcare Identifier (HI) Conformance testing.

Wednesday, 4 November 2020

Electronic Prescribing Conformance Process

Developer Guides, Products
This process is an overview of the steps software developers take declare electronic prescribing software conformant with the Agency’s technical framework. The Agency offers a range of support services throughout the conformance process including consultative support and scheduled information sessions. Click to view more about the Electronic Prescribing Conformance Process.

PCEHR Overviews, Guides and Conformance Material v1.4

Specifications | EP-2156:2015
Overviews, guides and conformance material relating to the My Health Record system.
Login to download

HI Test and Go Live

FAQs, Developer Guides, Products

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:

Products

Electronic Prescribing Conformance Process

Developer Guides, Products
This process is an overview of the steps software developers take declare electronic prescribing software conformant with the Agency’s technical framework. The Agency offers a range of support services throughout the conformance process including consultative support and scheduled information sessions. Click to view more about the Electronic Prescribing Conformance Process.

Specifications

Healthcare Identifiers Service - Support Documents v1.3

Products, Specifications | EP-3362:2020
These documents provide background and guidance for healthcare provider organisations, and conformance, compliance and accreditation requirements for vendors, regarding the Healthcare Identifiers Service.
Login to download

PCEHR Overviews, Guides and Conformance Material v1.4

Specifications | EP-2156:2015
Overviews, guides and conformance material relating to the My Health Record system.
Login to download

FAQs

HI Test and Go Live

FAQs, Developer Guides, Products

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:

Mobile known issues

FAQs, Industry Offers

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.

...

My Health Record Notice of Connection (NoC) and Conformance Compliance and Declaration (CCD) testing

FAQs, Developer Guides

Listed below are instructions and resources needed to test and go live with software linking to My Health Record 

Integrating Diagnostic Imaging Software with My Health Record

FAQs, Developer Guides

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.

NASH PKI organisation certificates in production

FAQs, Developer Guides

Important information you and your healthcare providers will need to be aware of when using NASH PKI organisation certificates in production.   

How to manage your B2B software in production

Developer Guides

On this page you will find the latest version of the document, My Health Record Managing your B2B software in production. 

What are the test endpoints?

FAQs, Sample Code

HI Service and My Health Record test endpoint access information: 

Organisations working with you

FAQs, Developer Guides

A list of organisations involved with digital health in Australia

My testing certificates have expired

FAQs, Sample Code

Expired testing certificates can be resolved by contacting Services Australia Developer Support at:

News

My Health Record SVT System - Notifications

System Notifications

ACTION IS REQUIRED: My Health Record B2B and Mobile Gateway SSL Certificate Renewal & Release 11.2 - SVT Environment

Friday, 15 January 2021

Transitioning HI CCA Testing to the Australian Digital Health Agency

News

From the 1st of November 2020, the Australian Digital Health Agency (the Agency) will be conducting Healthcare Identifier (HI) Conformance testing.

Wednesday, 4 November 2020

Working with your clients to keep healthcare information secure

News

Stay Smart Online Week ran from 8-14 October and centred on the theme ‘Together we can reverse the threat of cybercrime.’ A key message was to update software on all devices. The campaign highlighted 80% of Android users and 23% of iOS users hadn’t installed the latest software updates.1

Tuesday, 9 October 2018

Clinical Package Validator v2.7 Released

News

Version 2.7 of the Clinical Package Validator enables software developers to improve the depth and automation of clinical document conformance testing.

Monday, 9 July 2018

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

Stay Connected

with the Australian Digital Health Agency

Register to download resources and keep informed of the latest Developer News.

Register

Resources

  • My Health Record
  • Electronic Prescribing
  • Secure Messaging
  • Healthcare Identifiers
  • Clinical Terminology
  • View all

Help Centre

  • 1300 901 001
  • [email protected]
  • System Status
  • Terms of Use
  • Privacy

Connect

Help us improve

We are always looking for ways to improve Digital Health

Provide feedback

Australian Digital Health Agency logo of the Australian Digital Health Agency

Copyright © 2011-2021 Australian Digital Health Agency and third parties.

This website has been designed to be as accessible as possible. We are continually updating it to meet Web Content Accessibility Guidelines (WCAG) 2.0 Level AA.

If you have any problems using this site, or a document you need is not in a format you can access, email us or call us.

Back to Top