Site search

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

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

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

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 Security Requirements for My Health Record Connecting Systems Conformance Profile contains software requirements that harden clinical information systems from cyber security attacks, uplift information security and protect patient information and your software product. 

The Agency is cognisant of the inherent cyber security risks posed by systems connected to and accessing the My Health Record system, as well as potentially vulnerable aspects of the national infrastructure and all services under its care. To address this risk, a set of security requirements for systems connecting to the My Health Record system have been…

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…

From 25 May 2022, software systems and any application using interaction model 4 and provider apps to connect to the My Health Record Software Vendor Test (SVT) environment must trust the new My Health Record public SSL certificates.   This is required because the Agency is moving the endpoints for SVT from the current Global Switch data centre to…

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

This document provides usability recommendations for clinical information systems and contracted service provider systems authoring or rendering information contained in Shared Health Summary documents exchanged with the My Health Record system. The usability recommendations are provided to all software developers interested in improving the usability of…

This guide will walk through the steps to create and upload clinical documents

From 25 May 2022, software systems connected to the SVT environment must trust the new My Health Record public SSL certificate. My Health Record - B2B SVT Certificate V1.1 removes the Apache Server instructions and text files related to language translation. Installation Instructions for Apache To correctly install your certificate, it is important to…

Software products must pass testing requirements before gaining access to the My Health Record production system.

This document provides the requirements for producers and consumers of Shared Health Summary documents that connect to the My Health Record system. It lists the specific conformance requirements for Shared Health Summary documents in the context of the My Health Record system and provides references to all other documents that specify requirements…

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…

OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.

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.

This guide explains how a requesting clinician can communicate to a pathology or diagnostic imaging provider that they should not upload a report to the patient’s My Health Record. The intended audience includes developers and vendors of digital health systems that generate pathology and/or diagnostic imaging requests. Background Pathology and…

Outlines the client registration operations available through the API.

This guide will walk through the process to get patient clinical documents from the My Health Record system and display them to your users using a generic style sheet

A contracted service provider (CSP) in the My Health Record system is an organisation that provides technology services or health information management services relating to the My Health Record system to a healthcare provider organisation

My Health Record integration is typically done in two steps. Connecting to the HI Service and the My Health Record system. 

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…

Information about NSMN solution design, Provider Directories, message formats, message content, reference data, testing, technical support, standards, terminology and more.