FHIR:Vprepub-1.0 FHIR Profiling Guidelines R4 examples - Bewerkingsoverzicht

Pieter Edelman: Update slice names according to camelCasing scheme

2021-04-12T09:40:15Z

Update slice names according to camelCasing scheme

← Oudere versie		Versie van 12 apr 2021 09:40
Regel 20:		Regel 20:
	</slicing>		</slicing>
	</element>		</element>
	<element id="Patient.identifier:~~BSN~~">		<element id="Patient.identifier:bsn">
	<path value="Patient.identifier"/>		<path value="Patient.identifier"/>
	<max value="1" />		<max value="1" />
Regel 45:		Regel 45:
	</slicing>		</slicing>
	</element>		</element>
	<element id="Observation.component:~~TypeOfTobaccoUsed~~">		<element id="Observation.component:typeOfTobaccoUsed">
	<path value="Observation.component" />		<path value="Observation.component" />
	<sliceName value="~~TypeOfTobaccoUsed~~" />		<sliceName value="typeOfTobaccoUsed" />
	<max value="1" />		<max value="1" />
	</element>		</element>
	<element id="Observation.component:~~TypeOfTobaccoUsed~~.code">		<element id="Observation.component:typeOfTobaccoUsed.code">
	<path value="Observation.component.code" />		<path value="Observation.component.code" />
	<min value="1"/>		<min value="1"/>
Regel 88:		Regel 88:
	</patternCodeableConcept>		</patternCodeableConcept>
	</element>		</element>
	<element id="Observation.category:~~ResultType~~">		<element id="Observation.category:resultType">
	<path value="Observation.category" />		<path value="Observation.category" />
	<sliceName value="resultType" />		<sliceName value="resultType" />

Pieter Edelman: HOTFIX: Remove issue box

2021-02-16T08:48:30Z

HOTFIX: Remove issue box

← Oudere versie		Versie van 16 feb 2021 08:48
Regel 1:		Regel 1:
	~~{{IssuePaginaWaarschuwing\|Sandbox\|FHIR:V1.0_FHIR_Profiling_Guidelines_R4_examples}}~~
	__NOINDEX__		__NOINDEX__

Pieter Edelman: Add ValueSet binding examples

2021-02-10T12:30:50Z

Add ValueSet binding examples

Wijzigingen bekijken

Pieter Edelman: Remove slice for semantic code

2021-01-28T08:48:06Z

Remove slice for semantic code

@@ Regel 24: / Regel 24: @@
          <system value="http://fhir.nl/fhir/NamingSystem/bsn"/>
      </patternIdentifier>
 </element>
 </syntaxhighlight>

Ardon Toonstra op 25 jan 2021 om 17:13

2021-01-25T17:13:31Z

← Oudere versie		Versie van 25 jan 2021 17:13
Regel 155:		Regel 155:
	{{Collapse bottom}}		{{Collapse bottom}}

	{{Collapse top\|Slice definition for multiple mapped concepts to one element that are discriminated by ~~the~~ conformance to a profile \|left=yes}}		{{Collapse top\|Slice definition for multiple mapped concepts to one element that are discriminated by their conformance to a profile. \|left=yes}}
	'''Note:''' try to avoid profile type discriminators as they are more costly to perform by a validator. This slicing definition is discriminated based on the conformance of the target resource to a profile. In this case, the path needs to include the resolve() function to indicate to the validator that is should resolve the reference.		'''Note:''' try to avoid profile type discriminators as they are more costly to perform by a validator. This slicing definition is discriminated based on the conformance of the target resource to a profile. In this case, the path needs to include the resolve() function to indicate to the validator that is should resolve the reference.

Ardon Toonstra op 25 jan 2021 om 17:11

2021-01-25T17:11:26Z

← Oudere versie		Versie van 25 jan 2021 17:11
Regel 4:		Regel 4:

	{{Collapse top\|Slice definition to specify 1 or more variations of a concept.\|left=yes}}		{{Collapse top\|Slice definition to specify 1 or more variations of a concept.\|left=yes}}
	The {{fhir:identifier}} element is sliced to provide the definition ~~for at least~~ one specific identifier.		The {{fhir:identifier}} element is sliced to provide the definition one specific identifier.

	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
