From aedce51abafae3d5a12785877af5124e62353a8a Mon Sep 17 00:00:00 2001 From: Amy Koo Date: Thu, 26 Sep 2024 13:35:01 +0200 Subject: [PATCH] updated known issues --- known-issues.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/known-issues.yml b/known-issues.yml index 12f2cad..1058114 100644 --- a/known-issues.yml +++ b/known-issues.yml @@ -10,7 +10,7 @@ zib-HealthcareProvider: - datatype: Address instead of a reference reason: An address in FHIR is represented using the Address datatype, not as a separate resource. - cardinality: 0..1 instead of 0..* - reason: The cardinality mismatch between the zib (0..*) and FHIR (0..1) is explained by the restriction of FHIR to limit the Location.address to a physical address while the zib allows for other types of addresses (e.g. a postal address). Other types of addresses than a physical address are given in Organization.address which is referenced by Location.managingOrganization. More documentation can be found at https://github.com/Nictiz/Nictiz-R4-zib2020/issues/38. + reason: The cardinality mismatch between the zib (0..*) and FHIR (0..1) is explained by the restriction of FHIR to limit the Location.address to a physical address while the zib allows for other types of addresses (e.g. a postal address). Other types of addresses than a physical address are given in Organization.address which is referenced by Location.managingOrganization. Location.telecom: - cardinality: 0..* instead of 0..1 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.