There is a growing need to align how to add tags or flags to individual patients.
Current Design Examples:
In a Header, or on a Patient Summary: The latest design proposed for an HIV Summary from this week’s 3.x Design call (though it can be extrapolated to any condition):
There’s a clear need to support patient tags in 3.x. So how do folks recommend we approach this?
What should we apply from the historic OMRS Patient Flags Module?
Or, the old work done on the Generic Tagging Module?
At least under the hood, we’ve tried to use the term “tags” within OpenMRS to reference a folksonomy (like Discourse or Wordpress topic tags or Atlassian labels), where the terminology doesn’t have to be pre-defined. So, I wouldn’t recommend using the generic tagging module.
The Patient Flags module is closer to the use case you’re describing for OMRS 3.0. It might be too old to be useful, but it does offer a REST API.
@grace I think patient flags would benefit from the computed concepts approach being designed and thought to by the @OHRI team - as the computations can become pretty expensive slowing down their usage