Healthcare Identifiers Service for software developers
Registered healthcare providers must use software specifically developed to connect to the Healthcare Identifiers (HI) Service.
If you want to develop new products, or update existing products that connect to the HI Service, you need to use the HI licensed material and undertake product testing.
Access to the HI licensed material
To access the HI licensed material you will need to read and accept the terms and conditions of the Licence Agreement – Use of the Healthcare Identifiers licenced material for Notice of Connection.
A logon ID and password will be emailed to you, usually within 2 working days, which you will need to use when downloading material from the Current Version (n) Healthcare Identifiers licensed material page.
Software development environment
Once you have access to the HI licensed material you will receive information about our vendor environment, and how to access it. You can use this environment to help with product development. This environment will also be used to complete some of the required product testing.
All products developed or updated to connect with the HI Service are required to undergo testing before production access will be granted.
There are 2 types of mandatory testing:
1. Notice of Connection (NOC) - confirms your product connects successfully with the HI Service.
This is not a certification process and does not certify any products.
Once you've completed NOC testing for each version of your products, the following B2B header fields must remain consistent until production access is granted:
- vendor ID
- product name
- product version
Contact the Online Technical Support (OTS) for information about how to begin the NOC testing process.
2. National E-Health Transition Authority (NEHTA) Compliance, Conformance and Declaration (CCD) - makes sure the software supports the safe implementation and use of healthcare identifiers in clinical environments. These requirements were developed by NEHTA in consultation with the eHealth industry. Visit the NEHTA website or email firstname.lastname@example.org for more information about how to begin the CCD testing process.
It is strongly recommended that products not directly connecting to the HI Service, but still using healthcare identifiers, undergo CCD testing to make sure the products use and manage healthcare identifiers in a manner that supports clinical safety. We recommend you complete NOC testing before CCD testing.
Production access to the HI Service
When you have successfully completed both the NOC and CCD testing for your product, we will let you know your product has been granted access to the HI Service production environment. You’ll be sent the URL address to access it.
With your consent, NEHTA will publish your product on the eHealth Register of Conformity. For more information visit the NEHTA website.
If you require further information about being granted access to the HI Service or would like to find out the status of your production access, email the HI Vendor Operations Team.
We can support you in developing your product.
HI Vendor Operations Team
The HI Vendor Operations Team can help you to understand HI Service business processes, including B2B web services and using the HI Service licensed material.
The HI Vendor Operations Team is responsible for enabling access to the HI Service once you have completed both the NOC and CCD testing requirements.
Online Technical Support (OTS)
The Online Technical Support (OTS) team can help you develop products for the department's health professional online businesses.
Feedback about the HI licensed material
If you wish to provide feedback about the HI licensed material website or the HI licensed material you can email the HI Vendor Operations Team with your comments. Your feedback is important to us and will help improve the quality of our services.
Support for your customers
If your customers have any questions about accessing the HI Service and using healthcare identifiers, they can contact the HI Service Operations Team.
For information about the My Health Record system visit the My Health Record website.
National E-Health Transition Authority (NEHTA) provide information and support for Compliance, Conformance and Declaration (CCD) testing and other eHealth information for software vendors.
For secure messaging you should access:
- Web Service Profiles specification (ATS 5280-2010)
- XML Secured Payload specification (ATS 5281-2010)
The PDF specifications are free and are available online at the Standards Australia e-health website. You will be required to register with Standards Australia to access these specifications.
A complete current version of HI licensed material for software developers.
Software developers must accept the conditions of the Licence Agreement.
When available, the next draft version of the material is provided for comment and feedback before being released as the final version.
There is currently no draft version available for comment.
The National Authentication Service for Health (NASH) allows healthcare providers and supporting organisations to securely communicate and exchange electronic health (eHealth) information.
NASH Public Key Infrastructure (PKI) certificates are used to access the My Health Record system, provide confidence in the integrity of information transmitted and facilitate the secure exchange of eHealth information with other healthcare providers.
Software vendors or software development teams that work in healthcare provider organisations can find information about NASH PKI certificates for software vendors and developers here.