Site search

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

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

Access to register endpoint requires an initial access token (IAT) of type bearer. Publisher and Subscriber organisations must now request an IAT by registering their software details with the PCA™ Operator first.

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

Prior to registration, the client software needs to generate a 2048-bit RSA key pair as defined in PKCS #1: RSA Cryptography Specifications – RFC 8017 and conveyed using  JSON Web Key (JWK) – RFC 7517.

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

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 discuss potential changes which are required in your software.

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

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

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

HI Service and My Health Record test endpoint access information: 

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

The developer guide is intended to get you up-and-running with using the PCA™ API. It covers everything you need to know from registration, authorisation, participation to publication and subscription.