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 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.
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.
In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service
My Health Record integration is typically done in two steps. Connecting to the HI Service and 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.
This developer guide helps you to verify whether a My Health Record exists for a patient using their Individual Healthcare Identifier (IHI)
In this tutorial, you will; register as a developer for the Gateway, understand your testing obligations and more
We will use the token received from MyGov to access the patient’s My Health Record
My Health Record B2B Gateway Services - Document Exchange Service - Technical Service Specification v1.8
My Health Record B2B Gateway Services - Document Exchange Service Logical Service Specification v1.5
After creating a healthcare service(s) at a location, you can search for available partner services.
This guide will look at retrieving all clinical document data (including these 2, but excluding MBS documents)
Discover our developer guides