Aligned constraint name with profiling guidelines

Nictiz · Sep 25, 2024 · 6965cf8 · 6965cf8
1 parent ced92f5
commit 6965cf8
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/release-notes.md b/release-notes.md
@@ -1,2 +1,2 @@
 ## AddressInformation (zib-AddressInformation)
-* `.line.extension:houseNumberIndication.value[x]` ; constraint ; Adjusted houseNumberIndication for HouseNumberIndication ; ZIB-2218
+* `.line.extension:houseNumberIndication.value[x]` ; constraint ; Adjusted zib-AddressInformation-1 for HouseNumberIndication ; ZIB-2218
diff --git a/zib/StructureDefinitions/zib-AddressInformation.xml b/zib/StructureDefinitions/zib-AddressInformation.xml
@@ -177,7 +177,7 @@
       <comment value="The mapping of zib AddressInformation on the FHIR Address datatype is the result of compatibility with HL7v3, which is the format that a lot of healthcare data in the Netherlands is stored in. As a result of this, the coded zib HouseNumberIndication concept (CD datatype) is mapped to a FHIR string datatype with a constraint added (the value can only be 'by' or 'to' or 'OTH')." />
       <alias value="AanduidingBijNummer" />
       <constraint>
-        <key value="houseNumberIndication" />
+        <key value="zib-AddressInformation-1" />
         <severity value="error" />
         <human value="Must have value 'by' or 'to' or 'OTH'" />
         <expression value="$this in ('by' | 'to' | 'OTH')" />