Part 1: Architecture of the HIP-Bridge

Series by Stefan Spiska, Senior Backend Developer, PEN, vitagroup HIP

Part 1 of the series "Vendor neutral interoperability with openEHR and HL7 FHIR"

To ensure interoperability, data must be extracted from 3rd party applications like HIS (Hospital Information System) or LIS (Laboratory information systems), transformed into open, vendor-neutral formats, and stored within the Platform via the HIP-Bridge:

In HIP, non medical data is stored separately from medical data in a HL7 FHIR server. This separation enables fine grained access control, enhancing privacy and security.

Structured medical data is primarily stored in HIP EHRbase, following the openEHR standard. This ensures that all data is standardised using clinical information models, known as Archetypes and Templates.

The HIP-Bridge serves as the central integration point for reading and writing data, facilitating data transformation between different formats. Through connectors, it supports data exchange using multiple standard and legacy data formats, ensuring seamless integration with existing healthcare systems.

Note: HIP Bridge is backed by a powerful mapping framework, where the storage system of the data can be flexible defined. Therefore, medical data could also be stored in the FHIR Server, as well as non medical data can be stored in EHRbase.