Thanks @dkayiwa for sharing the pointers to @gchan.
Mekom is an active maintainer of openmrs-eip. One of the internal components of openmrs-eip is ‘dbsync’, that helps support OpenMRS-OpenMRS sync through the embedded OpenMRS Camel component.
An important point to understand is that openmrs-eip enforces EIP around OpenMRS, but it is not a substitution to HIE patterns. In English: openmrs-eip solves low-level tech challenges around capturing data changes, orchestrating messages, routing messages, handling errors, … etc at the middleware layer.
There are a number of projects that currently leverage openmrs-eip’s dbsync to achieve one-way OpenMRS-OpenMRS sync as a proxy-HIE pattern within an OpenMRS-only ecosystem. We (at Mekom) do complement this with patient matching at the receiver end for instance, that thereby behaves partially like an MPI. Two-way sync will be on the roadmap for next year most likely.
Please don’t hesitate to get in touch privately if there is anything that you would which to fast-track through us, or publicly if you want to contribute to the current shared roadmap (that we are in the process of establishing.)