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.
My Health Record Notice of Connection (NoC) and Conformance Compliance and Declaration (CCD) testing
Software products must pass testing requirements before gaining access to the My Health Record production 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.
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.
Within these guides we will demonstrate the functionality of the FHIR Gateway using Xamarin.Forms in Visual Studio and the Android Emulator
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 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 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)