An issue was identified with the Healthcare Identifiers (HI) Service IHI Inquiry web services, affecting the date of birth field. This issue resulted in a timezone to the consumer date of birth value in the IHI search response.
Make sure your workplan includes: Transition from SHA-1 NASH PKI certificates to SHA-2 NASH PKI certificates and Using a NASH PKI Certificate to access the HI Service. Learn more....
The following frequently asked questions relate to the use of Healthcare Identifiers in Health Software Systems.
In this guide, you will; Understand high level concepts regarding the HI Service, Register as a developer for the HI Service, Request Test Certificates and Test Environment Data, Install the Test Certificates locally and Import Certificates in CIS Software
From the 1st of November 2020, the Australian Digital Health Agency (the Agency) will be conducting Healthcare Identifier (HI) Conformance testing.
My Health Record is a secure online summary of an individual’s health information and is available to all Australians. Healthcare providers authorised by their healthcare organisation can access My Health Record to view and add patient health information.
All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.
There are two mandatory testing processes that you will need to complete:
Notice of changes: Changes are coming for National Authentication Service for Health (NASH) PKI Certificates and the Healthcare Identifiers (HI) Service. Make sure your work plan includes: Transition from SHA-1 to SHA-2 NASH PKI certificates and using a NASH PKI Certificate to access the HI Service. Learn more
The Healthcare Identifiers Service (HI) is a national system for uniquely identifying individuals and healthcare providers. HIs help to ensure individuals and providers can have confidence that the correct information is associated with the correct individual at the point of care.
The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators.
In this guide, you will; Understand high level concepts regarding the HI Service, Register as a developer for the HI Service, Request Test Certificates and Test Environment Data, Install the Test Certificates locally and Import Certificates in CIS Software
My Health Record is a secure online summary of an individual’s health information and is available to all Australians. Healthcare providers authorised by their healthcare organisation can access My Health Record to view and add patient health information.
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. Continued from: IHI Lookup - HI Service Developer Guide 1
Your software will need to conduct lookups for Individual Healthcare Identifiers (IHIs) for patients. This is conducted when registering a new patient, updating a patient in your local system, and in some other specific circumstances. This can be done in batch, or individually. Our example will focus on looking up a patient IHI individually.
Notice of changes: Changes are coming for National Authentication Service for Health (NASH) PKI Certificates and the Healthcare Identifiers (HI) Service. Make sure your work plan includes: Transition from SHA-1 to SHA-2 NASH PKI certificates and using a NASH PKI Certificate to access the HI Service. Learn more
The Healthcare Identifiers Service (HI) is a national system for uniquely identifying individuals and healthcare providers. HIs help to ensure individuals and providers can have confidence that the correct information is associated with the correct individual at the point of care.
The eHealth integration toolkits are a collection of integration tools and sample code resources available in both .NET and Java. The sample code and integration tools are used within the eHealth Reference Platform, forming part of the code library for tools and simulators.
The following frequently asked questions relate to the use of Healthcare Identifiers in Health Software Systems.
All products developed, or updated, to connect with the HI Service are required to undergo testing before production access is granted.
There are two mandatory testing processes that you will need to complete:
The purpose of this page is to outline the changes implemented in September 2018 to the Healthcare Identifiers (HI) Service to enable a National Authentication Service for Health (NASH) PKI organisation certificate.
The Australian Digital Health Agency provides sample code to assist software development and integration with the Healthcare Identifiers Service and the My Health Record system. Most sample code is available in .NET and Java. To see the full list, please visit the eHealth Reference Platform section on the Australian Digital Health Agency website or GitHub. Read more....
My Health Record integration is typically done in two tranches. Connecting to the Healthcare Identifiers Service and the My Health Record system.
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.
Please follow these steps to register your software product with the My Health Record system vendor (SVT) test environment. This is applicable for new products connections or conformant software enhancements.
Complete the following steps in this section to start developing new products that connect to the Healthcare Identifiers (HI) Service, or to modify existing ones.
High Level Scope: The software will enable the upload of pathology or diagnostic imaging reports to the My Health Record system, and the viewing of the My Health Record system by authorised representatives of the diagnostic services organisations.
Important information you and your healthcare providers will need to be aware of when using NASH PKI organisation certificates in production.
A list of organisations involved with digital health in Australia
Healthcare Identifiers licensed materials and software requirements for the use of healthcare identifiers
An issue was identified with the Healthcare Identifiers (HI) Service IHI Inquiry web services, affecting the date of birth field. This issue resulted in a timezone to the consumer date of birth value in the IHI search response.
Make sure your workplan includes: Transition from SHA-1 NASH PKI certificates to SHA-2 NASH PKI certificates and Using a NASH PKI Certificate to access the HI Service. Learn more....
From the 1st of November 2020, the Australian Digital Health Agency (the Agency) will be conducting Healthcare Identifier (HI) Conformance testing.
Notice of changes: Changes are coming for National Authentication Service for Health (NASH) PKI Certificates and the Healthcare Identifiers (HI) Service. Make sure your work plan includes: Transition from SHA-1 to SHA-2 NASH PKI certificates and using a NASH PKI Certificate to access the HI Service. Learn more
By operation of the Public Governance, Performance and Accountability (Establishing the Australian Digital Health Agency) Rule 2016, on 1 July 2016, all the assets and liabilities of NEHTA will vest in the Australian Digital Health Agency. In this website, on and from 1 July 2016, all references to "National E-Health Transition Authority" or "NEHTA" will be deemed to be references to the Australian Digital Health Agency. PCEHR means the My Health Record, formerly the "Personally Controlled Electronic Health Record", within the meaning of the My Health Records Act 2012 (Cth), formerly called the Personally Controlled Electronic Health Records Act 2012 (Cth).
