HIP Tech Blog

The introduction of an open platform to healthcare organization needs to consider the existing system landscape. From a birds-eye perspective, HIP (Health Intelligence Platform) will be integrated as any other application system in a typical best-of-breed architecture. Typically, a communication server will serve as an intermediate to route messages and integration jobs towards the CDR. However, as the aim is to get a very comprehensive data collection into the HIP, it requires extensive and flexible tooling to deal with very different integration scenarios.

In this series of articles, we take a look at the HIP Bridge. The HIP Bridge provides a configurable facade to integrate with legacy systems via HL7 v2 and FHIR and store the data in the semantically-rich and vendor-neutral openEHR format in the HIP.

The interoperability of the HIP has three main components:

In HIP CDR, demographic data is stored separately from medical data in in a HL7 FHIR Server. This provides a solid basis for ensuring privacy by fine-grained access control. To most extend, structured medical data is stored in HIP EHRbase according to the openEHR standard. This means all the data is standardized according to clinical information models, called Archetypes and Templates. The HIP Bridge acts as central docking point for read and write data access. Via Connectors data can be exchanged using multiple standards and legacy data formats.

I am text block. Click edit button to change this text. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

I am text block. Click edit button to change this text. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

I am text block. Click edit button to change this text. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.