Closed craig-landry closed 1 year ago
Hey @craig-landry - anyone championing this should consider OpenMRS; as an active interoperability opportunity now exists with UgandaEMR. cc @SMurithi
Thank you. As with all product initiatives, we are eager to work with programs where we can get useful features into a real production environment, measure impact, and cooperatively iterate to make improvements. It helps a lot have these opportunities. Right now the Ecosystem FG is working on cht-pipeline functionality, but this interoperability initiative is up next and we'll include you in discussions for where to have the most impact.
Hi @brian256 and @SMurithi we (Medic) are exploring having an interoperability use case with OpenMRS. What workflows did you have in mind? We have built FHIR standards mediators for the CHT based on the OpenHIE architecture, you can review our repository and let us know if you have any questions. Our proof of concept was the loss to follow up workflow.
Is this ticket still relevant, or does #123 cover it already?
This is no longer relevant. I will remove it from the board.
As others noted, this is better described in https://github.com/medic/cht-roadmap/issues/123. This ticket is older and more general. The new style/format is a better representation of what's going on and more completable, where this "Interoperability" is more of a general area of work that will never be totally "done". I'm going to remove this from the board.
Overview CHT apps should interoperate with other digital health systems allowing critical functionality to exist without needing to be custom-coded into the app itself.