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.

The National Authentication Service for Health (NASH) makes it possible for healthcare providers and supporting organisations to securely access and exchange health information. NASH provides Public Key Infrastructure (PKI) Certificates that help you or your organisation to: access the My Health Record system; and send and receive messages securely using…

This document defines the logical service interfaces and associated conformance points for the My Health Record View Service. The My Health Record View Service encapsulates the set of information (View) service interactions between clinical information systems, My Health Record portals and the national My Health Record system. This specification considers…

This document defines the logical service interfaces and associated conformance points for the My Health Record Document Exchange Service.

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.

This document provides an implementable technical interface specification for the My Health Record View Service.

This document provides an implementable technical interface specification for the document exchange services using IHE’s Cross-Enterprise Document Sharing-b (XDS-b) specification and accompanying bespoke web services.

After creating a healthcare service(s) at a location, you can search for available partner services.

In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service

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

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

A contracted service provider (CSP) in the My Health Record system is an organisation that provides technology services or health information management services relating to the My Health Record system to a healthcare provider organisation

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

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

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

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.

It is highly recommended that your software conduct HPI-I searches for users of your system. 

Changes to the National Authentication Service for Health (NASH) PKI certificates.

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.

The purpose of this document is to define the high-level business requirements for Individual Healthcare Identifiers (IHIs) as part of the Healthcare Identifiers (HI) Service. The intention is to explain, at a high level: why IHIs are required; and the requirements that need to be included in the technical design and build of…

Now that we have created a Location we want to add one or more Healthcare services that are delivered at that Location.

The National eHealth Security and Access Framework (NESAF) provides standards, tools, and guides for the Australian healthcare sector to build and implement secure systems that protect patient data and eHealth-related assets, while providing the provenance required for ensuring patient safety and privacy. (For more details and to download fact sheets, see…

This guide will look at retrieving all clinical document data (including these 2, but excluding MBS documents)