Site search

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

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

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

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

This guide walks through the steps to access a patient’s My Health Record using the GainPCEHRAccess web service

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.

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

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.

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…

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

Within these guides we will demonstrate the functionality of the FHIR Gateway using Xamarin.Forms in Visual Studio and the Android Emulator

This release of the My Health Record B2B Gateway Services includes updates to View Service and Document Exchange Service’s technical service specifications.  The updates to the My Health Record B2B Gateway specifications result from new capabilities being introduced to the My Health Record in March 2021.

The Australian Digital Health Agency has developed the following webinar recording for My Health Record B2B Software Developers. This webinar recording provides an introduction to integrating B2B software with the My Health Record system. Topics covered include: Foundational information about The Healthcare Identifier (HI) Service including HI Service…

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.

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 Australian Digital Health Agency has developed the following webinar recording for My Health Record B2B Software Developers. This webinar recording provides an introduction to integrating B2B software with the My Health Record system. Topics covered include: Foundational information about The Healthcare Identifier (HI) Service including HI Service…

The My Health Record SVT environment allows software vendors to build and test the B2B Gateway web services for interactions with the My Health Record system. To express your interest in connecting to the My Health Record SVT environment or if you require further information about software vendor testing, please contact Customer Support at help…

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).

In this tutorial, you will; register as a developer for the Gateway, understand your testing obligations and more

This release of the My Health Record Overviews, Guides and Conformance Material have been updated to include the newly released Security Requirements for My Health Record Connecting Systems Conformance Profile - Final Draft v1.1. The security profile boosts cyber-security defences for clinical information systems connected to the My Health Record system. DH…

This release includes updates to the Health Record Overview Presentation and Data Usage Guide v1.2 resulting from adding new Goals Of Care Specification document to the recent release of the My Health Record system. The Health Record Overview provides a summary of an individual’s My Health Record and is intended to serve as the “home screen…

The My Health Record programme has identified specific use cases where the author of a personal health summary may not have an individual healthcare identifier (IHI). For example, a care agency worker may add a personal health summary to the My Health Record system on behalf of an individual. The conformance profile allows for the use of an alternative…

This guide will use the My Health Record getView web service to download collated information from a My Health Record in a ‘View’