FHIR Chat · FORGE/Simplifier R4 extension on binding level · implementers

Stream: implementers

Topic: FORGE/Simplifier R4 extension on binding level

view this post on Zulip Robin Bosman (Jul 22 2019 at 13:37):

Was trying to implement this one on the a R4 patient structuredefinition via Forge:
https://www.hl7.org/fhir/extension-elementdefinition-maxvalueset.html
Should be extension on the ElementDefinition.binding -> I did not find how to do this in Forge - is it possible?
When I added it manually in the snapshot like below, it seems to work (tested with Hapi validator). However, Simplifier does not show it in its overview.

<binding>
            <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet">
                <valueCanonical value="https://www.ehealth.fgov.be/standards/fhir/ValueSet/be-contactperson" />
            </extension>
            <strength value="extensible" />
            <description value="The nature of the relationship between a patient and a contact person for that patient." />
            <valueSet value="http://hl7.org/fhir/ValueSet/patient-contactrelationship" />
        </binding>

view this post on Zulip Michel Rutten (Jul 22 2019 at 14:35):

Hi @Robin Bosman, yes, this is correct.
FHIR introduces a set of special meta-data extensions for StructureDefinition and ElementDefinition, e.g. to specify custom binding constraints, as in your example. However the Forge UI does not yet support such meta-extensions; they are not visible in the UI, and the author cannot add or edit them. However you can add them to a profile by manually editing the XML/JSON. Simplifier rendering logic does not yet display such meta-extensions. The .NET profile validator also does not recognize/verify custom constraints expressed via meta-extensions. So the actual benefits of using such custom meta-extensions are currently still quite limited.

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -