Stream: conformance
Topic: Inheritance of meta-extensions defined on ElementDefinition
Abel Enthoven (Feb 20 2020 at 11:14):
Suppose I have a base profile containing an ElementDefinition which has the meta-extension 'elementdefinition-bestpractice' defined on it. Now I want to make a derived profile, adding the meta-extension 'elementdefinition-bindingName' to the same ElementDefinition. Then what does the meta extensions collection in the differential of the ElementDefinition look like?
- It contains both extensions, repeating the one found in the base ElementDefinition and adding the new one
- It contains only the added extension
I am asking because the default collection inheritance (e.g. for ElementDefinition.code) repeats all items (solution 1) but I heard rumours about the extensions collection inheritance being different
Grahame Grieve (Feb 20 2020 at 11:23):
I'm not actually sure what the snapshot generator does with extensions like this. But in principle. I'd expect the collections to collect. I suppose if the code was extra clever, it would consult the definition of the extension to see whether it can repeat
Abel Enthoven (Feb 20 2020 at 12:58):
Thanks @Grahame Grieve . The extra intelligence you mention would be useful for some use cases. Are you talking about a hypothetical new field/meta-extension in the extension-defining StructureDef?
Grahame Grieve (Feb 20 2020 at 20:44):
no it's already there
Last updated: Apr 12 2022 at 19:14 UTC
