Bahmni: SNOMED vs SCT conflict

When you say “CIEL import”, your actually referring to the Subscription Module, which is different from CIEL. It’s important to be clear about this: the OCL Subscription Module is designed to load concepts and mappings from Open Concept Lab. It is not designed to handle managing all of the things that might be in the OpenMRS Concept Dictionary.

One of those things that it doesn’t manage is concept sources. I would recommend using the Initializer concept source domain, as was done in Grace’s PR, instead of using a Liquibase changeset for this. Managing data via Liquibase tends to be a bad idea over the long term (this is different from managing schemas, which is more or less what Liquibase is designed to handle).

From OCL’s perspective, SNOMED is an external source (i.e., there isn’t a “SNOMED CT” source in OCL to attach that metadata to). Even if we solved this for SNOMED CT, we’d have similar issues come up when we had any external source referenced from OCL. Even if we added that metadata in, we’d then need to change the subscription module to understand how to consume that metadata. By which I mean to say, yes this is solvable, but it’s creating a lot of work to do something we already have a mechanism for doing without a lot of clear value (maintaining the HL7 code for sources referenced from CIEL seems a bit beyond the scope of what CIEL has been doing).

If we make this “configurable”, what would the suggested way in which we do so? (I.e. what are we configuring?).

1 Like