Site search

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

The purpose of this document is to define the high-level business requirements for Individual Healthcare Identifiers (IHIs) as part of the Healthcare Identifiers (HI) Service. The intention is to explain, at a high level: why IHIs are required; and the requirements that need to be included in the technical design and build of…

Frequently Asked Questions regarding Healthcare Identifiers.

All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.

The Healthcare Identifiers Integration Toolkit contains libraries for B2B connectivity to the Healthcare Identifiers service, used to search for IHI, HPI-Is and HPI-Os. The sample code and integration tools provided here should only be used in conjunction with the Agency's detailed specifications for the Healthcare Identifiers Service and, where appropriate…

This FAQ answers the question: What is the conformance assessment process for healthcare identifiers

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 FAQ is out of date and no longer accurate.

This release of the end product contains a reorganisation of worksheets to provide for requirement #22000 and Electronic Prescribing has been introduced.   The supporting documents on this page provide background and guidance for healthcare provider organisations, and conformance, compliance and accreditation requirements for vendors. For more…

See details on the PKI certificate page

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

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 frequently asked questions relate to the use of Healthcare Identifiers in Health Software Systems.

This Concept of Operations provides an overview of the Healthcare Identifiers Service by: describing the current state of healthcare identification; describing the Healthcare Identifiers (HI) Service in such a way that key stakeholders can visualise how the HI Service will be used and how it will work; documenting key concepts…

This software conformance requirements specification supports the safe use of healthcare identifiers in health software systems. The conformance requirements listed apply to one or more business use cases, where each business use case describes a scenario in which healthcare identifiers are used. 

Version 1.2 of the Healthcare Identifiers Integration Toolkit provides defect fixes and performance improvements for the Healthcare Identifiers B2B Client Library.

The Agency, in conjunction with industry (including Services Australia, Medicare Australia, the Department of Health, MSIA, AIIA and ACIVA, and state and territory health jurisdictions), has specified a set of conformance requirements for health software that uses Healthcare Identifiers. A developer who wishes to claim that their software conforms to…

Outlines the client registration operations available through the API.

Version 1.4.0 of the Healthcare Identifiers B2B Client Library provides defect fixes, performance improvements and internal optimisations without impact on the fuctionality of the library. GitHub This resource is also available here: https://github.com/AuDigitalHealth/hi-b2b-client-dotnet

The _count search parameter returns the number of requested resources per page (excluding the resources returned with _include search parameter) as requested by the client.

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

One of the key features available to business partners is to prefill business partner online forms using PCA. 

The HI Service provides a variety of interfaces for retrieving IHI, HPI-I and HPI-O numbers, as well as a number of maintenance features. The Healthcare Identifiers B2B Client Library provides vendors with an example implementation of some of these client interfaces in both Java and .NET development environments.