Textual changes

resources/zib/zib-AbilityToDrink.xml

@@ -34,7 +34,7 @@
     <element id="Observation">
       <path value="Observation" />
       <short value="AbilityToDrink" />
-      <comment value="One concept of zib AbilityToDrink is represented using distinct Observation resources. These are grouped using the current resource and are referenced on `Observation.hasMember`:&#xD;&#xA;&#xD;&#xA;* DrinkingLimitations (NL-CM:4.8.4): [zib-AbilityToDrink.DrinkingLimitations](http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDrink.DrinkingLimitations)" />
+      <comment value="The DrinkingLimitations concept (NL-CM:4.8.4) is represented using distinct Observation resources, using profile [zib-AbilityToDrink.DrinkingLimitations](http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDrink.DrinkingLimitations). It is referenced from this resource using Observation.hasMember." />
       <alias value="VermogenTotDrinken" />
       <mapping>
         <identity value="zib-abilitytodrink-v3.1.1-2020EN" />

resources/zib/zib-AbilityToEat.xml

@@ -34,7 +34,7 @@
     <element id="Observation">
       <path value="Observation" />
       <short value="AbilityToEat" />
-      <comment value="One concept of zib AbilityToEat is represented using distinct Observation resources. These are grouped using the current resource and are referenced on `Observation.hasMember`:&#xD;&#xA;&#xD;&#xA;* EatingLimitations (NL-CM:4.7.4): [zib-AbilityToEat.EatingLimitations](http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToEat.EatingLimitations)" />
+      <comment value="The EatingLimitations concept (NL-CM:4.7.4) is represented using distinct Observation resources, using profile [zib-AbilityToEat.EatingLimitations](http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToEat.EatingLimitations). It is referenced from this resource using Observation.hasMember." />
       <alias value="VermogenTotEten" />
       <mapping>
         <identity value="zib-abilitytoeat-v3.1.1-2020EN" />

resources/zib/zib-PulseRate.xml

@@ -34,7 +34,7 @@
     <element id="Observation">
       <path value="Observation" />
       <short value="PulseRate" />
-      <comment value="**HL7 Vital Signs compatibility**&#xD;&#xA;&#xD;&#xA;Although this profile represents a vital signs measurement, it is *not* directly based on a HL7 Vital Signs profile because there isn't a direct counterpart in HL7 Vital Signs. Moreover the HL7 Vital Signs profiles contain two issues in their current version that prevent them from being used for the exchange of zibs (see below). However, an effort has been made to make this profile consistent with the (other) [HL7 Vital Signs profiles](https://www.hl7.org/fhir/R4/observation-vitalsigns.html), since the zib PulseRate is considered to be a vital sign. In particular it is closely related to the zib HeartRate, the profile of which is derived from its HL7 Vital Signs counterpart.&#xD;&#xA;&#xD;&#xA;**Differences with the HL7 Vital Signs profiles**&#xD;&#xA;&#xD;&#xA;* The _required_ terminology binding on `Observation.component` to the [Vital Signs Units](http://hl7.org/fhir/ValueSet/ucum-vitals-common) dataset makes it impossible to use `.component` for representing anything else than a Quantity (like a CodeableConcept or a boolean). This binding has therefore been omitted in the current profile.&#xD;&#xA;* The `mustSupport` = _true_ flag found on numerous elements isn't further specified in the HL7 Vital Signs IG, as is required by FHIR. This flag has therefore been omitted from the current profile.&#xD;&#xA;* The target restriction on `Observation.hasMember` and `Observation.derivedFrom` to a HL7 Vital Signs profile cannot be fulfilled. This restriction has therefore been omitted from the current profile.&#xD;&#xA;&#xD;&#xA;It might happen that for some concepts, the zib uses a different (but compatible) way than what is recommended by the [HL7 Vital Signs IG](http://hl7.org/fhir/r4/observation-vitalsigns.html). This is described in the comments for these concepts. There are also some differences in the profiling approach between the current profile and the HL7 profiles, like the use of patterns rather than slices with fixed systems and codes to enforce the inclusion of some coding (for reasons of consistency with other zib profiles, the former approach has been chosen here). Apart from what is mentioned above, constraints, invariants and terminology bindings have been copied from the HL7 Vital Signs profiles, but some textual descriptions have been omitted.&#xD;&#xA;&#xD;&#xA;Note: No equivalent for the HL7 Vital Signs base profile has been created to implement the zib profiles. The profile for this zib has been modelled taking the other HL7 Vital Signs profiles into consideration.&#xD;&#xA;&#xD;&#xA;One concept of zib PulseRate is represented using distinct Observation resources. These are grouped using the current resource and are referenced on `Observation.hasMember`:&#xD;&#xA;&#xD;&#xA;* PulseRegularity (NL-CM:12.7.5): [zib-PulseRate.PulseRegularity ](http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate.PulseRegularity)" />
+      <comment value="**HL7 Vital Signs compatibility**&#xD;&#xA;&#xD;&#xA;Although this profile represents a vital signs measurement, it is *not* directly based on a HL7 Vital Signs profile because there isn't a direct counterpart in HL7 Vital Signs. Moreover the HL7 Vital Signs profiles contain two issues in their current version that prevent them from being used for the exchange of zibs (see below). However, an effort has been made to make this profile consistent with the (other) [HL7 Vital Signs profiles](https://www.hl7.org/fhir/R4/observation-vitalsigns.html), since the zib PulseRate is considered to be a vital sign. In particular it is closely related to the zib HeartRate, the profile of which is derived from its HL7 Vital Signs counterpart.&#xD;&#xA;&#xD;&#xA;**Differences with the HL7 Vital Signs profiles**&#xD;&#xA;&#xD;&#xA;* The _required_ terminology binding on `Observation.component` to the [Vital Signs Units](http://hl7.org/fhir/ValueSet/ucum-vitals-common) dataset makes it impossible to use `.component` for representing anything else than a Quantity (like a CodeableConcept or a boolean). This binding has therefore been omitted in the current profile.&#xD;&#xA;* The `mustSupport` = _true_ flag found on numerous elements isn't further specified in the HL7 Vital Signs IG, as is required by FHIR. This flag has therefore been omitted from the current profile.&#xD;&#xA;* The target restriction on `Observation.hasMember` and `Observation.derivedFrom` to a HL7 Vital Signs profile cannot be fulfilled. This restriction has therefore been omitted from the current profile.&#xD;&#xA;&#xD;&#xA;It might happen that for some concepts, the zib uses a different (but compatible) way than what is recommended by the [HL7 Vital Signs IG](http://hl7.org/fhir/r4/observation-vitalsigns.html). This is described in the comments for these concepts. There are also some differences in the profiling approach between the current profile and the HL7 profiles, like the use of patterns rather than slices with fixed systems and codes to enforce the inclusion of some coding (for reasons of consistency with other zib profiles, the former approach has been chosen here). Apart from what is mentioned above, constraints, invariants and terminology bindings have been copied from the HL7 Vital Signs profiles, but some textual descriptions have been omitted.&#xD;&#xA;&#xD;&#xA;Note: No equivalent for the HL7 Vital Signs base profile has been created to implement the zib profiles. The profile for this zib has been modelled taking the other HL7 Vital Signs profiles into consideration.&#xD;&#xA;&#xD;&#xA;The PulseRegularity concept (NL-CM:12.7.5) is represented using distinct Observation resources, using profile [zib-PulseRate.PulseRegularity](http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate.PulseRegularity). It is referenced from this resource using Observation.hasMember." />
       <alias value="Polsfrequentie" />
       <mapping>
         <identity value="zib-pulserate-v3.3-2020EN" />