Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R4
-
FHIR Infrastructure
-
(NA)
-
-
Grahame Grieve / Bryn Rhodes: 11-0-0
-
Correction
-
Compatible, substantive
-
R5
Description
From https://chat.fhir.org/#narrow/stream/179177-conformance/topic/Context.20for.20Normative.20Version:
The normative-version extension has context 'element: StructureDefinition': https://www.hl7.org/fhir/extension-structuredefinition-normative-version.html
However, it seems to also be used in non-StructureDefinitions, like this OperationDefinition: https://www.hl7.org/fhir/operation-codesystem-lookup.xml.html#DomainResource.text.div-end
Also on, for example, the profile for the data type Identifier the extensions are both used on the StructureDefinition level (good), but also on deeper Element levels (bad): https://simplifier.net/packages/hl7.fhir.r4.core/4.0.1/files/82704/~xml
Since last release Forge copies the extensions on these elements to derived profiles. When validating these with the Java validator the error is thrown:
error: The extension http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version is not allowed to be used at this point (allowed = e:StructureDefinition; this element is [[StructureDefinition.differential.element, BackboneElement.element, ElementDefinition])
{{}}
Grahame replied: the context of use for the structure definition is too narrow; we use it in more places than that
Attachments
Issue Links
- mentioned in
-
Page Loading...