Site search

This Developer Guide is for the use of developers whose products connect to the Healthcare Identifiers (HI) Service, My Health Record, Electronic Prescribing and Secure Messaging with a National Authentication Service for Health (NASH) PKI Certificate.

In this guide, you will Register as a developer for the HI Service, Request Test Certificates and Test Environment Data, Install the Test Certificates locally, Import Certificates in CIS Software.

This guide will discuss potential changes which are required in your software.

Software products must pass testing requirements before gaining access to the My Health Record production system.

My Health Record integration is typically done in two steps. Connecting to the HI Service and the My Health Record system. 

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

The following frequently asked questions relate to the use of Healthcare Identifiers in Health Software Systems.

After successfully executing the IHI Lookup, it is important to modify your implementation to meet the Test Cases for the Use Cases we have built to UC.010 and UC.015.

Update Certificates - The CPV installation includes some expired certificates. The Agency is currently working on updating the included certificates, however until the new version is released, download this zip file, unzip and replace the certificates. See DH-3517:2021 NASH SHA-2 Readiness Test Specification v1.1 for more details. 

This FAQ answers: What identity information contained in a production or test NASH certificate should I use when validating a signature And What will be the impact on the CCA status of any SMD product that was tested with code that used the URI in the test NASH certificates issued before June 2012

Before you can begin development, you are required to register for access to the My Health Record system

This Developer Guide provides guidance for developers on how to test their NASH SHA-2 software enhancements and submit evidence of their product’s readiness to the Agency for assessment.

In this guide, we will cover; How to implement CIS to NPP into your software, Solution overview and Conformance Test Requirements

The Australian Digital Health Agency aims to increase the adoption of the My Health Record by connecting the My Health Record platform to mobile applications through industry-standard APIs.

The NASH Organisation Certificate Tracker is a simple tool for listing the expiration dates of NASH PKI Certificates for Healthcare Provider Organisations (NASH certificates). Healthcare provider organisations need active NASH certificates to both access the My Health Record system and securely send and receive information via SMD secure messaging services…

Within these guides we will demonstrate the functionality of the FHIR Gateway using Xamarin.Forms in Visual Studio and the Android Emulator

Version 1.0.3 of the Secure Messaging Conformance Test Tools provides updated National Authentication Service for Health (NASH) Public Key Infrastructure (PKI) test certificates. The test certificates are required by the following tools included in the software package: Secure Messaging Test Harness; Secure Messaging Delivery Agent. The test certificates…

The following steps will assist prescribing and dispensing Clinical Information System (CIS) software developers connect to the national Prescription Delivery Service (PDS) and declare software conformance with the Agency’s Electronic Prescribing technical framework.

See details on the PKI certificate page

HI Service and My Health Record test endpoint access information: 

The following steps will assist software developers who provide open Prescription Delivery Service (PDS) and/or Active Script List Registry capabilities to declare software conformance with the Agency’s Electronic Prescribing technical framework.

From 25 May 2022, software systems connected to the SVT environment must trust the new My Health Record public SSL certificate. My Health Record - B2B SVT Certificate V1.1 removes the Apache Server instructions and text files related to language translation. Installation Instructions for Apache To correctly install your certificate, it is important to…

The following steps will assist Clinical Information System (CIS) software developers with a direct Prescription Delivery Service (PDS), declare software conformance with the Agency’s Electronic Prescribing technical framework.

This developer guide helps you to verify whether a My Health Record exists for a patient using their Individual Healthcare Identifier (IHI)