2020-09-03: OpenMRS + Bahmni PLIR Architectural Design Session

@ayesh you better take time and read the readme: https://github.com/openmrs/openmrs-eip


@dkayiwa sure thanks

@ayesh all Camel routes feed off the main Debezium one, whether it is for pure OpenMRS syncing or for integration purposes.

As @dkayiwa suggested, please try to go through the READMEs. They are in a still imperfect state but there is a lot of info in there anyway :wink:


thanks alot @mksd

Hey everyone! I set up a poll to help us identify a good date/time for the Design Forum that @mozzy suggests. Please take the poll by Monday morning so that I can make a general announcement in a timely manner.

Here is the recording from Monday’s Design Forum: 2020-09-24 PLIR Architectural Design Forum.


Thanks for sharing this @jennifer. Is there a copy of the slide deck that @mozzy shared for further reference?

oh sure , you can find it here


FYI , form the design sessions , we are replacing the OpenMRS eip component with the Analytics engine .Both components depend on Apache Camel and an embeded Dbezium engine .see wiki .


@mozzy does the eip component serve the same purpose as the analytics engine?

The component of the analytics engine that we’re using (which is just the “export data from OpenMRS” component) works for what we would’ve used the eip component for here.

@dkayiwa , ideally both components can extract and export data(FHIR) from OpenMRS to an external system .

However ,the primarly function of the eip component is focused on two was Syncing between two Systems (OpenMRS and an external System) ,

but the primary function of the analytics engine is to export data to an external system . This is implemented Both in the Streaming and Batch mode , and using several approaches like using the Atomfeed and Dbezium .

Basically it has more Functions and features foccused on Data export than the eip component .

so i would say as far as merely data Export is concerned , the analytics engine is a preference