Healthcare Identifiers licensed materials and software requirements for the use of Healthcare Identifiers
The Healthcare Identifiers specifications you will require for your development are hosted in 2 different locations:
- System Interface Specifications (SIS) for connecting to the Healthcare Identifiers web services are licensed materials hosted on the Department of Human Services web portal. Suggested document relevant for your implementation are listed below.
|HI Service - Developers Guide.pdf
||Health Systems Developer Portal
|HI Service - IHI Searching Guide.pdf
|TECH.SIS.HI.06 - IHI Inquiry Search via B2B v10.0.pdf
|TECH.SIS.HI.31 - Search for Provider Individual Details – v7.0.pdf
- Healthcare Identifiers Service - Support documents which provide background and guidance for healthcare provider organisations, and conformance, compliance and accreditation requirements for vendors are hosted in the Australian Digital Health Agency Developer Centre.
Plan the scope of your Healthcare Identifiers Implementation
If you are connecting to the HI Service as a pre-requisite to connecting to the My Health Record system, there are particular requirements that you will need to meet in order to be given production access to the My Health Record system. These requirements are explained in section 3.4.1 of the PCEHR Connecting Systems Conformance Assessment Scheme.
Your software will also be required to connect to the HI Service if it is participating in Electronic Prescribing. UC.010, UC.015 and UC.131 will be relevant to your development.
It is important to understand that each HI Service use case may be fulfilled by one or more HI Service web service. You need to determine which web service and use case you require in your product. We recommend that you also familiarise yourself with the use cases outlined in the table below. (If you do not need to access the My Health Record system, participate in Electronic Prescribing, or be listed in the Digital Health Incentive Product Register, then you can implement whichever HI use cases are appropriate.)