Conformance Testing

Testing applications to ensure conformance before release is required. Further information on testing can be found on the MHR Developer website here.

More information:

The links below point to important information you and your healthcare providers will need to be aware of when using NASH PKI organisation certificates in production.   

Testing

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

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

The HI NOC testing is conducted to ensure that your application can connect to the HI environment.

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

This document is intended for B2B software vendors.

It outlines the process for liaising with the My Health Record System Operator (SO) about production incidents and events requiring notification to the SO, such as changes and upgrades to software that connects to the My Health Record system.

It covers areas such as definitions, incident management and software changes and upgrades.

HI Service:

A list of organisations involved with digital health in Australia

Tuesday, 9 October 2018

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

Expired testing certificates can be resolved by contacting OTS Helpdesk [email protected]

Monday, 9 July 2018

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

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