Site search

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

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

In this tutorial, you will; register as a developer for the Gateway, understand your testing obligations and more

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 guide will discuss potential changes which are required in your software.

Your software will need to conduct lookups for Individual Healthcare Identifiers (IHIs) for patients. 

A mobile application or web-based application is used by a subject of care or carer to manage prescriptions and to present an electronic prescription token to a pharmacy.

A mobile intermediary system is a software product that a mobile application uses to connect to, and interact with, Open Prescription Delivery Services (PDS) and/or Active Script List Registry (ASLR) Services. 

The Security Requirements for My Health Record Connecting Systems Conformance Profile contains software requirements that harden clinical information systems from cyber security attacks, uplift information security and protect patient information and your software product. 

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.

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

Information about NSMN solution design, Provider Directories, message formats, message content, reference data, testing, technical support, standards, terminology and more.

This guide walks through the steps to access a patient’s My Health Record using the GainPCEHRAccess web service

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

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

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.

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.

This document describes a standards-based set of concepts, structuring rules and approaches for use in specifying and building interoperable eHealth systems. It includes guidelines for: structuring specifications; recommending document components for an eHealth specification; and defining the capability of healthcare organisations to…

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