FHIR Chat · implementing Extension: permitted-value-conceptmap · implementers

Stream: implementers

Topic: implementing Extension: permitted-value-conceptmap

Stephan Opdenberg (Dec 16 2019 at 12:07):

Hi all. Is anyone familiar yet with the extension: permitted-value-conceptmap?
https://www.hl7.org/fhir/stu3/extension-11179-permitted-value-conceptmap.html
I am wondering how we could use this extension in our differntial while our valuesets are defined in the core resources. If anyone would have an example XML/JSON, that would be very helpfull.
Thanks!

Stephan Opdenberg (Dec 16 2019 at 13:16):

Would this be correct?

<element id="Encounter.class">
  <path value="Encounter.class" />
  <binding>
    <strength value="extensible" />
    <valueSetReference>
      <extension url="http://hl7.org/fhir/StructureDefinition/11179-permitted-value-conceptmap">
      <valueReference>
        <reference value="http://nictiz.nl/fhir/ConceptMap/ContactTypeCodelijst-to-ActEncounterCode" />
        <display value="ContactTypeCodelijst-to-ActEncounterCode" />
      </valueReference>
      </extension>
      <reference value="http://hl7.org/fhir/ValueSet/v3-ActEncounterCode" />
    </valueSetReference>
  </binding>

Grahame Grieve (Dec 16 2019 at 13:52):

yeah pretty much

Stephan Opdenberg (Dec 16 2019 at 15:08):

Thanks!

Lloyd McKenzie (Dec 16 2019 at 15:53):

"Permitted value" is a slightly odd concept. It doesn't constrain what's sent over the wire, it constrains what's stored - in situations where what comes over the wire and what's stored is different. If you want to constrain what comes over the wire, us the element.binding structure.

Grahame Grieve (Dec 16 2019 at 19:47):

"constrain" isn't the right word. I've run across multiple implementers using it along with ElementDefinition.mapping to map from some external source (not always a database) to the profile

Last updated: Apr 12 2022 at 19:14 UTC