Site search

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.

This Developer Guide provides guidance for developers on how to test their NASH SHA-2 software enhancements and submit evidence of their product’s readiness to the Agency for assessment.

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

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.

The Provider Connect Australia™ (PCA) Business Partner Welcome Pack contains guides to help business partners register their organisation with PCA to receive information that has been published to them from healthcare provider organisations. To enquire about becoming a PCA business partner, or for more information, please email [email protected]…

This release of Provider Connect Australia – Conformance v2.0 includes updates to the following resources to support publishing systems: Provider Connect Australia – Conformance Requirements Provider Connect Australia – Implementation Conformance Statement

This document is a guide for business partners to use when developing their Information Use Statements for each partner service they have registered in PCA.

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

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 document specifies software Implementation Conformance Statement (ICS) for Integrated Systems connecting to the Provider Connect Australia (PCA) solution. A developer who wishes to claim that their software conforms to the requirements for connecting to PCA must complete this ICS to indicate which requirements are satisfied by their implementation…

The Provider Connect Australia (PCA) document library contains documentation and other resources related to software conformance requirements for software vendors to integrate their software with the PCA solution. It is updated on an as-needed basis, when new or updated resources become available, or when existing resources need to be withdrawn.

This document summarises the steps to register as a Business Partner organisation in the PCA Portal.

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

In this guide, you will Register as a developer for the HI Service, Request Test Certificates and Test Environment Data, Install the Test Certificates locally, Import Certificates in CIS Software.

You can use a client such as Postman for testing. The latest collections and environment imports are in the ZIP file linked below: Quick start guide Step   Details 1 Install Postman and create a PCA workspace 2 Unzip the latest postman collections archive above 3 Import all extracted files into PCA workspace 4 Create an…

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

Outlines the client registration operations available through the API.

This document specifies Conformance Requirements for integrated systems connecting to the Provider Connect Australia (PCA) solution.  These requirements are used to assess systems for conformance to help minimise risks to information privacy and security, while maximising the benefits of connecting to PCA. 

The Provider Connect Australia™ (PCA) Business Partner Welcome Pack contains guides to help business partners register their organisation with PCA to receive information that has been published to them from healthcare provider organisations.

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

This document provides a guide to implementing the logical model detailed by the Agency's Australian Organ Donor Register Structured Content Specification as an HL7 Clinical Document Architecture Release 2 (CDA) XML document. This guide is based on version 1.1.1 of the structured content specification. The primary aim of the guide is to take implementers…

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