Page Comparison

Why are we doing this?

Problem statement

Doing modern analytics on OpenMRS data is challenging - even more so when national and global reporting requirements change frequently. Over the years, OpenMRS implementers have developed a variety of reporting solutions in response to customer demands for aggregate data, often housed in separate, aggregate data systems. They often rely on writing custom scripts in order to meet deadlines, meaning that every change to reporting indicators will require a manual fix. This limits the ability to re-use and sustainably scale these solutions among OpenMRS implementers. Additionally, calculating indicators within OpenMRS often leads to performance issues. 

One solution is to use an OpenMRS Analytics Engine that goes beyond extracting data from OpenMRS and calculates reporting indicators. This solution is currently in development by the Analytics Engine Squad.

A related solution is to extract and send the disaggregated data to a mediator, such as OpenHIM, that will in turn forward the data to a FHIR server and CQL engine, where the indicator calculations will be done.

Impact of this solution

More and more countries are seeking robust, interoperable solutions that will fit into an increasingly sophisticated health information exchange architecture based on recognized standards. By developing a proof of concept that demonstrates how OpenMRS patient data can be extracted and sent to a mediator and is standards-based, countries and implementers will have access to a proven solution that works and can be extended for use within their country's HIE architecture.