diff --git a/SearchParameters/SearchParameter-Flag-category.xml b/SearchParameters/SearchParameter-Flag-category.xml
new file mode 100644
index 000000000..3d59bb290
--- /dev/null
+++ b/SearchParameters/SearchParameter-Flag-category.xml
@@ -0,0 +1,21 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-DevelopmentChild-01.xml b/examples/nl-core-DevelopmentChild-01.xml
new file mode 100644
index 000000000..26e7f681c
--- /dev/null
+++ b/examples/nl-core-DevelopmentChild-01.xml
@@ -0,0 +1,135 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-LifeStance-01.xml b/examples/nl-core-LifeStance-01.xml
new file mode 100644
index 000000000..9c3a02c70
--- /dev/null
+++ b/examples/nl-core-LifeStance-01.xml
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-Pregnancy.DateLastMenstruation-01.xml b/examples/nl-core-Pregnancy.DateLastMenstruation-01.xml
new file mode 100644
index 000000000..562af07e4
--- /dev/null
+++ b/examples/nl-core-Pregnancy.DateLastMenstruation-01.xml
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-Pregnancy.EstimatedDateOfDelivery-01.xml b/examples/nl-core-Pregnancy.EstimatedDateOfDelivery-01.xml
new file mode 100644
index 000000000..9fdbb6e47
--- /dev/null
+++ b/examples/nl-core-Pregnancy.EstimatedDateOfDelivery-01.xml
@@ -0,0 +1,34 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-Pregnancy.Parity-01.xml b/examples/nl-core-Pregnancy.Parity-01.xml
new file mode 100644
index 000000000..e435c8322
--- /dev/null
+++ b/examples/nl-core-Pregnancy.Parity-01.xml
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-Pregnancy.PregnancyDuration-01.xml b/examples/nl-core-Pregnancy.PregnancyDuration-01.xml
new file mode 100644
index 000000000..3bdbd797e
--- /dev/null
+++ b/examples/nl-core-Pregnancy.PregnancyDuration-01.xml
@@ -0,0 +1,31 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -31,13 +17,10 @@
-
-
-
-
+
-
+
diff --git a/examples/nl-core-Procedure-event-03.xml b/examples/nl-core-Procedure-event-03.xml
deleted file mode 100644
index 5b9b0b09e..000000000
--- a/examples/nl-core-Procedure-event-03.xml
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-SkinDisorder-01.xml b/examples/nl-core-SkinDisorder-01.xml
new file mode 100644
index 000000000..5657c15b7
--- /dev/null
+++ b/examples/nl-core-SkinDisorder-01.xml
@@ -0,0 +1,53 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/examples/nl-core-TextResult-01.xml b/examples/nl-core-TextResult-01.xml
index d74e2d251..8ea7e76a4 100644
--- a/examples/nl-core-TextResult-01.xml
+++ b/examples/nl-core-TextResult-01.xml
@@ -25,7 +25,7 @@
-
+
diff --git a/examples/nl-core-TextResult.VisualResult-01.xml b/examples/nl-core-TextResult.VisualResult-01.xml
index db42b52b1..1579c1877 100644
--- a/examples/nl-core-TextResult.VisualResult-01.xml
+++ b/examples/nl-core-TextResult.VisualResult-01.xml
@@ -8,7 +8,7 @@
-
+
diff --git a/known-issues.yml b/known-issues.yml
index 1baa6fd04..fa3899ef8 100644
--- a/known-issues.yml
+++ b/known-issues.yml
@@ -45,13 +45,13 @@ pattern-GstdSimpleQuantity:
ignored issues:
StructureDefinition:
- message: "Rule sd-pg-08: 'The title of the StructureDefinition should conform to the profiling guidelines'"
- reason: The title is shown in the hosting profiles as the name of the datatype. "G-Standaard SimpleQuantity" is more descriptive than the title according to the profiling guidelines ("pattern GstdSimpleQuantity").
+ reason: The title is shown in the hosting profiles as the name of the datatype. "G-Standard SimpleQuantity" is more descriptive than the title according to the profiling guidelines ("pattern GstdSimpleQuantity").
pattern-GstdQuantity:
ignored issues:
StructureDefinition:
- message: "Rule sd-pg-08: 'The title of the StructureDefinition should conform to the profiling guidelines'"
- reason: The title is shown in the hosting profiles as the name of the datatype. "G-Standaard Quantity" is more descriptive than the title according to the profiling guidelines ("pattern GstdQuantity").
+ reason: The title is shown in the hosting profiles as the name of the datatype. "G-Standard Quantity" is more descriptive than the title according to the profiling guidelines ("pattern GstdQuantity").
pattern-NlCoreHealthProfessionalReference:
ignored issues:
@@ -64,24 +64,24 @@ pattern-VitalSigns:
Observation.category:VSCat:
- message: "Rule sd-pg-13: 'Slice names should be camelCased starting with a lowercase letter.'"
reason: This slice name is adopted from the Vital Signs profile.
-
+
pattern-ZibHealthProfessionalReference:
ignored issues:
StructureDefinition:
- message: "Rule sd-pg-08: 'The title of the StructureDefinition should conform to the profiling guidelines'"
reason: The title is shown in the hosting profiles as the name of the datatype. "zib HealthProfessional Reference" is more descriptive than the title according to the profiling guidelines ("pattern ZibHealthProfessionalReference").
-
+
zib-AbilityToUseToilet:
zib deviations:
Observation:
- - short: AbilityToUseToilet
- reason: The root concept name 'ToiletUseAbility' is a mistake in the zib and will be fixed in the next prepublication.
+ - short: AbilityToUseToilet instead of ToiletUseAbility
+ reason: The root of the zib is called "ToiletUseAbility" (which is incorrect), even though the zib itself is called "AbilityToUseToilet".
zib-AbilityToGroom:
zib deviations:
Observation:
- - short: AbilityToGroom
- reason: The root of the zib is still called AbilityToGroome (which is incorrect), even though the zib itself has been renamed.
+ - short: AbilityToGroom instead of AbilityToGroome
+ reason: The root of the zib is called "AbilityToGroome" (which is incorrect), even though the zib itself is called "AbilityToGroom".
zib-AddressInformation:
zib deviations:
@@ -111,7 +111,7 @@ zib-AllergyIntolerance:
zib-ApgarScore-*Minute:
zib deviations:
Observation.component:muscleToneScore.value[x]:
- - short: MuscleToneScore
+ - short: MuscleToneScore instead of MusleToneScore
reason: The zib concept name "MusleToneScore" is an incorrect translation of the Dutch name into English.
zib-BloodPressure:
@@ -170,6 +170,9 @@ zib-ContactPerson:
zib-Encounter:
ignored issues:
+ Encounter.participant:healthProfessional.individual:
+ - message: "Rule sd-zpg-03: 'References to other resource profiles should be added next to the HL7 base references.'"
+ reason: The restriction only applies to, and defines, this slice. The slicing is open so the base references can still be used.
Encounter.reasonReference:*:
- message: "Rule sd-zpg-03: 'References to other resource profiles should be added next to the HL7 base references.'"
reason: The restriction only applies to, and defines, this slice. The slicing is open so the base references can still be used.
@@ -190,18 +193,18 @@ zib-Encounter:
zib-FLACCpainScale:
zib deviations:
Observation:
- - short: FLACCpainScale
- reason: The root concept name 'FLACCpainScore' is a mistake in the zib and will be fixed in the next pre-publication.
+ - short: FLACCpainScale instead of FLACCpainScore
+ reason: The root of the zib is called "FLACCpainScore" (which is incorrect), even though the zib itself is called "FLACCpainScale".
zib-FreedomRestrictingIntervention:
ignored issues:
- Procedure.reasonReference:legalSituation:
+ Procedure.reasonReference:legalSituation-*:
- message: "Rule sd-zpg-03: 'References to other resource profiles should be added next to the HL7 base references.'"
reason: The restriction only applies to, and defines, this slice. The slicing is open so the base references can still be used.
zib deviations:
Procedure:
- short: FreedomRestrictingIntervention instead of FreedomrestrictingIntervention
- reason: The root of the zib is called FreedomrestrictingIntervention (which is incorrect), even though the zib itself is called FreedomRestrictingIntervention.
+ reason: The root of the zib is called "FreedomrestrictingIntervention" (which is incorrect), even though the zib itself is called "FreedomRestrictingIntervention".
zib-FunctionalOrMentalStatus:
zib deviations:
@@ -221,7 +224,7 @@ zib-HealthcareProvider:
reason: The cardinality mismatch between the zib (0..1) and FHIR (0..*) is explained by the missing root element of zib part ContactInformation in FHIR. Instead, the two containers of the zib (TelephoneNumbers and EmailAddresses), which both have a cardinality of 0..*, are mapped directly into the resource. Thereby this mapping is still honoring the cardinality requirements of the zib.
Location.telecom*:
- datatype: ContactPoint instead of a reference
- reason: ContactInformation in FHIR is represented using the ContactPoint datatype, not as a separate resource. Because the FHIR profile for ContactInformation consists of two parts the root concept of the ContactInformation is mapped on .telecom.
+ reason: ContactInformation in FHIR is represented using the ContactPoint datatype, not as a separate resource. Because the FHIR profile for ContactInformation consists of two parts the root concept of ContactInformation is mapped on .telecom.
zib-HealthProfessional-Practitioner:
zib deviations:
@@ -236,7 +239,7 @@ zib-HealthProfessional-Practitioner:
reason: The cardinality mismatch between the zib (0..1) and FHIR (0..*) is explained by the missing root element of zib part ContactInformation in FHIR. Instead, the two containers of the zib (TelephoneNumbers and EmailAddresses), which both have a cardinality of 0..*, are mapped directly into the resource. Thereby this mapping is still honoring the cardinality requirements of the zib.
Practitioner.telecom*:
- datatype: ContactPoint instead of a reference
- reason: ContactInformation in FHIR is represented using the ContactPoint datatype, not as a separate resource. Because the FHIR profile for ContactInformation consists of two parts the root concept of the ContactInformation is mapped on .telecom.
+ reason: ContactInformation in FHIR is represented using the ContactPoint datatype, not as a separate resource. Because the FHIR profile for ContactInformation consists of two parts the root concept of ContactInformation is mapped on .telecom.
Practitioner.address:
- datatype: Address instead of a reference
reason: An address in FHIR is represented using the Address datatype, not as a separate resource.
@@ -248,7 +251,7 @@ zib-HealthProfessional-PractitionerRole:
reason: The cardinality mismatch between the zib (0..1) and FHIR (0..*) is explained by the missing root element of zib part ContactInformation in FHIR. Instead, the two containers of the zib (TelephoneNumbers and EmailAddresses), which both have a cardinality of 0..*, are mapped directly into the resource. Thereby this mapping is still honoring the cardinality requirements of the zib.
PractitionerRole.telecom*:
- datatype: ContactPoint instead of a reference
- reason: ContactInformation in FHIR is represented using the ContactPoint datatype, not as a separate resource. Because the FHIR profile for ContactInformation consists of two parts the root concept of the ContactInformation is mapped on .telecom.
+ reason: ContactInformation in FHIR is represented using the ContactPoint datatype, not as a separate resource. Because the FHIR profile for ContactInformation consists of two parts the root concept of ContactInformation is mapped on .telecom.
zib-HearingFunction.HearingAid:
ignored issues:
@@ -264,7 +267,7 @@ zib-HearingFunction.HearingAid:
reason: The referenced zib AnatomicalLocation is profiled on a datatype level and not a resource. Therefore it cannot be referenced, rather its concepts and constraints are added inline. This element conforms to the zib AnatomicalLocation.
DeviceUseStatement.timing[x]:timingPeriod.end:
- short: EndDate instead of EindDatum
- reason: Incorrect short in zib definition. This is reported in https://bits.nictiz.nl/browse/ZIB-1534.
+ reason: The zib concept name "EindDatum" has not been translated into English.
zib-HearingFunction.HearingAid.Product:
ignored issues:
@@ -290,6 +293,9 @@ zib-LaboratoryTestResult:
Observation.performer:performer:
- message: "Rule sd-zpg-03: 'References to other resource profiles should be added next to the HL7 base references.'"
reason: The restriction only applies to, and defines, this slice. The slicing is open so the base references can still be used.
+ Observation.hasMember:laboratoryTest:
+ - message: "Rule sd-zpg-03: 'References to other resource profiles should be added next to the HL7 base references.'"
+ reason: The restriction only applies to, and defines, this slice. The slicing is open so the base references can still be used.
zib deviations:
Observation.status:
- cardinality: 1..1 instead of 0..1
@@ -302,7 +308,7 @@ zib-LaboratoryTestResult:
reason: In FHIR there's no datatype ANY. All stated datatypes in the description can be accommodated using this element (Quantity and CodeableConcept are in fact both supported).
Observation.referenceRange.*:
- datatype: Quantity instead of ANY
- reason: The zib concepts ReferenceRangeUpperLimit and ReferenceRangeLowerLimit are defined as datatype ANY, but it is unclear how these concepts should work for anything that is not a Quantity. In addition, there's no obvious way in FHIR to support reference values other than of type Quantity (with the possible exception of String). Until this issue is resolved, support for reference ranges in the profile has been restricted to Quantity. See https://bits.nictiz.nl/browse/ZIB-1703.
+ reason: The zib concepts ReferenceRangeUpperLimit and ReferenceRangeLowerLimit are defined as datatype ANY, but these concepts only have meaning when they apply to a Quantity. See https://bits.nictiz.nl/browse/ZIB-1703.
zib-LaboratoryTestResult.Specimen:
zib deviations:
@@ -311,7 +317,7 @@ zib-LaboratoryTestResult.Specimen:
reason: Although a single SpecimenId is allowed according to the zib, .identifier is often used for additional identifiers outside the scope of the zib. It's not possible to create a slice or pattern specifically for SpecimenId without further formal requirements by the zib.
Specimen.subject:
- datatype: Reference instead of string
- reason: The zib concept SpecimenSource is communicated using a string within the profile zib-LaboratoryTestResult.Specimen.Source, which is referenced here.
+ reason: The zib concept SpecimenSource is communicated using a string within the profile zib-LaboratoryTestResult.SpecimenSource, which is referenced here.
Specimen.collection.bodySite:
- datatype: CodeableConcept instead of a reference
reason: Zib AnatomicalLocation is implemented as a datatype profile on CodeableConcept, so the datatype is not a Reference.
@@ -325,7 +331,7 @@ zib-LaboratoryTestResult.Specimen:
- cardinality: 1..1 instead of 0..1
reason: The value in the extension is 1..1, but the extension itself is 0..1, effectively matching the zib cardinality.
-zib-LaboratoryTestResult.Specimen.Source:
+zib-LaboratoryTestResult.SpecimenSource:
zib deviations:
Device.deviceName.name:
- cardinality: 1..1 instead of 0..1
@@ -348,7 +354,7 @@ zib-MedicalDevice:
reason: This is a special slice that represents situations where zib MedicalDevice is referenced from another zib through the reasonReference element. Because this reference is reversed in FHIR, this profile needs to contain the mappings for the references in _all_ these zibs. A common slice is defined with an indicative name rather than the name of all the targets.
DeviceUseStatement.timing[x]:timingPeriod.end:
- short: EndDate instead of EindDatum
- reason: Incorrect short in zib definition. This is reported in https://bits.nictiz.nl/browse/ZIB-1534.
+ reason: The zib concept name "EindDatum" has not been translated into English.
zib-MedicalDevice.Product:
zib deviations:
@@ -379,19 +385,19 @@ zib-MedicationContraIndication:
zib deviations:
Flag.code:
- cardinality: 1..1 instead of 0..1
- reason: Flag.code is manadatory in FHIR. The cardinality matches the cardinality of the zib, but not the conceptual cardinality. This should not be a major problem, as a contraindication is useless without specifying what it pertains to.
+ reason: Flag.code is mandatory in FHIR. The cardinality matches the cardinality of the zib, but not the conceptual cardinality. This should not be a major problem, as a contraindication is useless without specifying what it pertains to.
zib-NameInformation:
zib deviations:
HumanName.prefix:
- cardinality: 0..* instead of 0..1
- reason: prefix and suffix are mapped to the "titles" concept from the zib. There's a mismatch however in the way this information is represented in the zib and in FHIR. The mapping is documented in the profile.
+ reason: Both prefix and suffix are mapped to the "titles" concept from the zib. There's a mismatch however in the way this information is represented in the zib and in FHIR. The mapping is documented in the profile.
HumanName.suffix:
- cardinality: 0..* instead of 0..1
- reason: prefix and suffix are mapped to the "titles" concept from the zib. There's a mismatch however in the way this information is represented in the zib and in FHIR. The mapping is documented in the profile.
+ reason: Both prefix and suffix are mapped to the "titles" concept from the zib. There's a mismatch however in the way this information is represented in the zib and in FHIR. The mapping is documented in the profile.
HumanName.given:
- short: FirstName / Initial
- reason: The zib defines both the complete list of first names and of initals as a single string. In FHIR this is done fundamentally different, by using separate names. Hence, the short has been changed to the singular form.
+ reason: The zib defines both the complete list of first names and of initials as a single string. In FHIR this is done fundamentally different, by using separate names. Hence, the short has been changed to the singular form.
- alias: first name,middle name,Voornaam,Initiaal
reason: The first two initials are provided by FHIR. For the singular form of the latter two, see the remark above.
- cardinality: 0..* instead of 0..1
@@ -410,13 +416,13 @@ zib-NursingIntervention:
zib deviations:
CarePlan.activity.detail.scheduled[x]:scheduledTiming.repeat.frequency:
- datatype: positiveInt instead of Quantity
- reason: zib concepts Interval and Frequency are represented by a combination of .frequency, .period and .periodUnit, not by a single element of Quantity datatype.
+ reason: The zib concepts Interval and Frequency are represented by a combination of .frequency, .period and .periodUnit, not by a single element of Quantity datatype.
CarePlan.activity.detail.scheduled[x]:scheduledTiming.repeat.period:
- datatype: decimal instead of Quantity
- reason: zib concepts Interval and Frequency are represented by a combination of .frequency, .period and .periodUnit, not by a single element of Quantity datatype.
+ reason: The zib concepts Interval and Frequency are represented by a combination of .frequency, .period and .periodUnit, not by a single element of Quantity datatype.
CarePlan.activity.detail.scheduled[x]:scheduledTiming.repeat.periodUnit:
- datatype: code instead of Quantity
- reason: zib concepts Interval and Frequency are represented by a combination of .frequency, .period and .periodUnit, not by a single element of Quantity datatype.
+ reason: The zib concepts Interval and Frequency are represented by a combination of .frequency, .period and .periodUnit, not by a single element of Quantity datatype.
CarePlan.activity.detail.extension:medicalDevice.value[x]:
- cardinality: 0..1 instead of 0..*
reason: The value of the extension can only occur once, but the use of the extension itself is unlimited, making the effective cardinality 0..* as required by the zib.
@@ -427,7 +433,7 @@ zib-NursingIntervention:
CarePlan.activity.detail.performer:*:
- message: "Rule sd-zpg-03: 'References to other resource profiles should be added next to the HL7 base references.'"
reason: The slice is constrained on the target profile because this is what defines the slice. The HL7 base references are still available in the default slice.
-
+
zib-Patient:
zib deviations:
Patient.extension:nationality.extension:code.value[x]:
@@ -495,7 +501,7 @@ zib-PharmaceuticalProduct:
reason: The appropriate representation of Ingredient in FHIR is Medication.ingredient. The container can be properly mapped to this BackboneElement.
Medication.ingredient.strength:
- datatype: Ratio instead of Container
- reason: The `ingredient.strength` acts as a container for the two child elements and can the be correctly mapped to the zib Concentration container.
+ reason: The .ingredient.strength acts as a container for the two child elements and can thus be correctly mapped to the zib Concentration container.
zib-Payer.InsuranceCompany:
zib deviations:
@@ -562,20 +568,20 @@ zib-Refraction:
- datatype: CodeableConcept
reason: The zib has both a reference to AnatomicalLocation and a mapping on AnatomicalLocation::Laterality, while it seems only the latter is important. This leads to unexpected results. https://bits.nictiz.nl/browse/ZIB-1442.
Observation.component:cylindricalRefractionAxis.value[x]:
- - short: CylindricalRefractionAxis
- reason: The zib concept name "CilindricRefractionAxis" contains a typo which is corrected in a later release of the zibs.
+ - short: CylindricalRefractionAxis instead of CilindricRefractionAxis
+ reason: The zib concept name "CilindricRefractionAxis" is an incorrect translation of the Dutch name into English.
Observation.component:prismValue.value[x]:
- - short: PrismValue
- reason: The zib concept name "PrismaValue" contains a typo which is corrected in a later release of the zibs.
+ - short: PrismValue instead of PrismaValue
+ reason: The zib concept name "PrismaValue" is an incorrect translation of the Dutch name into English.
Observation.component:prismBase.value[x]:
- - short: PrismBase
- reason: The zib concept name "PrismaBase" contains a typo which is corrected in a later release of the zibs.
+ - short: PrismBase instead of PrismaBase
+ reason: The zib concept name "PrismaBase" is an incorrect translation of the Dutch name into English.
Observation.component:sphericalRefractionValue.value[x]:
- - short: SphericalRefractionValue
- reason: The zib concept name "SfericRefractionValue" contains a typo which is corrected in a later release of the zibs.
+ - short: SphericalRefractionValue instead of SfericRefractionValue
+ reason: The zib concept name "SfericRefractionValue" is an incorrect translation of the Dutch name into English.
Observation.component:sphericalEquivalent.value[x]:
- - short: SphericalEquivalent
- reason: The zib concept name "SfericalEquivalent" contains a typo which is corrected in a later release of the zibs.
+ - short: SphericalEquivalent instead of SfericalEquivalent
+ reason: The zib concept name "SfericalEquivalent" is an incorrect translation of the Dutch name into English.
zib-SOAPReport:
zib deviations:
@@ -598,20 +604,26 @@ zib-SOAPReport.SOAPLine:
- cardinality: 1..1 instead of 0..1
reason: The cardinality of both zib (SOAPLineHeader) and FHIR is 1..1, but because of conceptual cardinality 0..1 is expected. In case of absent data, the profiling guidelines provide guidance.
+zib-SkinDisorder:
+ zib deviations:
+ Condition.bodySite:
+ - datatype: CodeableConcept instead of a reference
+ reason: The referenced zib AnatomicalLocation is profiled on a datatype level and not a resource. Therefore it cannot be referenced, rather its concepts and constraints are added inline. This element conforms to the zib AnatomicalLocation.
+
zib-Stoma:
zib deviations:
Condition.code:
- cardinality: 1..1 instead of 0..1
reason: The FHIR profiles are expected to implement zib cardinalities as conceptual cardinalities, but StomaType is essential to identify the Stoma. This aligns with the intention of the zib, as the StomaType concept is required for zib Stoma to make sense.
Condition.bodySite:
- - datatype: CodeableConcept
+ - datatype: CodeableConcept instead of a reference
reason: The referenced zib AnatomicalLocation is profiled on a datatype level and not a resource. Therefore it cannot be referenced, rather its concepts and constraints are added inline. This element conforms to the zib AnatomicalLocation.
zib-TextResult:
zib deviations:
DiagnosticReport.status:
- cardinality: 1..1 instead of 0..1
- reason: TextResultStatus (0..1) is mapped to mandatory .status element which should not be a problem because implementers shall have to support .status one way or another. When TextResultStatus is absent, other codes may be used than from the zib. The _unknown_ code can be used as a fallback.
+ reason: TextResultStatus (0..1) is mapped to the mandatory .status element which should not be a problem because implementers shall have to support .status one way or another. When TextResultStatus is absent, other codes may be used than from the zib. The _unknown_ code can be used as a fallback.
DiagnosticReport.code:
- cardinality: 1..1 instead of 0..1
reason: The cardinality in both zib and FHIR is 1..1, but because of conceptual cardinality 0..1 is expected. In case of absent data, the profiling guidelines provide guidance.
@@ -663,7 +675,7 @@ zib-VisualFunction.VisualAid:
reason: The referenced zib AnatomicalLocation is profiled on a datatype level and not a resource. Therefore it cannot be referenced, rather its concepts and constraints are added inline. This element conforms to the zib AnatomicalLocation.
DeviceUseStatement.timing[x]:timingPeriod.end:
- short: EndDate instead of EindDatum
- reason: Incorrect short in zib definition. This is reported in https://bits.nictiz.nl/browse/ZIB-1534.
+ reason: The zib concept name "EindDatum" has not been translated into English.
zib-VisualFunction.VisualAid.Product:
ignored issues:
@@ -696,7 +708,7 @@ issues should occur: false
"*":
ignored issues:
Consent.scope*:
- - message: Unknown Code http://terminology.hl7.org/CodeSystem/consentscope#adr in http://terminology.hl7.org/CodeSystem/consentscope
+ - message: Unknown Code 'adr' in the system 'http://terminology.hl7.org/CodeSystem/consentscope'
reason: This concerns an error in the FHIR terminology server. The adr code has been removed for R5 and the terminology server was updated for it too soon. They will fix it according to zulip chat https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Consent.2Escope.3A.20diff.20in.20codes.20shown.20on.20FHIR.20vs.20Tx.20server.
- message: None of the codings provided are in the value set 'Consent Scope Codes' (http://hl7.org/fhir/ValueSet/consent-scope), and a coding should come from this value set unless it has no suitable code
reason: See above.
@@ -710,8 +722,11 @@ nl-core-*:
- message: None of the codings provided are in the value set 'VerrichtingTypeCodelijsten'
reason: The current version of the Validator incorrectly raises an error on combined ValueSets.
"*.telecom[*].system.extension[*].value.ofType(CodeableConcept).coding[*]":
- - message: Display Name for http://terminology.hl7.org/CodeSystem/v3-AddressUse#MC should be one of 'mobile contact)' instead of 'Mobile Phone' for 'http://terminology.hl7.org/CodeSystem/v3-AddressUse#MC'
+ - message: Wrong Display Name 'Mobile Phone' for http://terminology.hl7.org/CodeSystem/v3-AddressUse#MC
reason: This core display value is redefined by the ValueSet, but this isn't properly recognized by the Validator
+ "*.contentType":
+ - message: The value provided ('application/octet-stream') is not in the value set 'MimeType'
+ reason: The Validator is unable to check mime types in absence of a terminology server.
Condition.code:
- message: None of the codings provided are in the value set 'ProbleemNaamCodelijst'
reason: This ValueSet contains two SNOMED refsets. The terminology servers are unable to determine if a code is part of this refset.
@@ -725,18 +740,47 @@ nl-core-AllergyIntolerance*:
- message: None of the codings provided are in the value set 'SpecifiekeStofCodelijsten'
reason: The terminology servers cannot handle the refset specified in the ValueSet.
+nl-core-BodyHeight-*:
+ ignored issues:
+ Observation.value.ofType(Quantity).code:
+ - message: The value provided ('cm') is not in the value set 'Body Length Units'
+ reason: In absence of a terminology server, the Validator cannot check if 'cm' is a valid UCUM unit and raises an error.
nl-core-DOSScore-01:
ignored issues:
Observation.code.coding[0]:
- message: 'Local Error: Resolved system http://snomed.info/sct, but the definition is not complete. Server Error: Unable to find code 160591000146109 in http://snomed.info/sct'
reason: This is a Dutch SNOMED extension which is not present yet on the international terminology server.
-nl-core-HearingFunction.HearingAid-*:
+nl-core-*Function.*Aid-*:
ignored issues:
DeviceUseStatement:
- - message: 'DeviceUseStatement.reasonReference:zibMedicalDeviceReference: max allowed = 0, but found 1'
+ - message: 'DeviceUseStatement.reasonReference:functionalOrMentalStatus: max allowed = 0, but found 1'
reason: The Validator cannot actually inspect the referenced resources, and falsely assumes the reference is a reference to the offending profile.
+nl-core-HearingFunction.HearingAid-*:
+ ignored issues:
+ DeviceUseStatement.reasonReference[*]:
+ - message: 'Profile http://nictiz.nl/fhir/StructureDefinition/nl-core-HearingFunction.HearingAid, Element matches more than one slice'
+ reason: The Validator cannot actually inspect the referenced resources, and falsely assumes the reference is a reference to the offending profile.
+
+nl-core-VisualFunction.VisualAid-*:
+ ignored issues:
+ DeviceUseStatement.reasonReference[*]:
+ - message: 'Profile http://nictiz.nl/fhir/StructureDefinition/nl-core-VisualFunction.VisualAid, Element matches more than one slice'
+ reason: The Validator cannot actually inspect the referenced resources, and falsely assumes the reference is a reference to the offending profile.
+
+nl-core-PainScore-01:
+ ignored issues:
+ Observation.method:
+ - message: None of the codings provided are in the value set 'PijnMeetmethodeCodelijst'
+ reason: The terminology servers used don't know this code system and wrongly conclude that this is an invalid code.
+
+nl-core-Patient-01:
+ ignored issues:
+ Patient.communication[0].language:
+ - message: None of the codings provided are in the value set 'CommunicatieTaalCodelijst'
+ reason: The terminology servers used don't know this code system and wrongly conclude that this is an invalid code.
+
nl-core-PharmaceuticalProduct-01:
ignored issues:
Medication.code:
@@ -762,18 +806,6 @@ nl-core-Vaccination-event-03:
- message: 'Local Error: Resolved system http://snomed.info/sct, but the definition is not complete. Server Error: Unable to find code 159731000146104 in http://snomed.info/sct'
reason: This is a Dutch SNOMED extension which is not present yet on the international terminology server.
-nl-core-VisualFunction.VisualAid-*:
- ignored issues:
- DeviceUseStatement:
- - message: 'DeviceUseStatement.reasonReference:zibMedicalDeviceReference: max allowed = 0, but found 1'
- reason: The Validator cannot actually inspect the referenced resources, and falsely assumes the reference is a reference to the offending profile.
-
-zib-*Function.*Aid:
- zib deviations:
- DeviceUseStatement.reasonReference:zibMedicalDeviceReference:
- - short: zib MedicalDevice reference
- reason: The profiles zib-HearingFunction.HearingAid and zib-VisualFunction.VisualAid are derived from zib-MedicalDevice, where this slice is defined, but this slice is disabled in these derived profiles. However, the mapping still ends up in the snapshot, resulting in a warning here.
-
zib-*Function.*Aid.Product:
ignored issues:
Device.type:
diff --git a/qa.yaml b/qa.yaml
index 1f9628239..3c67879e4 100644
--- a/qa.yaml
+++ b/qa.yaml
@@ -14,6 +14,7 @@ patterns:
- resources/nl-core/*.xml
conceptmaps: resources/**/conceptmap-*.xml
terminology: resources/**/terminology/*.xml
+ SearchParameters: SearchParameters/*.xml
examples: examples/*.xml
steps:
@@ -44,6 +45,10 @@ steps:
validate other terminology:
description: Validate the other terminology resources
patterns: terminology
+ validate SearchParameters:
+ description: Validate SearchParameters
+ patterns: SearchParameters
+ profile: "http://nictiz.nl/fhir/StructureDefinition/ProfilingGuidelinesR4-SearchParameters"
validate examples:
description: Validate examples using the generic FHIR validation rules
patterns: examples
@@ -64,4 +69,4 @@ steps:
script: check-id.sh
check nl-core overrides:
patterns: nl-core profiles
- script: nl-core-overrides.sh
\ No newline at end of file
+ script: nl-core-overrides.sh
diff --git a/release-notes.md b/release-notes.md
index 379d240ea..7d95173b6 100644
--- a/release-notes.md
+++ b/release-notes.md
@@ -17,7 +17,6 @@ This document contains release notes per zib, indicating differences with their
## zib-AbilityToGroom
* No specific changes have been made to this profile other than the generic changes for the Observation resource.
-
## zib-AbilityToUseToilet
* No specific changes have been made to this profile other than the generic changes for the Observation resource.
@@ -26,19 +25,19 @@ This document contains release notes per zib, indicating differences with their
* Removed mapping to BRP.
* Added guidance on adding a value to `Address.line` to duplicate the relevant information in case the extensions are not supported.
* Renamed `Address.line` extensions to their functional counterparts.
-* Added a comment to `line.extension:houseNumberLetter-houseNumberAddition` on the possibility of a leading space not being parsed.
-* Added a constraint to `line.extension:houseNumberIndication` to restrict it to the values 'by' or 'to'.
+* Added a comment to `.line.extension:houseNumberLetter-houseNumberAddition` on the possibility of a leading space not being parsed.
+* Added a constraint to `.line.extension:houseNumberIndication` to restrict it to the values 'by' or 'to'.
* Mapped AddressType to `extension:addressType` and added ConceptMaps to map AddressType to `.use` and `.type` to adhere to international use. However, `extension:official` was removed. AddressType code 'HP' is now mapped to `.use` 'home' and `.type` 'both'. This was done because of two reasons:
* The notion to mark an address as 'official' seems to have its origin in the BRP, but is absent in the zib model.
- * The addition of `extension:official` seemed based on the rationale: "if implementers do not support the custom `extension:addressType`, you should be able to determine the AddressType by looking at `.use`, `.type` and custom `extension:official`". However, in this use case extension:official would probably also be not supported. By mapping 'HP' to .type 'both', all AddressType codes can be mapped to a combination of .type and .use.
+ * The addition of `extension:official` seemed based on the rationale: "if implementers do not support the custom `extension:addressType`, you should be able to determine the AddressType by looking at `.use`, `.type` and custom `extension:official`". However, in this use case `extension:official` would probably also not be supported. By mapping 'HP' to `.type` 'both', all AddressType codes can be mapped to a combination of `.type` and `.use`.
## zib-AlcoholUse
-* The code on `Observation.component:amount.code` has changed to 897148007
+* The code on `Observation.component:amount.code` has changed to 897148007.
## zib-Alert
* Renamed `extension:ConcernReference` to `extension:concern` to match its functional counterpart.
-* Added EndDateTime and Comment concepts
-* Added constraints in the profile on the choice that the zib provides between Concern and AlertName. Add guidance on which code to add to Flag.code if a reference to Concern is added.
+* Added EndDateTime and Comment concepts.
+* Added constraints in the profile on the choice that the zib provides between Concern and AlertName. Added guidance on which code to add to `Flag.code` if a reference to Concern is added.
## zib-AdvanceDirective
* Moved TypeOfLivingWill from `Consent.category` to `Consent.provision.code`, renamed it to LivingWillType in accordance with the zib and made the element 0..1 rather than 1..1 to adhere to the conceptual cardinalities of the zib.
@@ -50,10 +49,10 @@ This document contains release notes per zib, indicating differences with their
* Added guidance for mandatory elements `Consent.status`,`Consent.scope` and `Consent.policy` or `Consent.policyRule`.
# zib-AllergyIntolerance
-* Applied 'combined ValueSets' to `code` and `reaction.substance` instead of slicing per ValueSet.
-* The code-specification extensions have been removed from `clinicalStatus` and `reaction.severity` because the zib concepts can be fully mapped to FHIR.
-* Because AlleryStatus maps to both `clinicalStatus` and `verificationStatus`, but `verificationStatus` now has cardinality 0..1 compared to 1..1 in STU3, guidance on how to interpret the mapping has been added to the root, but has been simplified.
-* Changed cardinality of `note` from 0..* to 0..1 to align with the zib.
+* Applied 'combined ValueSets' to `.code` and `.reaction.substance` instead of slicing per ValueSet.
+* The code-specification extensions have been removed from `.clinicalStatus` and `.reaction.severity` because the zib concepts can be fully mapped to FHIR.
+* Because AlleryStatus maps to both `.clinicalStatus` and `.verificationStatus`, but `.verificationStatus` now has cardinality 0..1 compared to 1..1 in STU3, guidance on how to interpret the mapping has been added to the root, but has been simplified.
+* Changed cardinality of `.note` from 0..* to 0..1 to align with the zib.
## zib-AnatomicalLocation
* New partial zib. The anatomical location in FHIR is usually mapped on `.bodySite` (CodeableConcept with example binding). This zib has therefore been mapped onto a data type profile that can be used for `.bodySite`.
@@ -61,6 +60,9 @@ This document contains release notes per zib, indicating differences with their
## zib-ApgarScore
* ApgarScore is now divided into 3 profiles with their own time unit. Each profile also has its own terminology codes that correspond to the minutes.
+## zib-BarthelADLIndex
+* There was no profile in the STU3 version and therefore no diff.
+
## zib-BowelFunction
* The mapping of the Stoma concept has been moved from extension to profile level.
* MedicalDevice extension has been removed because the reference is reversed in FHIR. The MedicalDevice profile refers to this profile.
@@ -68,17 +70,32 @@ This document contains release notes per zib, indicating differences with their
## zib-CareTeam
* CareTeam is a newly added zib in the 2020 release. It has no previous profile and therefore no diff.
+## zib-ChecklistPainBehavior
+* The data type of `Observation.value[x]` (zib concept TotalScore) has been changed from Quantity to Integer, and minimum and maximum allowed values of 0 and 10 respectively are applied.
+* The system value on the `Observation.component.code` slices has changed from 'urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.0' to 'urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.0.1'.
+* The data type of the `Observation.component.value[x]` slices has changed from Quantity to Integer.
+* The code on `Observation.component:face.code` has changed from '12.17.3' to '12017003'.
+* The code on `Observation.component:mouth.code` has changed from '12.17.4' to '12017004'.
+* The code on `Observation.component:grimace.code` has changed from '12.17.5' to '12017005'.
+* The code on `Observation.component:lookingSad.code` has changed from '12.17.6' to '12017006'.
+* The code on `Observation.component:eyes.code` has changed from '12.17.7' to '12017007'.
+* The code on `Observation.component:panic.code` has changed from '12.17.8' to '12017008'.
+* The code on `Observation.component:moaning.code` has changed from '12.17.9' to '12017009'.
+* The code on `Observation.component:cry.code` has changed from '12.17.10' to '12017010'.
+* The code on `Observation.component:soundsOfRestlessness.code` has changed from '12.17.11' to '12017011'.
+* The code on `Observation.component:tears.code` has changed from '12.17.12' to '12017012'.
+
## zib-ContactInformation
-* zib ContactInformation is mapped onto two profiles: one for the concept TelephoneNumbers and one for the concept E-mailAddresses. Both are added to the hosting profile.
-* Removed mapping guidance on the root comment of zib-ContactInformation-E-mailAddresses, as this is now straightforward.
+* The zib ContactInformation is mapped onto two profiles: one for the concept TelephoneNumbers and one for the concept EmailAddresses. Both are added to the hosting profile.
+* Removed mapping guidance on the root comment of zib-ContactInformation-EmailAddresses, as this is now straightforward.
* Simplified mapping guidance on the root comment of zib-ContactInformation-TelephoneNumbers, as this is now straightforward.
-* `ContactPoint.system` has a fixed value for zib-ContactInformation-E-mailAddresses and a restricted ValueSet for zib-ContactInformation-TelephoneNumbers to implement only the relevant zib parts.
+* `ContactPoint.system` has a fixed value for zib-ContactInformation-EmailAddresses and a restricted ValueSet for zib-ContactInformation-TelephoneNumbers to implement only the relevant zib parts.
* `ContactPoint.use` has a restricted ValueSet in both profiles to implement only the relevant zib parts.
* The extension zib-ContactInformation-TelecomType, which replaced the generic code-specification extensions from release 2.x of the zib2017 package onwards, has been deprecated again in favor of code-specication, as the mapping is now much more straightforward.
* The element TelephoneNumbers/Comment was introduced. This is represented using the ext-Comment extension in the profile for TelephoneNumbers.
## zib-ComfortScale
-* The datatype of `Observation.value[x]` (zib concept TotalScore) element has been changed from Quantity to Integer, and minimum and maximum allowed values of 0 and 35 respectively are applied.
+* The data type of `Observation.value[x]` (zib concept TotalScore) has been changed from Quantity to Integer, and minimum and maximum allowed values of 0 and 35 respectively are applied.
* The code on `Observation.component:alertness.code` has changed from 12.12.3 to 12012003.
* The code on `Observation.component:calmnessAgitation.code` has changed from 12.12.4 to 12012004.
* The code on `Observation.component:respiratoryResponse.code` has changed from 12.12.5 to 12012005.
@@ -92,21 +109,26 @@ This document contains release notes per zib, indicating differences with their
* Removed the role extension (http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson-role) because `RelatedPerson.relationship` has changed from 0..1 to 0..*. The zib concept role is now mapped to a slice on relationship.
* Updated to new zib-NameInformation, zib-AddressInformation and zib-ContactInformation profiles.
+## zib-DevelopmentChild
+* The binding strength of all ValueSets has changed from 'extensible' to 'required'.
+* The data type for AgeFirstMenstruation has been changed from dateTime to Quantity, and the UCUM unit for 'year' (a) has been added.
+* The code on `Observation.component:developmentCognition.code` has been changed from 364644000 to 311465003.
+
## zib-DrugUse
-* The drugUseCode is mapped to `Observation.code` and based on a pattern
-* The code on `Observation.component:drugOrMedicationType.code` has changed to 105590001
-* The code on `Observation.component:amount.code` has changed to 363908000
+* The drugUseCode is mapped to `Observation.code` and is based on a pattern.
+* The code on `Observation.component:drugOrMedicationType.code` has changed to 105590001.
+* The code on `Observation.component:amount.code` has changed to 363908000.
## zib-DOSScore
* DOSScore is a newly added zib in the 2020 release. It has no previous profile and therefore no diff.
## zib-Encounter
* ContactWith is mapped on a slice of `Encounter.participant`.
-* `Encounter.participant.type` now honours the maximum cardinality of HealthProfessionalRole.
-* `Encounter.period.start` changed to cardinality 0 .. 1 due to the zibs conceptual cardinalities concept.
+* `Encounter.participant.type` now honors the maximum cardinality of HealthProfessionalRole.
+* `Encounter.period.start` changed to cardinality 0..1 due to the zibs conceptual cardinalities concept.
* The mapping of concepts Problem, Procedure and DeviatingResult is moved to `Encounter.reasonReference`.
* The mapping of Location is moved to `Encounter.location.location`.
-* Reference to other profiles not accounted for by the zib have been removed.
+* References to other profiles not accounted for by the zib have been removed.
## zib-Education
* There is no previous profile for Education in STU3 and therefore no diff.
@@ -116,6 +138,9 @@ This document contains release notes per zib, indicating differences with their
* The extension EpisodOfCare-Title has been replaced by ext-EpisodeOfCare.EpisodeOfCareName because this zib concept is functionally equivalent.
* The extensions EpisodeOfCare-DateFirstEncounter and EpisodeOfCare-DateLastEncounter from the previous profile are not inherited because no functional backing exists.
+## zib-FeedingPatternInfant
+* No specific changes have been made to this profile other than the generic changes for the Observation resource.
+
## zib-FLACCpainScale
* The semantic codes on the `Observation.component.code` elements have changed from LOINC to codes from the ScoreObservaties code system (urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.0.1).
* The system value on `Observation.code` has changed from http://loinc.org to http://snomed.info/sct and the code value has changed from 38213-5 to 108291000146105.
@@ -137,15 +162,15 @@ This document contains release notes per zib, indicating differences with their
## zib-HealthcareProvider
* `Organization.identifier` is now sliced based on a pattern.
-* `Organization.type[DepartmentSpecialty]` and `Organization.type[OrganizationType]` from 0..* to 0..1.
-* For `Organization.type` the slicing discriminator is changed from fixed system values to valueset binding.
+* Changed cardinality of `Organization.type[DepartmentSpecialty]` and `Organization.type[OrganizationType]` from 0..* to 0..1.
+* For `Organization.type` the slicing discriminator is changed from fixed system values to a ValueSet binding.
* Removed comments on `Organization.alias` because it has no basis in the zib.
-* Added comments on the root to point out to the usage of Location resource and the `Organization.partOf`.
+* Added comments on the root to point out the usage of the Location resource and the `Organization.partOf`.
* Major change: use of Location resource.
## zib-HealthProfessional
* `Practitioner.identifier` slices changed cardinality from 0..1 to 0..*.
-* Added HealthProfessionalIdentificationNumber mapping on `PracititionerRole.identifier`.
+* Added HealthProfessionalIdentificationNumber mapping on `PractitionerRole.identifier`.
* Added new mapping of Gender in Practitioner.
* Added textual guidance on the root to clarify the use of Practitioner and PractitionerRole.
* Added textual guidance on the root of the concept of HealthProfessionalRole.
@@ -154,7 +179,7 @@ This document contains release notes per zib, indicating differences with their
## zib-HearingFunction
* Changed fixed slice on `.code.coding` to a pattern on `.code`.
-* Relaxed cardinality of `value[x]` to 0..1 of the conceptual cardinalities of the zib.
+* Relaxed cardinality of `.value[x]` to 0..1 of the conceptual cardinalities of the zib.
## zib-HelpFromOthers
* The mappings on `CarePlan.identifier`, `CarePlan.subject`, `CarePlan.author` and `CarePlan.careTeam` have been removed.
@@ -172,14 +197,17 @@ This document contains release notes per zib, indicating differences with their
## zib-LegalSituation
* New zib in 2020. However, in the zib2017 package the zib-patient-legalstatus extension exists, which corresponds to the LegalStatus concept of the zib FreedomRestrictingMeasures (withdrawn in the 2020 release). This new zib profile expands on that LegalStatus concept.
+## zib-LifeStance
+* This zib was previously represented as an extension in the Patient profile, but this has been changed to a profile on Observation in order to prevent custom extensions.
+
## zib-LivingSituation
* Added two new concepts and modelled them on `Observation.component:homeAdaption` and `Observation.component:livingCondition`.
-* Concept 'HouseType' has been moved to its own valueCodeableConcept slice.
+* Concept 'HouseType' has been moved to its own `.valueCodeableConcept` slice.
* The comment element has been moved to `Observation.note.text`.
## zib-MedicalDevice
* Indication no longer requires a custom extension because the concept can be mapped to a native FHIR element, namely `.reasonReference`.
-* Provided more documenation on how to exchange ProductID in FHIR.
+* Provided more documentation on how to exchange ProductID in FHIR.
* Removed references on `.source` because those are not accounted for by the zib.
* Provided documentation on how to populate mandatory `.status` element.
@@ -190,26 +218,29 @@ This document contains release notes per zib, indicating differences with their
* The comment element is mapped on `Observation.note.text` instead of `Observation.comment`.
## zib-MUSTScore
-* The datatype of `Observation.value[x]` (zib concept TotalScore) element has been changed from Quantity to Integer, and minimum and maximum allowed values of 0 and 6 respectively are applied.
+* The data type of `Observation.value[x]` (zib concept TotalScore) has been changed from Quantity to Integer, and minimum and maximum allowed values of 0 and 6 respectively are applied.
* The code on `Observation.component:bmiScore.code` has changed to 4005003 and the system value to urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.0.1.
* The code on `Observation.component:weightLossScore.code` has changed to 4005004 and the system value to urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.0.1.
* The code on `Observation.component:illnessScore.code` has changed to 4005005 and the system value to urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.0.1.
+## zib-IllnessPerception
+* The concept PatientIllnessInsight with ID NL-CM:18.5.3 has been moved to `Observation.value[x]:valueString`
+
## zib-NameInformation
-* The way this partial zib has been modelled on the HumanName datatype has been overhauled to properly accommodate the way first names are handled. In the STU3 version, official first names, initials of this first name, and the given name (nickname, roepnaam) were all added to a `.given` element in the same HumanName instance, with a annotation of the type using an extension. This turned out to be the wrong approach, as all `.given` names are to be concatenated to the complete list of first names. So instead, there are now different instances of HumanName used to communicate the official names and the given name, indicated by `.use` -- resulting in two profiles. Communicating initials is now only done for names where the full name is not known (this deviates from the zib model).
+* The way this partial zib has been modelled on the HumanName data type has been overhauled to properly accommodate the way first names are handled. In the STU3 version, official first names, initials of this first name, and the given name (nickname, roepnaam) were all added to a `.given` element in the same HumanName instance, with an annotation of the type using an extension. This turned out to be the wrong approach, as all `.given` names are to be concatenated to the complete list of first names. So instead, there are now different instances of HumanName used to communicate the official names and the given name, indicated by `.use` -- resulting in two profiles. Communicating initials is now only done for names where the full name is not known (this deviates from the zib model).
* `.use` has been made mandatory (instead of discouraged).
-* Moved information and mappings from the extension level to the `value[x]` level.
+* Moved information and mappings from the extension level to the `.value[x]` level.
* `.family.extension`'s now have the zib concept names as slice names instead of the extension names.
* The `.given.extension` slice name has been changed to indicate that it is only about full name or initial.
-* Added mappings for the newly added zib concept 'titels' on `prefix` and `suffix`. Added documentation/implementation guidance on `prefix` and the root.
+* Added mappings for the newly added zib concept 'titels' on `.prefix` and `.suffix`. Added documentation/implementation guidance on `.prefix` and the root.
* Removed copied FHIR definitions and comments as these originated from DSTU2 and are given in the base data type. Moreover, this increases the focus on our added comments.
* Removed explanation of splitting up family names, as this is already given by the zib.
-* Aliases has been aligned with the zib.
+* Aliases have been aligned with the zib.
* Removed BRP mappings.
* Added the notion on the root that populating `HumanName.text` is encouraged.
## zib-NursingIntervention
-* The resource to represent this zib has been changed from Procedure to CarePlan. This aligns better with the meaning of the zib: a statement of a plan (which may or not may have been completed) rather than the record of a procedure that has been carried out. The profile for the current version is created from scratch.
+* The resource to represent this zib has been changed from Procedure to CarePlan. This aligns better with the meaning of the zib: a statement of a plan (which may or may not have been completed) rather than the record of a procedure that has been carried out. The profile for the current version is created from scratch.
* Because there's a better match with CarePlan, the five custom extensions are removed. One custom extension is added to mark a `CarePlan.contributor` as the zib Requester, and another one to define the materials used.
* Note: although the zib has changed quite dramatically since release 2017, the previous version of the profile was based on a pre-adopt of zib pre-release 2018, which is the same as release 2020.
@@ -219,38 +250,74 @@ This document contains release notes per zib, indicating differences with their
* New concept Indication mapped on the extension `NutritionOrder.extension:indication`.
* The comment extension has been replaced by a mapping to `NutritionOrder.note.text`.
+## zib-PainScore
+* Removed mapping on `Observation.bodySite` because the AnatomicalLocation concept has been removed from the zib.
+* Removed laterality extension because the Laterality concept has been removed from the zib.
+* Cardinality of `Observation.method` has changed from 1..1 to 0..1.
+* The data type of `Observation.value[x]` (zib concept PainScoreValue) has been changed from Quantity to Integer.
+
## zib-ParticipationInSociety
* No specific changes have been made to this profile other than the generic changes for the Observation resource
## zib-Patient
-* Includes Nationality, MaritalStatus, LanguageProficiency, LifeStance.
+* Includes Nationality, MaritalStatus, LanguageProficiency.
* Cardinality of `Patient.extension:nationality` left at 0..* due to the nature of the nationality core extension (which allows for a period to be placed next to the nationality and thus allows for different nationalities over time).
* Cardinality of `Patient.name` left at 0..* to allow including several name elements with a different `name.use` each.
* Cardinality of `Patient.telecom` left at 0..* to allow including several contact elements, because the zib ContactInformation includes a container that FHIR does not.
-* Added a comment to `deceased[x]`: When exporting the data, if `deceasedDateTime` (DateOfDeath) is present and has a value, DeathIndicator may be set to 'true', since DeathIndicator and DateOfDeath cannot both be represented at the same time.
+* Added a comment to `deceased[x]`: When exporting the data, if `.deceasedDateTime` (DateOfDeath) is present and has a value, DeathIndicator may be set to 'true', since DeathIndicator and DateOfDeath cannot both be represented at the same time.
## zib-Payer
* The STU3 version of the profile mapped part of the InsuranceCompany concept in the nl-core-organization profile, while these types of organizations do not necessarily have anything in common with HealthcareProviders, and it also did not allow for the situation where PayerPerson is an organization. To fix this, two separate profiles have been created for the situations where the Payer is a PayerPerson or an InsuranceCompany. These profiles could not be combined because slicing on .type with a maximum cardinality of 1 is not allowed.
* Both InsuranceCompany and 'PayerPerson as Organization' have been mapped in the profile Payer-Organization.
+## zib-Pregnancy
+* The value of `Condition.code` has changed from 118185001 to 364320009.
+
+## zib-Pregnancy.DateLastMenstruation
+* The zib-Pregnancy extension has moved from `Observation.extension` to `Observation.focus`.
+
+## zib-Pregnancy.EstimatedDateOfDelivery
+* The profile name has changed from zib-Pregnancy-TermDate to zib-Pregnancy.EstimatedDateOfDelivery.
+* The value of `Condition.code` has changed from 11778-8 (LOINC) to 161714006 (SNOMED CT).
+* The system of `Condition.code` has changed from http://loinc.org to http://snomed.info/sct.
+* The zib-Pregnancy extension has moved from `Observation.extension` to `Observation.focus`.
+
+## zib-Pregnancy.Gravidity
+* The value of `Condition.code` has changed from 11996-6 (LOINC) to 161732006 (SNOMED CT).
+* The system of `Condition.code` has changed from http://loinc.org to http://snomed.info/sct.
+* The data type on `Observation.value` has changed from Quantity to integer.
+* The zib-Pregnancy extension has moved from `Observation.extension` to `Observation.focus`.
+
+## zib-Pregnancy.Parity
+* The value of `Condition.code` has changed from 11977-6 (LOINC) to 364325004 (SNOMED CT).
+* The system of `Condition.code` has changed from http://loinc.org to http://snomed.info/sct.
+* The data type on `Observation.value` has changed from Quantity to integer.
+* The zib-Pregnancy extension has moved from `Observation.extension` to `Observation.focus`.
+
+## zib-Pregnancy.PregnancyDuration
+* The zib-Pregnancy extension has moved from `Observation.extension` to `Observation.focus`.
+
## zib-Problem
* ProblemType has been added on a slice of `Condition.category` allowing the category element to be used for other purposes too.
* FurtherSpecificationProblemName has been added with an extension on `Condition.code`.
* `Condition.bodySite` is now based on the zib AnatomicalLocation profile.
* ProblemStartDate and ProblemEndDate are placed on a DateTime type slice of `Condition.onset[x]` and `Condition.abatement[x]` allowing the option to use other types.
-* `Condition.note` now honours the max cardinality of zib Comment.
+* `Condition.note` now honors the max cardinality of zib Comment.
* `Condition.verificationStatus` contains a mandatory `.coding` element to capture the zib terminology because of the required binding on the CodeableConcept level and the zib and FHIR ValueSet do not completely map.
## Procedure
* Renamed profiles from zib-Procedure and zib-ProcedureRequest to zib-Procedure-event and zib-Procedure-request conform profiling guidelines.
-* ProcedureStartDate and ProcedureEndDate have been mapped to `Procedure.performed[x]` instead of `Procedure.performedPeriod` to account for the use of `Procedure.performedDateTime` when the zib Procedure concerns a instantaneous procedure.
-* Aligned cardinality of ProcedureMethod by setting the 'procedure-method' to 0..* instead of 0..0.
-* The ProcedureAnatomicalLocation is mapped on `Procedure.bodySite` and the cadinality has been set to 0..1 instead of 0..*.
+* ProcedureStartDate and ProcedureEndDate have been mapped to `Procedure.performed[x]` instead of `Procedure.performedPeriod` to account for the use of `Procedure.performedDateTime` when the zib Procedure concerns an instantaneous procedure.
+* Changed cardinality of the ProcedureMethod concept to 0..* instead of 0..1.
+* The ProcedureAnatomicalLocation is mapped on `Procedure.bodySite` and the cardinality has been set to 0..1 instead of 0..*.
* The resource ProcedureRequest has been renamed to ServiceRequest and now includes a mapping for all the possible concepts of zib Procedure. Compared to STU3 a mapping has been added for ProcedureMethod, ProcedureAnatomicalLocation, MedicalDevice, ProcedureStartDate and ProcedureEndDate.
* `Procedure.location` and `ServiceRequest.locationReference` are used to reference the zib HealthcareProvider instead of `Procedure.performer` and `ProcedureRequest.performer` to indicate where the Procedure takes place.
* The `Procedure.performer` only references the zib HealthProfessional represented in a PractitionerRole resource. Other references not dictated by the zib are removed.
* `ServiceRequest.performer` contains a reference to the zib CareTeam because the FHIR definition deviates from the zib Performer concept when multiple references are provided. This is described in the element's comment.
+## zib-PulseRate
+* The binding strength of the PulseRegularityCodelist has been changed from 'extensible' to 'required'.
+
## zib-Range
* There is no profile for this partial zib because the relevant parts can be modelled directly in the profiles where this zib is used.
@@ -258,21 +325,31 @@ This document contains release notes per zib, indicating differences with their
* Refraction is a newly added zib in the 2020 release. It has no previous profile and therefore no diff.
## zib-SOAPReport
-This is a newly added zib but had profiles that preceded the zib, namely gp-EncounterReport and gp-JournalEntry.
+* This is a newly added zib but had profiles that preceded the zib, namely gp-EncounterReport and gp-JournalEntry.
* Removed constraints not accounted for by the zib.
* Placed SOAPLine on a slice of `Composition.section` with a max cardinality of 4 conform the zib.
* Removed min cardinality of `Composition.section.text`.
* Removed min cardinality of `Observation.valueString` and moved mapping to a string type slice.
-* Removed fixed value of `Observation.status`
+* Removed fixed value of `Observation.status`.
* In the SOAPLineCode extension the fixed value on `.valueCodeableConcept.coding.system` has been removed because it is now covered by a required binding.
* Moved mapping of SOAPLineCode from `Observation.component`s to a custom extension because of lacking terminology codes to provide definiton ot the component.
+## zib-SkinDisorder
+* Renamed `extension:dueTo` to `extension:cause` to match its functional counterpart.
+* Changed fixed slice on `.category.coding` to a pattern on `.category`.
+* `Condition.bodySite` is now based on the zib AnatomicalLocation profile.
+* `Condition.note` now honours the max cardinality of zib Comment.
+
## zib-Stoma
* The resource to represent this zib has been changed from Observation to Condition. This aligns better with the meaning of the zib, as a stoma requires long term management.
* The general code of a Stoma has been added as a pattern to `Condition.category` allowing the category element to be used for other purposes too.
* `Condition.bodySite` is now based on the zib AnatomicalLocation profile.
* `Condition.note` now honours the max cardinality of zib Comment.
+## zib-StrongKidsScore
+* The data type of Observation.value[x] (zib concept TotalScore) element has been changed from Quantity to Integer, and minimum and maximum allowed values of 0 and 5 respectively are applied.
+* The system value of the Observation.component.code elements is changed to urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.0.1.
+
## zib-TimeInterval
* In the previous release, the concepts of this partial zib were mapped directly in the profiles where they are used. In this release the usage of this partial zib has been expanded and profiles have been created to aid the usage in profiles in the various situations that might occur.
@@ -282,8 +359,8 @@ This is a newly added zib but had profiles that preceded the zib, namely gp-Enco
# zib-TobaccoUse
* StartDate and EndDate are placed on a type slice of `Observation.effective[x]` adhering to the open world modelling principle.
* TobaccoUseStatus is placed on a type slice of `Observation.value[x]` adhering to the open world modelling principle.
-* The comment element is moved to `Observation.note.text` instead of `Observation.comment`
-* The datatype for PackYears has been changed from Quantity to integer to align with the functional definition and the Quantity datatype does not bring additional benefits to justify not aligning with the zib.
+* The comment element is moved to `Observation.note.text` instead of `Observation.comment`.
+* The data type for PackYears has been changed from Quantity to integer to align with the functional definition and the Quantity data type does not bring additional benefits to justify not aligning with the zib.
## zib-TreatmentDirective2
* This is a new zib loosely based on the previous zib TreatmentDirective. Below the most relevant changes compared to the previous zib and the STU3 profile are described.
@@ -296,16 +373,16 @@ This is a newly added zib but had profiles that preceded the zib, namely gp-Enco
* Removed references that are not defined by the zib (e.g. `Consent.organization` and `Consent.actor`).
## zib-Vaccination
-* Renamed profiles names: zib-Vaccination to zib-Vaccination-event and zib-VaccinationRecommendation to zib-Vaccination-request conform new profiling guidelines.
+* Renamed profile names: zib-Vaccination to zib-Vaccination-event and zib-VaccinationRecommendation to zib-Vaccination-request conform new profiling guidelines.
* Removed references not accounted for by the zib (e.g. `Immunization.location`, `Immunization.manufacturer` and `ImmunizationRecommendation.recommendation.supportingImmunization`).
* Aligned cardinality of `Immunization.note` with the zib by making it 0..1.
-* Moved VaccinationDate on a type slice on `Immunization.occurrence[x]:occurrenceDateTime`. This element has been renamed from `date` to `occurence[x]` in R4.
+* Moved VaccinationDate on a type slice on `Immunization.occurrence[x]:occurrenceDateTime`. This element has been renamed from `date` to `occurrence[x]` in R4.
* Moved Administrator to a slice on `Immunization.performer` with a mandatory fixed pattern in `Immunization.performer.function`.
-* Added a pattern on `Immunization.doseQuantity` to mandate the use of mL by ucum because the definition of Dose states to use milliliters.
+* Added a pattern on `Immunization.doseQuantity` to mandate the use of mL by UCUM because the definition of Dose states to use milliliters.
* Removed orderStatus extension because PlannedCareActivityForTransfer zib does not exist anymore.
-* Aligned cardinalities of ImmunizationRecommendation with the zib by constraining them and documentend this on the root element.
+* Aligned cardinalities of ImmunizationRecommendation with the zib by constraining them and documented this on the root element.
* Removed mapping of DesiredDateForRevaccination because it has been removed by the zib as well. The DesiredDateForRevaccination concept has been replaced by mapping to VaccinationDate which is placed on `ImmunizationRecommendation.recommendation.dateCriterion.value`. The mapping to PlannedCareActivityForTransfer start and end dates have been removed from this element.
## zib-VisualFunction
* Changed fixed slice on `.code.coding` to a pattern on `.code`.
-* Relaxed cardinality of `value[x]` to 0..1 of the conceptual cardinalities of the zib.
+* Relaxed cardinality of `value[x]` to 0..1 of the conceptual cardinalities of the zib.
\ No newline at end of file
diff --git a/resources/nl-core/ext-AdditionalCategory.xml b/resources/nl-core/ext-AdditionalCategory.xml
new file mode 100644
index 000000000..ad25fe4c9
--- /dev/null
+++ b/resources/nl-core/ext-AdditionalCategory.xml
@@ -0,0 +1,43 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+
diff --git a/resources/zib/terminology/codesystem-G_Standaard_Contra_Indicaties__Tabel_40_-2.16.840.1.113883.2.4.4.1.902.40.xml b/resources/zib/terminology/codesystem-G_Standaard_Contra_Indicaties__Tabel_40_-2.16.840.1.113883.2.4.4.1.902.40.xml
index 023251aae..3b83c3ffa 100644
--- a/resources/zib/terminology/codesystem-G_Standaard_Contra_Indicaties__Tabel_40_-2.16.840.1.113883.2.4.4.1.902.40.xml
+++ b/resources/zib/terminology/codesystem-G_Standaard_Contra_Indicaties__Tabel_40_-2.16.840.1.113883.2.4.4.1.902.40.xml
@@ -3,7 +3,7 @@
-
+
@@ -12,7 +12,7 @@
-
+
diff --git a/resources/zib/terminology/codesystem-G_standaard_Ongewenste_medicatiegroepen-2.16.840.1.113883.2.4.4.1.902.122.xml b/resources/zib/terminology/codesystem-G_standaard_Ongewenste_medicatiegroepen-2.16.840.1.113883.2.4.4.1.902.122.xml
index ccefd368a..7e019d33c 100644
--- a/resources/zib/terminology/codesystem-G_standaard_Ongewenste_medicatiegroepen-2.16.840.1.113883.2.4.4.1.902.122.xml
+++ b/resources/zib/terminology/codesystem-G_standaard_Ongewenste_medicatiegroepen-2.16.840.1.113883.2.4.4.1.902.122.xml
@@ -3,7 +3,7 @@
-
+
@@ -12,7 +12,7 @@
-
+
diff --git a/resources/zib/terminology/codesystem-G_standaard_Stofnaamcode_i_c_m__toedieningsweg__SSK_-2.16.840.1.113883.2.4.4.1.725.xml b/resources/zib/terminology/codesystem-G_standaard_Stofnaamcode_i_c_m__toedieningsweg__SSK_-2.16.840.1.113883.2.4.4.1.725.xml
index c2b8fc6ac..581aea255 100644
--- a/resources/zib/terminology/codesystem-G_standaard_Stofnaamcode_i_c_m__toedieningsweg__SSK_-2.16.840.1.113883.2.4.4.1.725.xml
+++ b/resources/zib/terminology/codesystem-G_standaard_Stofnaamcode_i_c_m__toedieningsweg__SSK_-2.16.840.1.113883.2.4.4.1.725.xml
@@ -3,7 +3,7 @@
-
+
@@ -12,7 +12,7 @@
-
+
diff --git a/resources/zib/terminology/codesystem-NHGTabel20CodeOpleiding-2.16.840.1.113883.2.4.4.30.20.xml b/resources/zib/terminology/codesystem-NHGTabel20CodeOpleiding-2.16.840.1.113883.2.4.4.30.20.xml
index 107d75a9e..6a29094c9 100644
--- a/resources/zib/terminology/codesystem-NHGTabel20CodeOpleiding-2.16.840.1.113883.2.4.4.30.20.xml
+++ b/resources/zib/terminology/codesystem-NHGTabel20CodeOpleiding-2.16.840.1.113883.2.4.4.30.20.xml
@@ -3,7 +3,7 @@
-
+
@@ -12,7 +12,7 @@
-
+
diff --git a/resources/zib/terminology/codesystem-SK_Gewichtsverlies-2.16.840.1.113883.2.4.3.11.60.40.4.17.1.xml b/resources/zib/terminology/codesystem-SK_Gewichtsverlies-2.16.840.1.113883.2.4.3.11.60.40.4.17.1.xml
new file mode 100644
index 000000000..9ffee6e2a
--- /dev/null
+++ b/resources/zib/terminology/codesystem-SK_Gewichtsverlies-2.16.840.1.113883.2.4.3.11.60.40.4.17.1.xml
@@ -0,0 +1,84 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+