Site search

In this guide, we will be accessing Prescription and Dispense List and Allergies List contained in a patient’s clinical document service

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.

We will use the token received from MyGov to access the patient’s My Health Record

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

In this guide, we will be accessing a patient’s medications and allergies contained in a Personal Health Summary

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.

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

When a patient has an appointment with a healthcare provider, and that healthcare provider is eligible for a Medicare rebate, a Medicare Benefits Schedule (MBS) clinical document is sent to Medicare

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. 

HIPS Mobile is a mobile web application that may be added to an existing HIPS v7.1 or higher instance operated by a HIPS site, enabling users to list, download and display CDA™ documents and views from a patient’s My Health Record on their mobile or tablet device. The product data sheet provides information for implementers about the…

Technical specifications to enable developers to connect applications to the My Health Record system via the FHIR® Gateway. It describes API requests and responses, Data Mapping between CDA Implementation Guide fields and Fast Healthcare Interoperability Resources (FHIR®), and the error scenarios and associated error codes for all APIs. It is…

From 25 May 2022, any application using interaction model 4 and provider apps to connect to the SVT environment must trust the new My Health Record public SSL certificate in the app’s intermediary server trust store. My Health Record - FHIR Mobility Certificate V1.1 removes the Apache Server instructions and text files related to language…

The purpose of this document is to define the operations requirements and guidelines for applications (apps) connecting with the My Health Record system APIs via the My Health Record FHIR® Gateway, using interaction models #1 or #4 (refer to Appendix A for details).

The purpose of this document is to define the consent requirements and guidelines for applications (apps) connecting with the My Health Record system APIs via the FHIR® standard gateway, using interaction models #1 or #4 (refer to Appendix A for details).

This document specifies the mandatory security requirements and recommended security guidelines for applications (apps) connecting with the My Health Record system APIs via the FHIR® standard gateway, using interaction models #1 or #4 (refer to Appendix A for details).

This document is designed to provide developers of applications (apps) accessing the My Health Record system through its FHIR Gateway with guidelines and requirements for the on-screen presentation of structured, non-CDA My Health Record data.

Version 2.4 of the My Health Record FHIR® Gateway introduces reference to the Agency My Health Record Document Register GitHub page which has the full list of My Health Record supported document types including the new Aged Care Transfer Summary documents.

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.

As a part of the vendor onboarding process, the proposed app or new functionality must undergo a risk assessment. The risk assessment is performed by reviewing user stories, requirements and consent workflows.

This document contains the mapping between CDA Implementation Guide fields and Fast Healthcare Interoperability Resources (FHIR®) (Version 1.4.0 of standard).

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 HIPS product enables the seamless integration of digital health systems with national digital health infrastructure services, such as the Healthcare Identifiers Service, the My Health Record system. The product data sheet provides information for implementers about the capabilities of the HIPS end product and its product components.