Site search

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

These use cases effectively form the intermediary layer between business processes and user initiated functions, and the HI Service. This includes the functions to search for an IHI, to check the IHI, and to perform batch processing of the IHI. This document contains the bulk of the complex processing in the IHI integration design. The Validate IHI is…

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 functional grouping focuses on functions available in the HI Service, with the design providing the local processing components needed to make optimum use of the HI Service. There is a one to one mapping between the use cases in this document and the IHI functions implemented by Medicare Australia in the HI Service. Note especially the coverage of the…

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

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…

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

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.

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

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

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

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

This document provides guidance for a healthcare provider organisation implementing the Create Verified IHI for Newborns web service to request a verified IHI from the HI Service for newborns. It does not provide advice about technical implementation of the web service within the HI Service.  

This document list the exceptions raised within the Victorian IHI integration design, and the available resolutions. The exception handling is a major part of the design, with some IHI related functions only available through the IHI exception resolution process. The Best Practice Guide should be referenced for more information. Note that the Best Practice…

This document provides a guide to implementing the logical model detailed by the Australian Digital Health Agency's Service Referral(SR) Structured Content Specification (SCS) as an HL7 Clinical Document Architecture (CDA) Release 2 XML document. This implementation guide is based on Version 1.1 of the Service . The primary aim of the implementation guide…