I’d started to come to the same conclusion, i.e. that this is probably best fixed by the kind of tooling guidance you have figured out.
Trying to come up with a modelling pattern, was just too hard.
@Ian_Bennett @richard.kavanagh - can we raise this with Benjamin re Better Studio? It is a common requirement and he may well recognise the issue himself.
@heidi.koikkalainen - this would solve our issue in the UCP context.
Other low-code implementers - suggest you follow this thread and take a view. @andrew.meiner @rong.chen @Sidharth_Ramesh
2 Likes
This may be an oversimplification of the areas raised above… However, we generally handle this through use of a generic (non openEHR) codedText input field on the form with dependencies that link to the archetyped fields on the form.
Thanks Ian,
I think the main request is that Studio should understands the “ShowAsSelectionList” tag (annotation), so that the ‘multiple checkbox’ pattern can be easily applied.
If that is done via a Generic facade, that would be fine, but ideally this would be bundled up with the dependency logic or a specific widget, to make this common pattern easy to apply.
2 Likes