-
Change Request
-
Resolution: Persuasive with Modification
-
Very High
-
FHIR Core (FHIR)
-
R5
-
FHIR Infrastructure
-
StructureDefinition
-
Extensibility
-
-
Grahame Grieve/Ewout Kramer: 11-0-0
-
Enhancement
-
Compatible, substantive
-
R5
By default, when creating a new derived profile, the constraints from the base profile become part of the new derived profile. This is also true for all extensions.
There is however a (growing) list of extensions that should not be "inherited" from a base profile to a new derived profile.
We have agreed (see https://chat.fhir.org/#narrow/stream/179239-tooling/topic/Forge.20added.20extension.20explicit-type-name for a discussion) that authors of an extension (familiar with its scope and meaning) should be responsible for determining whether an extension should be inherited or not.
To make this possible, we should create an extension on StructureDefinition.