Thanks @ball for starting this conversation, very important one.
OCL being able to provide concepts ready for the OpenMRS config (that’s the official name of what Iniz consumes) would be a terrific feature. I completely second @ssmusoke on this.
Another option that I have been working on is to simply being able to extract the above config from any OpenMRS instance that has Iniz installed. This would lead to a somewhat heavier process that would work this way:
OCL for concept management
→ concepts received on an OpenMRS “metadata instance” (running the OCL subscription module)
→ concept extracted as an OpenMRS config (aka ‘Iniz’ config)
→ config deployed on “real” instances running Iniz
That is a workaround where an intermediate “metadata instance” is used as a buffer between OCL and the target instances. It might still be used for a while though because the intermediate instance can also help maintain other pieces of metadata than concepts, and those could be exported as well in the very same fashion to be part of deployable configs aimed at real instances.
Lastly, and specifically in regards to CIEL, I intended to reach out to @akanter in the next few weeks to work out with him a way for CIEL releases to not only produce the usual SQL file but also new concepts as an OpenMRS config patch. This would allow implementers to start off the SQL dump at first and subsequently only add the CSV patches every time there’s a new CIEL release. Cc @jesplana.
P.S. Again, “OpenMRS config” refers to what is in the
configuration/ folder that Iniz consumes, see the README.