Stream: IG creation
Topic: Rendering issue with Slicing
Saul Kravitz (Oct 06 2020 at 17:15):
Something seriously awry with slicing in: https://saulakravitz.github.io/carin-bb-publish/StructureDefinition-C4BB-Organization.html
In the snapshot view, the identifier.type field appears twice.
Can someone please take a look: https://github.com/saulakravitz/carin-bb/blob/master/fsh/OrganizationProfile.fsh
@John Achoukian
Saul Kravitz (Oct 07 2020 at 21:09):
@Grahame Grieve -- apologies, but just wanted to make sure this one didn't slip through the cracks... (since you responded to my other issues, quickly, as usual). @Pat Taylor @Ryan Howells
Grahame Grieve (Oct 07 2020 at 21:12):
it's on my list
Grahame Grieve (Oct 07 2020 at 23:50):
so this is a consequence of the way you did the definitions - you defined a pattern, and you also walked into the element. Those are mutually incompatible, though I don't think we documented this that well. But it will most definitely lead to the outcome you see
Saul Kravitz (Oct 08 2020 at 13:13):
I figured I "stepped in it" somehow, but I don't understand the conflict. @Chris Moesel
Chris Moesel (Oct 08 2020 at 21:08):
Grahame Grieve said:
... you defined a pattern, and you also walked into the element. Those are mutually incompatible, though I don't think we documented this that well.
Is this an intentional limitation? Not all constraints can be expressed in a pattern. What happens if, like in this example, I need a pattern on identifier to satisfying the slicing criteria (which slices by pattern on $this) -- but I also need to mark something like identifier.type as must-support, or I want to require identifier.value, or even just define a short on identifier.value? All of those would require us to "walk into the element."
Grahame Grieve (Oct 08 2020 at 22:31):
I think it is but you could take it up on #conformance
Last updated: Apr 12 2022 at 19:14 UTC
