FHIR:Vprepub-1.0 FHIR Profiling Guidelines R4 examples: verschil tussen versies

Uit informatiestandaarden
Ga naar: navigatie, zoeken
k (HOTFIX: Remove issue box)
(Update slice names according to camelCasing scheme)
 
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" />

Huidige versie van 12 apr 2021 om 09:40


Examples are provided in XML format but could have been in JSON format as well.

Slice examples in XML

This section provides guidance on how slicing is expected in R4 profiles that are created by Nictiz.

ValueSet binding examples in XML

This section provides guidance on translating ValueSet bindings from functional descriptions to FHIR for the R4 profiles that are created by Nictiz.

In each of the cases below, .min and .max may be used to further specify what is required.