This section of the Ozone Docs is designed for software architects, engineers, and developers. It provides comprehensive information on Ozone's architecture, guides on integrating new software components, and technical advice on developing within Ozone.
Architecture Overview
Ozone Platform
Ozone Platform serves as the interoperability layer that seamlessly integrates HIS components by enabling data flows between them:
Ozone Platform is a decenstralised mesh of peer-to-peer interoperability services, each an instance of Ozone's EIP Client.
Each service connects a pair of HIS components of Ozone's digital health sofware suite:
Ozone's EIP Client
The core of the Ozone Platform is powered by the EIP Client(1), a Spring Boot application that runs Apache Camel routes. This application acts as the ETL1 agent between two components of the HIS.
The EIP Client facilitates the exchange of FHIR resources between two components of Ozone's digital health software suite. This exchange of FHIR resources is precisely what makes the data flows of Ozone HIS.
Development in Ozone primarily involves assembling peer-to-peer services using the EIP Client. This client is equipped with several built-in features, simplifying the development process:
- It's a ready-to-use application designed for implementing Camel routes.
-
It manages authentication:
- With Ozone FOSS's HIS components.
- With Ozone Pro's Identity Provider (IdP). Pro
-
It includes a variety of common libraries to implement data flows that can be reused across different services.
-
Extract, Transform, Load ↩