Probably rather an autocomplete text field.
Yes, so from a UI standpoint let’s think of it as some sort of tags or predefined labels.
This would help code attachments by mapping them to specific categories. After all EMR systems are all about coding observations.
Yes we could imagine that those categories/tags/labels could become queries filters.
This feature requires some UI/UX thinking. Adding categories will likely happen from the thumbnail, perhaps through a ‘+’ button popping up an autocomplete search field?
And then when categories have been applied, they should also display somewhere on the thumbnail. They should be visible enough to be useful, while not bloating the thumbnail (which is a small UI component).
From the backend perspective there is also some thinking about the best way to map those categories to an attachment. There is in fact no attachment DAO entity behind the scenes, it’s a complex obs. The question is: how to add categories to an obs then? We may need a new database table there…
@burke is suggesting to use concepts as categories, which obviously makes sense from a coding standpoint. A concept set could be used to define which concepts could be picked from.
Does that clarifies things a little? @burke do you agree?