Title. GSoC 2020 | Improvement to OpenMRS DHIS2 Integration
Description. We need to discuss the community’s requirements for the OpenMRS DHIS2 Integration
This module is followed by the great work done in the previous GSOC project .
The OpenMRS DHIS Integration Module gives a good overview of the module. Since this could be part of the CoVid-19 response I think this is quite urgent as well as an important project.
Title: How to: organize an OpenMRS Outreach Guide
This design call is to explore the best way to organize an outreach to sensitize the targeted community about OpenMRS. An Outreach is a predetermined visit executed by a member or members of OpenMRS focused on interesting the intended audience into contributing in different ways to OpenMRS .
We will explore:
Who should organize or get involved in an outreach.
What components ( e.g. information, other material) should be shared in an outreach.
How should an outreach be conducted?
When or how often should these outreaches be organized?
We need to find a time to continue the discussion about OCL interoperability that @ball kicked off a few days ago.
Title: OCL Interoperability with OpenMRS Production Deployments
Description: We need a common understanding and high level approach for OCL and OpenMRS interoperability beyond the subscription module. There’s good progress toward MVP of OCL for OpenMRS, but for PIH and deploying/updating production systems, this must include this full “happy path” from OCL -> Code -> OpenMRS Implementations. Is it possible to support Initializer (‘Iniz’) compatible csv format? Is this a good approach?
@mksd that was original suggestionl, but I think the feeling of others was that they didn’t want to try to cram too much into the OCL call. I still think it would make sense to discuss as part of the OCL call, but I’m happy either way, as long as the right people are in attendance.
The Condition List UI in core apps has been 90% ready-to-go for awhile now, and we’d like to get it over the finish line. However, that 10% that isn’t complete could potentially lead to a rabbit hole and lead to a lot of rework.
Can we have a design call to resolve these issues?
@mksd thanks… @burke had a very helpful post here Condition List Implementation that I think clarifies things a lot for me… still worth a design discussion though…
Title : Bahmni + OpenMRS PLIR Architectural Design
Description : @moshon presented a proposed architectural design for Bahmni’s PLIR (patient level indicator reporting) solution and much of it aligns with OpenMRS PLIR discussions, with one exception. @mozzy has started looking into the OpenMRS and Bahmni atomfeed modules, and debezium. At this design forum, we’ll discuss what he discovered - pros and cons - get additional input, and discuss what approach we’ll take.
