Stream: conformance
Topic: Forge slicing
Jonny Rylands (Mar 10 2016 at 23:28):
I believe you should be able to constraint the elements of a setup slice, as per Graeme Grieve:
"You can definitely constrain sub-elements of the setup slice. For example, you can say "the only kinds of telecoms allowed are phone numbers" and then slice to say that there must be one home number and can be up to two work numbers."
Is there any plan to support this in Forge?
Michel Rutten (Mar 11 2016 at 15:32):
Hi Jonny, yes I would like to support this, but it's challenging. I'll quote my response to Lloyd on this topic in the implementers chat today:
"In Forge, the element treeview represents slice constraints as child nodes of the sliced element. The original child elements of a sliced element are hidden in the treeview. The UI clearly expresses the relationship between the sliced element and the associated slices, however it also prevents the user from constraining the original child elements.
If the spec indeed allows this, then Forge should support it too. However I'm afraid that displaying both the original child elements as well slices will clutter the UI and is likely to confuse the user. Alternatively, displaying slices as following siblings (like they are defined in StructureDefinition) would require quite invasive and time-consuming changes in the application, and frankly that is not a feasible option at the moment. Some kind of toggle button that controls the visibility of the original child nodes might work, but I'm not fully convinced. I'll add an issue to our tracker and ponder on the UI."
Jonny Rylands (Mar 14 2016 at 12:11):
Michel - yes I appreciate creating an intuitive UI to represent this would be very tricky! Thanks.
Michel Rutten (Mar 14 2016 at 12:28):
Hi Jonny, I'm open to suggestions on how to present this in the Forge UI and welcome your input. So please feel free to share your thoughts.
Last updated: Apr 12 2022 at 19:14 UTC