Regel 27:		Regel 27:
	</syntaxhighlight>		</syntaxhighlight>
	{{Collapse bottom}}		{{Collapse bottom}}


	{{Collapse top\|Slice definition to map semantic codes to a repeating element.\|left=yes}}		{{Collapse top\|Slice definition to map semantic codes to a repeating element.\|left=yes}}

	Semantic code provides meaning to a part of or complete resource, e.g. a semantic code can be used to indicate that a {{fhir\|MedicationRequest}} represents a zib MedicationAgreement. These semantic codes often need to be present. To also allow other codes to be used they are profiled as patterns.		Semantic code provides meaning to a part of or complete resource, e.g. a semantic code can be used to indicate that a {{fhir\|MedicationRequest}} represents a zib MedicationAgreement. These semantic codes often need to be present. To also allow other codes to be used they are profiled as patterns.

Regel 131:		Regel 129:
	</syntaxhighlight>		</syntaxhighlight>
	{{Collapse bottom}}		{{Collapse bottom}}


	{{Collapse top\|Slice definition to allow multiple ValueSet bindings. \|left=yes}}		{{Collapse top\|Slice definition to allow multiple ValueSet bindings. \|left=yes}}
	'''Note:'''only applies in rare circumstances when different requirements are present for each ValueSet.		'''Note:''' only applies in rare circumstances when different requirements are present for each ValueSet.

	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">

Ardon Toonstra: /* Slice examples in XML */

2021-01-25T17:09:11Z

Slice examples in XML

Wijzigingen bekijken

Ardon Toonstra op 25 jan 2021 om 16:14

2021-01-25T16:14:10Z

@@ Regel 1: / Regel 1: @@
 __NOINDEX__
-=Slicing examples=
+=Slice examples in XML=
 This page provides guidance on how slicing is expected in R4 profiles that are created by Nictiz. Examples are provided in XML format but could have been in JSON format as well.
 {{Collapse top|Slice definition to map a semantic code.|left=yes}}
 <syntaxhighlight lang="xml">
 <element id="Observation.code.coding">
@@ Regel 26: / Regel 29: @@
      </patternCoding>
 </element>
 </syntaxhighlight>
 {{Collapse bottom}}

Ardon Toonstra: Textual improvements

2021-01-05T17:07:35Z

Textual improvements

← Oudere versie		Versie van 5 jan 2021 17:07
Regel 3:		Regel 3:
	This page provides guidance on how slicing is expected in R4 profiles that are created by Nictiz. Examples are provided in XML format but could have been in JSON format as well.		This page provides guidance on how slicing is expected in R4 profiles that are created by Nictiz. Examples are provided in XML format but could have been in JSON format as well.

	{{Collapse top\|Slice definition to map ~~the fixed values of~~ a semantic code.\|left=yes}}		{{Collapse top\|Slice definition to map a semantic code.\|left=yes}}
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
	<element id="Observation.code.coding">		<element id="Observation.code.coding">
Regel 29:		Regel 29:
	{{Collapse bottom}}		{{Collapse bottom}}

	{{Collapse top\|Slice definition to specify ~~different~~ variations of a concept.\|left=yes}}		{{Collapse top\|Slice definition to specify 1 or more variations of a concept.\|left=yes}}
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
	<element id="Patient.identifier">		<element id="Patient.identifier">
Regel 145:		Regel 145:
	{{Collapse bottom}}		{{Collapse bottom}}

	{{Collapse top\|Slice definition that ~~descriminates on~~ the conformance to a profile in a referenced resource.\|left=yes}}		{{Collapse top\|Slice definition for multiple mapped concepts to one element that are discriminated by the conformance to a profile in a referenced resource.\|left=yes}}
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
	<element id="DiagnosticReport.result">		<element id="DiagnosticReport.result">

Pieter Edelman: Create prepub environment from FHIR:V1.0

2021-01-05T13:41:28Z

Create prepub environment from FHIR:V1.0

← Oudere versie		Versie van 5 jan 2021 13:41
Regel 1:		Regel 1:
			__NOINDEX__
	=Slicing examples=		=Slicing examples=
	This page provides guidance on how slicing is expected in R4 profiles that are created by Nictiz. Examples are provided in XML format but could have been in JSON format as well.		This page provides guidance on how slicing is expected in R4 profiles that are created by Nictiz. Examples are provided in XML format but could have been in JSON format as well.