Go to top of page

The Health Identifier and PCEHR System (HIPS) is an interface service designed originally for health systems, particularly within hospitals. Different healthcare systems can be connected to share data using HIPS to pass information back and forth.

HIPS in the Australian context

The HIPS product enables the seamless integration of digital health systems with national digital health infrastructure services, such as the Healthcare Identifiers Service, the My Health Record system, Secure Message Delivery (SMD) systems and National Directory Services (NHSD, NEPS).

HIPS is a middleware product offering standards-based interfaces for seamless integration with systems like patient administration systems, clinical information systems, and laboratory and radiology information systems. It is aimed primarily at supporting large-scale digital health environments typically found in organisations such as hospitals and diagnostic service providers, however, it is also suitable for direct integration with digital health products.

Context in digital health

There are a number of key business flows that occur within digital health in Australia, as outlined in Figure 1 below.

Digital health business flows for HIPS

Figure 1: Digital health business flows for HIPS

Feature specifications

Supporting specifications

Victoria IHI Pre-Implementation Project v1.0

EP-1344:2011

The primary objective of the Victorian IHI Pre-Implementation project is to develop a suite of system design artefacts to support integration of the national Individual Healthcare Identifier into health services’ patient administration systems.

Friday, 11 Feb 2011

Roadmap

The High Level roadmap for this product has recently been developed as follows:

HIPS Roadmap

Roadmap: 
November, 2016
Completed
v6.1 of HIPS merges the functionalities of the previously released eHealth Integration Sample Code (eHISC) and HIPS products. HIPS v6.1 supersedes and combines the functionality of HIPS v5.0 and eHISC v6.0. This version and all future releases of the merged product will be published as HIPS releases only. HIPS v6.1 introduces support for the following views of the My Health Record system:pathology report view, diagnostic imaging report view and health record overview.
May, 2016
Completed
v6.0 of the eHealth Integration Sample Code (eHISC) enables the upload of pathology and diagnostic imaging reports to the My Health Record system without the need to generate CDA™1 documents. This eHISC release introduces the ability to upload HL7™ v2 pathology and diagnostic imaging reports to the My Health Record system as CDA documents. eHISC automatically converts HL7 v2 ORU messages into eHealth Pathology Report and eHealth Diagnostic Imaging Report CDA documents, and facilitates their upload to the My Health Record system. The conversion capability supports ORU messages containing a PDF version of the diagnostic report. The resulting CDA documents do not contain any structured report information but instead refer to the PDF report that was extracted from the ORU message and attached to the CDA document. eHISC accepts ORU messages via both its SOAP web service interface and its new low-level MLLP interface. MLLP offers an easy-to-use integration path, as it is already widely supported by existing laboratory and radiology information system implementations.