Stream: IG creation
Topic: reslicing eventCoding
Eric Haas (Dec 10 2019 at 13:45):
I think this has been brought up before but I can't find a solution:
I have created a test of this here: https://github.com/Healthedata1/IG-Template3/tree/test-coding-reslice
with the Structuredefinitions in here: https://github.com/Healthedata1/IG-Template3/tree/test-coding-reslice/source/resources
StructureDefinition-profile-test1-messageheader.xml
StructureDefinition-profile-test2-messageheader.xml
I constrain MessageHeader.event[x] to coding in test1 with an extensible binding like so...
using this elementdef in the diff:
<derivation value="constraint"/> <differential> <element id="MessageHeader"> <path value="MessageHeader"/> <mustSupport value="false"/> </element> <element id="MessageHeader.eventCoding"> <path value="MessageHeader.eventCoding"/> <min value="1"/> <max value="1"/> <type> <code value="Coding"/> </type> <mustSupport value="true"/> <binding> <strength value="extensible"/> <valueSet value="http://www.fhir.org/guides/test3/ValueSet/blah-codes"/> </binding> </element> </differential>
Eric Haas (Dec 10 2019 at 13:47):
... then try to reslice with a specific code using the pattern in a second profile test2 based on test1:
Eric Haas (Dec 10 2019 at 13:49):
looks nice in the rendered diff but the full view is all messed up :-(
Eric Haas (Dec 10 2019 at 13:51):
and qa error on the id and extension links...
here is the element definition:
<differential> <element id="MessageHeader"> <path value="MessageHeader"/> <mustSupport value="false"/> </element> <element id="MessageHeader.eventCoding"> <path value="MessageHeader.eventCoding"/> <sliceName name="eventCoding"/> <min value="1"/> <max value="1"/> <type> <code value="Coding"/> </type> <patternCoding> <system value="http://www.fhir.org/guides/test3/CodeSystem/blah-codes"/> <code value="blah"/> <display value="Blah"/> </patternCoding> </element> </differential>
Eric Haas (Dec 10 2019 at 13:53):
needless to say I tried a few things but seeking some help on how to do this with pattern and whether its me or an ig-pub thing
Grahame Grieve (Dec 10 2019 at 22:15):
my first question is why you are even talking about slicing? And then, why <sliceName name="eventCoding"/>
- there's no introduction of slicing other wise
so my second question is why this isn't just a snapshot generation error
Eric Haas (Dec 11 2019 at 00:24):
The snapshot generates a slice from "MessageHeader.eventCoding" so what should it be called when the element is constrained even further Anyway, I don't care what to call it, I just want a fix. So it sounds like its a snapshot generation error then? It doesn't matter if the sliceName is present or not - the same error and output occurs.
Grahame Grieve (Dec 11 2019 at 00:34):
there's definitely a bug in the snapshot generation; working on it now
Last updated: Apr 12 2022 at 19:14 UTC