This architecture reduces software and code to maintain by respecting a separation of concerns for patients data – it is managed where it belongs.
This architecture reduces software and code to maintain by respecting a separation of concerns for patients data – it is managed where it belongs.
Ozone abides by MIT Governance Lab’s “don’t build it” principle wherever possible. It refrains from building features because they have most likely been developed elsewhere already, and are ready to be integrated.
Ozone’s vision is to coalesce existing digital health efforts together so that there is less code, more features and simplified and lighter software maintenance processes.
Ozone pledges to bundle digital health goods without forking or modifying them. This principle entertains a feedback loop where Ozone contributes mechanically to the success of its constitutive components by resourcing them.
OpenMRS 3 stands at the core of Ozone as its interoperable electronic medical record (EMR) system. It provides a rich and modern user experience built on the principles of user-centred design supported by extensive, detailed and meticulous research and user testing.
Ozone uses the community edition of OpenMRS 3 and helps improve and maintain it by continuously feeding back into it.
Health facilities require much more than documenting patient files (EMR/EHR) to effectively support all the workflows that take place across healthcare services delivery, for example:
Ozone goes beyond the EMR and EHR as an all-in-one patient management solution that can be deployed anywhere, from hospitals to community health programs operated at the last mile.
Ozone adapts to a large variety of clinical use cases thanks to its flexible and configurable modular opt-in architecture, it can be lightweight or exhaustive.
Ozone inherits all its features from the work done by the communities supporting its constitutive components. It just makes them work together as an easy-to-install enterprise-grade product.
All Ozone components are established free and open-source softwares of their own. They are governed, developed and maintained by their respective communities.
Because it ensures that there are no forks of the goods that Ozone is made of; in particular of OpenMRS 3 that is a Global Good and a Digital Public Good.
However this principle extends to all Ozone’s default components. Minor add-ons are sometimes needed to make them work together but Ozone otherwise strictly sticks to the official or community editions of SENAITE, Odoo and Superset.
We are working hard to provide multiple options for some components, and when we get there we will make sure that you can select your preferred blend of Ozone. In the meantime it is anyway possible to create your own distribution of Ozone with the changes and customizations that you wish to make. Reach out to the community to accomplish this.
The level, extend and nature of L1 support or close-up support that is needed vastly differs from project to project. Rather than attempting to embed a standard L1 support formula, we leave this item open to be dimensioned and organised in the way that best fits each Ozone implementation.
Not so much, we have made sure that Ozone FOSS is a ready-to-use and comprehensive health information system that is as close as possible to an enterprise-grade system.
However Ozone Pro does come with additional features that make it fully enterprise-grade. The biggest difference however is that Ozone Pro embeds a service level agreement.
For more details check our plans.
Yes, our intent is to stage new features as pro features until they can become FOSS for everyone.
A lot of investment and resources are being put in developing pro features. They deserve to be monetised for a while, thereby helping to make Ozone (Pro and FOSS) better and better.
Ozone is a product in motion and expansion and our developers are continuously working on improving Ozone and bringing new features.
It is probably ill-informed to engage in brand new features development, at least in the global health context – because oftentimes someone else has already gone through all the pain and hard work.
It also boils down to nurturing the open-source mentality of adopting and contributing to existing projects rather than dispersing resources in redoing too many variations on the same theme.
Please check Don’t Build It. A Guide for Practitioners in Civic Tech.
Type the following commands in a terminal:
git clone https://github.com/ozone-his/ozone-docker
cd ozone-docker
./start-demo.sh
Then start browsing Ozone:
Ozone emanates from the OpenMRS ecosystem, come join us write code to save lives!
Open digital health is a pillar of universal access to healthcare, and Ozone is building it.
The enterprise-grade
health information system
built with OpenMRS 3
Username: jdoe
Password: password