Guides

The following code samples are written in Python and provided as samples only.

Security resources from our Cyber Security Awareness team.

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

Your software will need to conduct lookups for Individual Healthcare Identifiers (IHIs) for patients. 

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.

It is highly recommended that your software conduct HPI-I searches for users of your system. 

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

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

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

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

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

A mobile intermediary system is a software product that a mobile application uses to connect to, and interact with, the National Prescription Delivery Service (NPDS) and/or Active Script List Registry (ASLR).

A mobile application or web-based application can be used by a subject of care or carer to manage prescriptions and to present an electronic prescription token to a pharmacy.

This guide describes the steps to supersede a Clinical Document in the My Health Record system

This guide will describe the steps to remove a Clinical Document

Before you can begin development, you are required to register for access to the My Health Record system

In this guide, we will cover; How to implement CIS to NPP into your software, Solution overview and Conformance Test Requirements

This guide discusses potential changes required in your software.

Outlines the API calls available to developers who wish to connect software to PCA™

Currently, the only channel to authorise publication of service offerings is through the PCA™ Portal. 

In cases when a publisher submits a business partner identifier and the business partner identifies that an incorrect identifier has been provided the business partner can patch the identifier provided in PCA™.

The following steps will assist prescribing and dispensing Clinical Information System (CIS) software developers connect to the National Prescription Delivery Service (NPDS) and declare software conformance with the Agency’s Electronic Prescribing technical framework.

The following steps will assist Clinical Information System (CIS) software developers with a direct Prescription Delivery Service (PDS), declare software conformance with Australia Digital Health Agency (the Agency’s) Electronic Prescribing technical framework.

Register our system as a client with the PCA™ Identity and Access Manager as per OAuth 2.0 Dynamic Client Registration Protocol – RFC 7591.