Building a new UI from scratch called “OCL for OpenMRS”
It will be “official” and hosted on OCL servers
It will be built in a future-looking JS-based technology, and use the OCL REST API
It would specifically (and only) target the use case of managing OpenMRS dictionaries, so it will be less powerful but easier to use than the traditional OCL UI
The detailed concept and plan is outlined in this living doc(https://docs.google.com/document/d/1aQq3GowirojKG4Djvqn9RdAT9hP_WUw2l3KKyc2ThaM/edit).
Once this project is complete, a typical new OpenMRS implementation would no longer manage concepts via the OpenMRS UI at all. Instead your OpenMRS server would use the Open Concept Lab module to subscribe to a dictionary that you only manage on the cloud through this new application.
OCL's backend (https://github.com/OpenConceptLab/oclapi) is written in Python/Django and exposes a REST API that is used by the OCL for OpenMRS client. Current deployment is at https://api.demo.openconceptlab.org/.
What is a “Dictionary” and how does this compare to OCL’s existing domain model?
Add a reference to each custom concept from the other dictionary
Add all references that are in the other dictionary