@michaelbontyes recently raised on Slack the idea of “tagging” concepts - and the more I think about it, the more I want this feature too! This is important and relevant for MSF, but increasingly relevant even for me as I try to build example content sets for sample clinical packages.
Scenario: Imagine you are an Implementer managing dictionaries and code sets for many different kinds of implementations around the world. You have different sets of code recommendations that vary by things like program area, type of site / site resources, by country, etc. There’s a lot of overlap between these different ways of categorizing your codes. So just having the linear Hierarchy of Organization, Source, and Collection doesn’t adequately help you slice-and-dice all the content you have to manage. Mappings don’t address this need because your goal here is not to link things together - it’s more that you want to categorize them, i.e. label related things.
Some practical examples:
Different teams may use these tags in different ways, but here are some ideas:
- Right now every time MSF has a new program, or new site, or new country implemenation, they have to create a new collection. They would rather just go through all the concepts in the MSFOCP source and tag these, rather than having to re-create new dictionaries and sources for each new use case. Then the tags could be used through a search to rapidly set up the new dictionaries needed (e.g. “show me everything that’s tagged with maternity”).
- “Forms warning”: MSF would like to tag all concepts used in Production forms with a “forms” tag, so that it’s plainly obvious which concepts are currently being used live. This could also help a content manager be aware to be especially careful changing these particular concepts. (@michaelbontyes do I have this quite right?)
- “moh731”: Imagine tagging all the concepts needed for a specific Ministry of health report, such as the Kenya MoH 731 reports. These may be spread across different collections.
- Tags for breaking down work you’ve done in a Dictionary: Right now I’m building sample Demo Dictionaries for a HIV and NCD demo packages. I want to put all the codes into a single collection for each of these, however, I wish I could filter the list by one category at a time, so that I can compare my Iniz .csv files to make sure I have all the concepts that I need for things like locations, programs, etc, which don’t automatically have a filter or concept type (nor should they) in the same way that Tests or Diagnoses do.