@mozzy thanks I also had a look yeah it only fires save events. Yeah, It implements AfterReturningAdvice which is better for an analytical solution than firing event before a transaction is committed as we do in openmrs-atom feed module.
But have only a limited set of resources available right but can be extended easily without much effort it seems.
And exactly as u said it doesn’t depend on any other bahmini module. But to save the fired events I think it is using ICT4h atomfeed server if am right. But in openmrs atomfeed also we are using the same way.
@mozzy it’s perfectly fine to do a FHIR communication channel between OpenMRS and OpenHIM with openmrs-eip in the middle. It’s exactly for such purposes that it was designed.
In this case you wouldn’t use its dbsync component (that’s an OpenMRS-OpenMRS only thing), it’s just about writing a couple of Camel routes to hydrate Debezium events with FHIR messages, and then making REST calls to OpenHIM.
perfect @mksd , i think thats the approach we would want take for this project . We will dicuss that approach more in the next design call . It woud do us very good if you can even attend our next call
@mksd out of nowhere . So isn’t dbsync the component which listens to mysql bin to retrive events ?. Or it is not and camel can be configured directly listen to events ?. I am asking because I am not familliar with any