Skip to content

This section of the Ozone Docs is tailored for digital health decision-makers and business analysts, detailing Ozone's functionalities and highlighting its benefits for end users of health information systems and integrated digital health software.


Ozone is an easy-to-install growing suite of digital health software,
integrated by a scalable interoperability framework
delivering a complete health information system experience.

    state "Ozone HIS" as ozone
    state "digital health software" as state1
    state "interoperability framework" as state2

    state1 --> ozone
    state2 --> ozone

1   A suite of opt in/out digital health software

Ozone is a ready-to-use solution, providing a pre-selected array of FOSS1 components that function seamlessly together.

It is a complete health information system allowing users to customize it by choosing which supported digital health software to include or exclude:

Ozone HIS suite

Ozone HIS 1.0.0-alpha.9

HIS type Component Version in Ozone HIS
EMR OpenMRS 3.0.0-beta.16
ERP Odoo 14
ERP ERPNext 15.12.2
BI Apache Superset 1.5.1
IdP JBoss Keycloak 22.0.0

Ozone Pro markers

Features and sections exclusive to Ozone Pro are marked with    Created by potrace 1.16, written by Peter Selinger 2001-2019 Pro.

Criteria for inclusion

As Ozone continues to expand its suite of software components, several criteria must be met for a software component to be included in the Ozone HIS ecosystem. Below, we outline these requirements by order of importance:

Criterion Requirement
Open-source Must Ozone is FOSS under MPL 2.0. Closed-source software is accommodated within the Pro edition of Ozone or through custom developments.
Released version Must Ozone supports HIS flows between versioned components with stable and, ideally, well-documented APIs.
OAuth 2 Must OAuth2 is required for enhanced security and to implement SSO within Ozone HIS.
Docker image Must Docker, while not the sole deployment mechanism supported, is currently the default one in Ozone HIS.
Automated configurability Should Components should be configurable through deployment processes, allowing for automated setup and initialization (specifically of master data) by placing configuration files in the appropriate locations.
Health check Should It is crucial that each component includes a web endpoint to let Ozone verify it is operational within the HIS.
Prometheus metrics Should Providing Prometheus metrics is recommended to enhance monitoring and ensure effective system performance management.
Backup & restore Should Automated backup and restore capabilities ensure data integrity and system resilience in production use.
Modularity Should Modularitiy enables potential enhancements or modifications to be made via modules, plugins, or addons without affecting the core component.
HL7 FHIR API Should Providing HL7 FHIR API reduces development overhead for peer-to-peer HIS components routes within Ozone.
Event bus Could An event bus offers a more efficient method of dispatching information as it becomes available, eliminating the need for polling.

2   An interoperability framework

Ozone is powered by an interoperability EIP2 framework that orchestrates seamless data flows between health information system components — EMR, LIMS, pharmacy, accounting, BI, and more.

Sample data flows

Clinicians' drug orders in the EMR system automatically generate items on the patient bill.

Lab results entered into the LIMS by lab staff are immediately visible to clinicians in the EMR system.

Data analysts can perform real-time cross-analysis of clinical and billing data on the BI platform.

What Ozone is not

Ozone is not a fork of other open-source projects; it utilizes standard and officially released software components from various open-source communities.

Ozone packages the latest LTS3 versions of its components 'as-is'. Therefore it is not liable for any bugs, deficiencies, or performance issues in the bundled LTS versions of its components; these fall outside the purview of Ozone itself.


We generally do not document Ozone’s components. Instead we refer to their own official documentation as much as possible.

  1. Free and open-source software 

  2. Entreprise integration patterns 

  3. Long-term support