Stream: IG creation
Topic: Why this entrant in a Structure definition
Brian Reinhold (Sep 14 2018 at 15:19):
For some reason Forge populated all my display elements of a codeableConcept with this
<extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-translatable">
<valueBoolean value="true" />
</extension>
What is the implication of that entrant (I think I know) but why only on the display (maybe I don't know the implication)? What would be the consequences of removing it? My feeling is that it is Forge-specific and I can safely strip it out.
Michel Rutten (Sep 17 2018 at 09:07):
Hi @Brian Reinhold, this extension is inherited from the core datatype definition (profiles-types.xml). NB same extension is also introduced by the CodeableConcept.text element. Base constraints, incl. extensions, are included in the diff when you constrain an element.
IIRC, there is a GForge ticket that suggests to introduce a way for extensions to define the desired inheritance behavior. This would allow us to say that e.g. the translatable extensions shouldn't be inherited by derived profiles. I've hardcoded info about some known core extensions into Forge, to prevent these from being inherited (which confused users), however apparently Forge does not (yet) recognize the translateable extension.
Brian Reinhold (Sep 17 2018 at 09:14):
@Michel Rutten Okay, I think I partially understand. I just was not sure why it was there and only present in a few select elements. In particular the display element of a codeable concept but no others. Since I didn't know why it was there, if I were writing the SD from scratch, I would not have included it or thought to include it. So I wondered what the consequence of removing it would be.
At this time I have removed it and as far as I can tell , it makes no difference (so far) on the rendering done by the IG Publisher. But my guide is in a very youthful stage since I really have not yet grasped how all these details work. In Forge and Simplifer, all these details were hidden so you didn't have to pay attention to all the gory details. Now I have to code structure definitions using xml (the only tool I have is Notepad++)!
Michel Rutten (Sep 17 2018 at 09:21):
Hi @Brian Reinhold, these extensions are inherited implicitly anyway, so I think you can safely delete them from the diff. If necessary, you could always re-expand the snapshot the include all inherited constraints.
Brian Reinhold (Sep 24 2018 at 10:26):
Hi @Brian Reinhold, these extensions are inherited implicitly anyway, so I think you can safely delete them from the diff. If necessary, you could always re-expand the snapshot the include all inherited constraints.
@Michel Rutten I have. They were only present in a few elements. Always in display elements. Can't remember what else.
Last updated: Apr 12 2022 at 19:14 UTC
