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.

Slice definition to map the fixed values of a semantic code.

<element id="Observation.code.coding">
    <path value="Observation.code.coding"/>
    <slicing>
        <discriminator>
            <type value="value"/>
            <path value="$this"/>
        </discriminator>
        <rules value="open"/>
    </slicing>
    <min value="1"/>
</element>
<element id="Observation.code.coding:drugUseCode">
    <path value="Observation.code.coding"/>
    <sliceName value="drugUseCode"/>
    <min value="1"/>
    <max value="1"/>
    <patternCoding>
        <system value="http://snomed.info/sct"/>
        <code value="228366006"/>
    </patternCoding>
</element>

Slice definition to specify different variations of a concept.

<element id="Patient.identifier">
    <path value="Patient.identifier"/>
    <slicing>
        <discriminator>
            <type value="value"/>
            <path value="$this"/>
        </discriminator>
        <rules value="open"/>
    </slicing>
</element>
<element id="Patient.identifier:BSN">
    <path value="Patient.identifier"/>
    <patternIdentifier>
        <!--<use value="official"/> -->
        <system value="http://fhir.nl/fhir/NamingSystem/bsn"/>
    </patternIdentifier>
</element>

Slice definition to allow multiple ValueSet bindings.

<element id="Procedure.code.coding">
    <path value="Procedure.code.coding"/>
    <slicing>
        <discriminator>
            <type value="value"/>
            <path value="$this"/>
        </discriminator>
        <rules value="open"/>
    </slicing>
</element>
<element id="Procedure.code.coding:verrichtingTypeCodelijst">
    <path value="Procedure.code.coding"/>
    <sliceName value="verrichtingTypeCodelijst"/>
    <binding>
        <strength value="required"/>
        <description value="The name of the procedure using the Verrichtingenthesaurus DHD."/>
        <valueSet value="http://decor.nictiz.nl/fhir/ValueSet/2.16.840.1.113883.2.4.3.11.60.40.2.14.1.2--20171231000000"/>
    </binding>
</element>

Slice definition to specify the datatype(s) of the element

<element id="Observation.value[x]">
    <path value="Observation.value[x]"/>
    <slicing>
        <discriminator>
            <type value="type"/>
            <path value="$this"/>
        </discriminator>
        <rules value="open"/>
    </slicing>
</element>
<element id="Observation.value[x]:valueCodeableConcept">
    <path value="Observation.valueCodeableConcept"/>
    <sliceName value="valueCodeableConcept"/>
    <type>
        <code value="CodeableConcept"/>
    </type>
</element>
<element id="Observation.value[x]:valueQuantity">
    <path value="Observation.valueQuantity"/>
    <sliceName value="valueQuantity"/>
    <type>
        <code value="Quantity"/>
    </type>
</element>

Slice definition that combines the use of a semantic code and a HCIM concept

<element id="Observation.category">
    <path value="Observation.category" />
    <slicing>
        <discriminator>
            <type value="value" />
            <path value="$this" />
        </discriminator>
        <rules value="open" />
    </slicing>
    <min value="1" />
</element>
<element id="Observation.category:laboratoryTestResultCode">
    <path value="Observation.category" />
    <sliceName value="laboratoryTestResultCode" />
    <min value="1" />
    <max value="1" />
    <patternCodeableConcept>
        <coding>
            <system value="http://snomed.info/sct" />
            <code value="49581000146104" />
        </coding>
    </patternCodeableConcept>
</element>
<element id="Observation.category:ResultType">
    <path value="Observation.category" />
    <sliceName value="resultType" />
    <max value="1" />
    <binding>
        <strength value="required" />
        <description value="ResultaatTypeCodelijst" />
        <valueSetReference>
            <reference value="http://decor.nictiz.nl/fhir/ValueSet/2.16.840.1.113883.2.4.3.11.60.40.2.13.1.1--20171231000000" />
            <display value="ResultaatTypeCodelijst" />
        </valueSetReference>
    </binding>
</element>

Slice definition that descriminates on the conformance to a profile in a referenced resource.

<element id="DiagnosticReport.result">
    <path value="DiagnosticReport.result" />
    <slicing>
        <discriminator>
            <type value="profile" />
            <path value="resolve()" />
        </discriminator>
        <rules value="open" />
    </slicing>
    <max value="1" />
</element>
<element id="DiagnosticReport.result:measurementValue">
    <path value="DiagnosticReport.result" />
    <sliceName value="measurementValue" />
    <max value="1" />
    <type>
        <code value="Reference" />
        <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/zib-GeneralMeasurement" />
    </type>
</element>
<element id="DiagnosticReport.result:healthCondition">
    <path value="DiagnosticReport.result" />
    <sliceName value="healthCondition" />
    <max value="1" />
    <type>
        <code value="Reference" />
        <targetProfile value="http://nictiz.nl/fhir/StructureDefinition/zib-FunctionalOrMentalStatus" />
    </type>
</element>

@@ Regel 2: / Regel 2: @@
 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 for fixed values to map a semantic code.}}
+{{Collapse top|Slice definition to map the fixed values of a semantic code.|left=yes}}
 <syntaxhighlight lang="xml">
 <element id="Observation.code.coding">
@@ Regel 28: / Regel 28: @@
 {{Collapse bottom}}
-{{Collapse top|Slice to define different variations of the concept}}
+{{Collapse top|Slice definition to specify different variations of a concept.|left=yes}}
 <syntaxhighlight lang="xml">
 <element id="Patient.identifier">
@@ Regel 50: / Regel 50: @@
 {{Collapse bottom}}
-{{Collapse top|Slice to allow multiple ValueSet bindings}}
+{{Collapse top|Slice definition to allow multiple ValueSet bindings.|left=yes}}
 <syntaxhighlight lang="xml">
 <element id="Procedure.code.coding">
@@ Regel 74: / Regel 74: @@
 {{Collapse bottom}}
+{{Collapse top|Slice definition to specify the datatype(s) of the element|left=yes}}
-{{Collapse top|Slice to define element type(s)}}
 <syntaxhighlight lang="xml">
 <element id="Observation.value[x]">
@@ Regel 104: / Regel 103: @@
 {{Collapse bottom}}
+{{Collapse top|Slice definition that combines the use of a semantic code and a HCIM concept|left=yes}}
-{{Collapse top|Slice that combines the use of a semantic code and HCIM concept}}
 <syntaxhighlight lang="xml">
 <element id="Observation.category">
@@ Regel 146: / Regel 144: @@
 {{Collapse bottom}}
-{{Collapse top|Slice that is differentiated by the use of a profile in a referenced resource}}
+{{Collapse top|Slice definition that descriminates on the conformance to a profile in a referenced resource.|left=yes}}
 <syntaxhighlight lang="xml">
 <element id="DiagnosticReport.result">

FHIR:V1.0 FHIR Profiling Guidelines R4 examples: verschil tussen versies

Versie van 4 jan 2021 16:52

Slicing examples

Navigatiemenu

Zoeken