Pieter Edelman: /* Datatype {{datatype|CodeableConcept}} */

2021-05-27T19:31:21Z

Datatype {{datatype|CodeableConcept}}

← Oudere versie		Versie van 27 mei 2021 19:31
Regel 200:		Regel 200:
	* The ConceptMap will be added using the extension [https://www.hl7.org/fhir/extension-11179-permitted-value-conceptmap.html permitted-value-conceptmap extension] on the FHIR ValueSet.		* The ConceptMap will be added using the extension [https://www.hl7.org/fhir/extension-11179-permitted-value-conceptmap.html permitted-value-conceptmap extension] on the FHIR ValueSet.
	===Datatype {{datatype\|CodeableConcept}}===		===Datatype {{datatype\|CodeableConcept}}===
	When not all codes from the functional specification map cleanly to a {{term\|required}} ValueSet from a FHIR base resource with datatype {{datatype\|~~code~~}}:		When not all codes from the functional specification map cleanly to a {{term\|required}} ValueSet from a FHIR base resource with datatype {{datatype\|CodeableConcept}}:
	* {{fhir\|CodeableConcept.coding}} will be sliced with a discriminator of <code>value</code>/<code>$this</code>, based on a {{term\|required}} binding on the {{fhir\|CodeableConcept.coding}} level.		* {{fhir\|CodeableConcept.coding}} will be sliced with a discriminator of <code>value</code>/<code>$this</code>, based on a {{term\|required}} binding on the {{fhir\|CodeableConcept.coding}} level.
	* A slice will be created that binds the ValueSet of the functional description:		* A slice will be created that binds the ValueSet of the functional description:

Pieter Edelman: Document how to bind additional ValueSets for CodeableConcepts

2021-05-27T19:30:42Z

Document how to bind additional ValueSets for CodeableConcepts

← Oudere versie		Versie van 27 mei 2021 19:30
Regel 191:		Regel 191:
	Also see the [[FHIR:V1.0 FHIR Profiling Guidelines R4 examples\|examples]].		Also see the [[FHIR:V1.0 FHIR Profiling Guidelines R4 examples\|examples]].
	==Handling conflicts with base bindings==		==Handling conflicts with base bindings==
	~~For~~ FHIR base resource ~~elements with datatype {{datatype\|code}} and binding~~ {{term\|required}} ~~it may be that~~ the functional ~~description~~ uses ~~other/additional codes to specialize the FHIR~~ codes. To conform to FHIR and the functional description:		FHIR base resource might specify a {{term\|required}} binding for some of its elements, whereas the corresponding concept in the functional specification uses alternative or more specialized codes. To conform both to FHIR and to the functional description, a ConceptMap will be created to map the codes from the functional specification to the codes from the FHIR ValueSet. This ConceptMap will be linked to the existing ValueSet using the extension [https://www.hl7.org/fhir/extension-11179-permitted-value-conceptmap.html permitted-value-conceptmap extension].

			If all mappings in the ConceptMap are {{term\|equal}} or {{term\|equivalent}}, no further action is needed.
			===Datatype {{datatype\|code}}===
			When not all codes from the functional specification map cleanly to a {{term\|required}} ValueSet from a FHIR base resource with datatype {{datatype\|code}}:
	* The ValueSet from the functional description will be bound with the binding strength of the functional concept using the {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/ext-CodeSpecification\|title=CodeSpecification}} extension. The extension slice is named after the full English name of the value set according to the functional description, in camelCased notation.		* The ValueSet from the functional description will be bound with the binding strength of the functional concept using the {{Simplifier\|http://nictiz.nl/fhir/StructureDefinition/ext-CodeSpecification\|title=CodeSpecification}} extension. The extension slice is named after the full English name of the value set according to the functional description, in camelCased notation.
	* Mapping to the concepts of the functional description is applied both to the FHIR element and the extension.		* Mapping to the concepts of the functional description is applied both to the FHIR element and the extension.
	* The ~~mapping will be documented in a~~ ConceptMap~~, which~~ will be ~~linked~~ using the extension [https://www.hl7.org/fhir/extension-11179-permitted-value-conceptmap.html permitted-value-conceptmap extension].		* The ConceptMap will be added using the extension [https://www.hl7.org/fhir/extension-11179-permitted-value-conceptmap.html permitted-value-conceptmap extension] on the FHIR ValueSet.
			===Datatype {{datatype\|CodeableConcept}}===
			When not all codes from the functional specification map cleanly to a {{term\|required}} ValueSet from a FHIR base resource with datatype {{datatype\|code}}:
			* {{fhir\|CodeableConcept.coding}} will be sliced with a discriminator of <code>value</code>/<code>$this</code>, based on a {{term\|required}} binding on the {{fhir\|CodeableConcept.coding}} level.
			* A slice will be created that binds the ValueSet of the functional description:
			** The slice is named after the full English name of the value set according to the functional description, in camelCased notation.
			** The binding strength is set to {{term\|required}}. This is needed in order to make a valid slice definition.
			** The minimum cardinality of the slice is set to 1; if the concept is included, bot the FHIR and function model codes are required.
			** The ConceptMap is documented using the permitted-value-conceptmap extension on the ValueSet bound in this slice.
			** {{fhir\|binding.description}} is set to: <q>In addition to a coding from this ValueSet, the corresponding coding from the FHIR base ValueSet SHALL be communicated. The ConceptMap <[canonical of ConceptMap]> can be used to relate these two ValueSets.</q>
			* Mapping to the concepts of the functional description is applied only to the FHIR element, not to the slice.

	=Extensions=		=Extensions=

Pieter Edelman: Clone of V1.0 production page for issue Github-53

2021-05-27T19:04:01Z

Clone of V1.0 production page for issue Github-53

Wijzigingen bekijken

FHIR:Vissue-Github-53 FHIR Profiling Guidelines R4 - Bewerkingsoverzicht

Pieter Edelman: /* Datatype {{datatype|CodeableConcept}} */

Pieter Edelman: Document how to bind additional ValueSets for CodeableConcepts

Pieter Edelman: Clone of V1.0 production page for issue Github-53