My Health Record integration is typically done in two tranches. Connecting to the Healthcare Identifiers Service and the My Health Record system.
Note: Before you start your development, you will need to have completed the Healthcare Identifiers Initial Registration and the My Health Record Initial Registration.
1- Healthcare Identifiers Service
Before software connects to the My Health Record system, the software first must be able to identify both the patient and the healthcare provider which is done through the Healthcare Identifiers (HI) Service. The HI Service B2B Gateway exposes as SOAP based web services.
The Healthcare Identifiers service manages 3 sets of identifiers:
Note: Searching for HPI-Os is not applicable for My Health Record integration. As a Healthcare Provider Identifier for Organisations do not change during an organisation’s life, it should only need to be captured once.
Rather than connecting to the HI Service to retrieve the HPI-O it is easier to record the HPI-O in the clinical information system at the time of site activation rather than retrieving it from the HI Service.
HI Scope and Development
- HI use cases, conformance requirements and test specifications to help scope your HI development. Learn more
HI Test and Go Live
This section provides full guidance on the steps to test your software for conformance to the Healthcare Identifiers (HI) Service. Learn more
See our article on sample code
, for developer resources for connecting to the Healthcare Identifiers Service and My Health Record system.
2- My Health Record system
Once you have connected to the Healthcare Identifiers Service you can then connect to the My Health Record system via the B2B Gateway. The B2B Gateway provides a way to provide My Health Record functionality directly and natively into your software.
The My Health Record B2B Specifications are available as four service specifications, each service specification is provided both as a logical and technical service specification.
The Record Access Service enables software to discover whether a patient has an advertised My Health Record (required for both viewing a patient’s my health record and uploading to a patient’s my health record) as well as gaining access to a patient’s My Health Record (required for software which is viewing a patient’s My Health Record)
The Document Exchange Service is an XDS.b based service for uploading, replacing, removing and downloading Clinical Documents from the My Health Record service. This service is suitable for both uploading to the My Health Record as well as viewing.
The view service provides a set of dynamic, virtual results set collated from records and clinical documents. The view service is suitable for those systems viewing a patient’s My Health Record.
The registration service allows software developers to offer assisted registration functionality in their software to create a My Health Record for those patient’s who don’t have one but would like one.
The following table describes the My Health Record functionalities and their relevance to various Healthcare sectors.
My Health Record Functionalities
The My Health Record allows different types of functionality including uploading of clinical documents and accessing targeted My Health Record views.
✓✓ Highly Recommended ✓ Recommended
Uploading GP Pharmacy Pathology Diagnostic Imaging Allied Health
Shared Health Summary ✓✓
Event Summary ✓✓ ✓ ✓✓
eHealth Prescription Record ✓✓
eHealth Dispense Record ✓✓
eHealth Pathology Report ✓✓
eHealth Diagnostic Imaging Report ✓✓
Viewing GP Pharmacy Pathology Diagnostic Imaging Allied Health
Health Record Overview ✓✓ ✓ ✓ ✓ ✓
Medicare Overview ✓✓ ✓ ✓ ✓ ✓✓
eHealth Pathology Report View ✓✓ ✓ ✓✓ ✓ ✓✓
eHealth Diagnostic Imaging Report View ✓✓ ✓ ✓ ✓✓ ✓✓
eHealth Prescription & Dispense View ✓✓ ✓✓ ✓ ✓ ✓✓
eHealth Medicines View ** ✓✓ ✓✓ ✓ ✓ ✓✓
** The eHealth Medicines View is not a document that is uploaded by clinical information software. It can only be downloaded via the document list.
For GP desktop software, please also read about the Practice Incentives Program. Learn more
- PCEHR Connecting Systems
The conformance assessment scheme for clinical information systems connecting to the My Health Record system. Learn more
- Uploading Clinical Documents
Detailed specifications for all clinical documents. Learn more
- My Health Record Usability Guidelines
It is recommended that the following usability guidelines, referenced in the My Health Record Usability Recommendations on the Agency website, be considered. Learn more
My Health Record Testing and Go Live
My Health Record Notice Of Connection (NOC) testing and Conformance Compliance and Declaration
- Instructions and resources needed to test and go live with software linking to My Health Record. Learn more
Clinical Package Validator (inc. Template Package Libraries and IQ Rules)
- The Clinical Package Validator (CPV) does not test conformance against all specifications. The product data sheet for the CPV lists the tests that are supported, tests partially supported, and a general description of the types of tests not supported. In order to validate a specific document type using the CPV, you will be required to load in the relevant template package. The Information Quality Rules (IQ Rules) is a tool that helps developers, testers and analysts determine the conformance of clinical documents to the My Health Record system conformance requirements. It should be used in addition to the CPV tests. Learn more
See our article on source code, which covers sample code for connecting to the My Health Record system.
Please contact [email protected] for a confidential discussion about your product integration to the My Health Record system and the support available from the Australian Digital Health Agency.