Site search

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.

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.

Electronic Prescribing Frequently Asked Questions covering topics such as Prescribing Systems, Dispensing Systems, Mobile Applications, Mobile Intermediaries, Transitional eNRMC and Conformance Profile 3.0 and more. 

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

This guide will walk through the steps to create and upload clinical documents

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

OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.

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.

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

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. 

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.

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.

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.

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.

This guide will walk through the process to get patient clinical documents from the My Health Record system and display them to your users using a generic style sheet

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

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.

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

The Agency has a Compliance, Conformance and Accreditation (CCA) program that supports clinical safety and quality in health software. CCA provides leadership, guidance and materials for assessing the conformance of software that implements e-health specifications and standards. These conformance test specifications should be used by implementers and third…

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

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.