Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zib-LaboratoryTestResult #14

Draft
wants to merge 59 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from 55 commits
Commits
Show all changes
59 commits
Select commit Hold shift + click to select a range
24a6126
Added base profile and extension
Ashwin-nictiz Sep 7, 2024
f857158
Changed the mapping identity to the 2024 version
Ashwin-nictiz Sep 7, 2024
61b5668
Run addDataToZib script
Ashwin-nictiz Sep 7, 2024
308b81d
Changed the purpoose to 2024 and run scrip adddatafromzib in nl-core …
Ashwin-nictiz Sep 7, 2024
1c43abe
Mapping of extension in 2024 and deleted the version element, added t…
Ashwin-nictiz Sep 9, 2024
156c4df
Moved the profiles to the StructureDef folder
Ashwin-nictiz Sep 9, 2024
7128f54
Added code spec extension
Ashwin-nictiz Sep 9, 2024
081cf68
Added terminology
Ashwin-nictiz Sep 10, 2024
583c0e8
Added conceptmaps and valuesets changes also known-issues.
Ashwin-nictiz Sep 10, 2024
116be3b
Removed root concept and adjust adress type to 2024
Ashwin-nictiz Sep 10, 2024
adb5006
Added release notes
Ashwin-nictiz Sep 10, 2024
1ac8fe3
Resave forge?
Ashwin-nictiz Sep 11, 2024
1014130
Commen value updated with OTH
Ashwin-nictiz Sep 11, 2024
b0c71ed
Added release note about the comment on houseNumberIndication
Ashwin-nictiz Sep 11, 2024
cce6061
Terminology update
Ashwin-nictiz Sep 12, 2024
a7dd6b5
Initial commit of new profiling for AnatomicalLocation including a du…
ArdonToonstra Sep 12, 2024
d2809e2
zib-HealthcareProvider: base profile, valuesets
AmyKoo1 Sep 17, 2024
efb4336
Feedback changes
Ashwin-nictiz Sep 19, 2024
599b5e8
Deleted version element in the concept maps and also move to the manu…
Ashwin-nictiz Sep 20, 2024
ced92f5
Updated release-notes.md to latest convention documented in ZIBFHIR20…
ArdonToonstra Sep 25, 2024
6965cf8
Aligned constraint name with profiling guidelines
ArdonToonstra Sep 25, 2024
830884b
Added known issues
AmyKoo1 Sep 25, 2024
51af961
zib ContactInformation-EmailAddresses en zib ContactInformation-Telep…
AmyKoo1 Sep 25, 2024
d6e5ebb
Merge branch 'main' into zib-ContactInformation
AmyKoo1 Sep 26, 2024
36fe60c
added valuesets, codesystem, conceptmaps and release notes
AmyKoo1 Sep 26, 2024
3f8f738
Merge branch 'main' into zib-HealthcareProvider
AmyKoo1 Sep 26, 2024
aedce51
updated known issues
AmyKoo1 Sep 26, 2024
fd24586
Merge branch 'zib-AnatomicalLocation' into zib-LaboratoryTestResult
AmyKoo1 Sep 30, 2024
9aa499b
Moved some of the implementation guidance to the purpose of the profi…
ArdonToonstra Oct 1, 2024
5669cec
textual changes, updated known-issues and release-notes
AmyKoo1 Oct 2, 2024
e1604f7
draft base profile and valuesets
AmyKoo1 Oct 7, 2024
1efa7c3
Merge branch 'zib-AddressInformation' into zib-HealthcareProvider
AmyKoo1 Oct 7, 2024
3b821fd
removed redundant elements
AmyKoo1 Oct 7, 2024
215796d
Moved binding from coding to root CodeableConcept and fixed missing b…
ArdonToonstra Oct 8, 2024
2875333
Renamed profile, added ext-EdifactReferenceNumber
AmyKoo1 Oct 8, 2024
0192b13
Merge branch 'zib-AnatomicalLocation' into zib-LaboratoryTestResult
AmyKoo1 Oct 8, 2024
90d5b36
Added release-notes
ArdonToonstra Oct 8, 2024
f52fabb
Fixed nl-core profile based on QA and improved wording in zib-Anatomi…
ArdonToonstra Oct 8, 2024
9b00b4c
Updated Id and comment
AmyKoo1 Oct 8, 2024
6ce70c2
Merge branch 'zib-AnatomicalLocation' into zib-LaboratoryTestResult
AmyKoo1 Oct 8, 2024
96a78f6
Merge branch 'zib-HealthcareProvider' into zib-LaboratoryTestResult
AmyKoo1 Oct 8, 2024
df9396a
Removed unneccesary CodeSystem, updated metadata
AmyKoo1 Oct 8, 2024
13e4b3a
add ext-CodeSpecification
AmyKoo1 Oct 8, 2024
e13a0a3
Merge branch 'zib-ContactInformation' into zib-HealthcareProvider
AmyKoo1 Oct 8, 2024
0ccd1b2
Merge branch 'zib-HealthcareProvider' into zib-LaboratoryTestResult
AmyKoo1 Oct 8, 2024
1fe5d69
Satisfy nl-core-overwrite QA
ArdonToonstra Oct 9, 2024
c6615cb
Satisfy 2.0 nl-core-overwrite QA
ArdonToonstra Oct 9, 2024
0075dc7
Merge branch 'zib-AnatomicalLocation' into zib-LaboratoryTestResult
AmyKoo1 Oct 9, 2024
326bf9b
Added terminology and known-issues.
AmyKoo1 Oct 9, 2024
50419d1
updated known issues
AmyKoo1 Oct 9, 2024
79c5178
Merge branch 'zib-HealthcareProvider' into zib-LaboratoryTestResult
AmyKoo1 Oct 9, 2024
bdd7f1c
added dependency
AmyKoo1 Oct 14, 2024
3f3a704
added release notes, mapping guidance
AmyKoo1 Oct 14, 2024
58b1c6d
removed incorrect mappings
AmyKoo1 Oct 14, 2024
d8f730d
Cardinality adjusted in profile
AmyKoo1 Oct 14, 2024
9f5dc09
updated release notes
AmyKoo1 Oct 21, 2024
649546f
updated release notes, removed incorrect mapping, added nl-core-Labor…
AmyKoo1 Oct 23, 2024
5d241d2
Added ext CopyIndicator
AmyKoo1 Oct 24, 2024
20b41c8
fix nl-core overrides
AmyKoo1 Oct 25, 2024
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 61 additions & 0 deletions known-issues.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,70 @@

issues should occur: true

zib-HealthcareProvider:
zib deviations:
Location.address:
- 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.
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.
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 ContactInformation is mapped on .telecom.

unmapped zib concepts:
- NL-CM:17.2.10: HealthcareProvider.LocationNumber
reason: This zib concept is problematic to map cleanly to FHIR and it has been deemed too uncommon in practice to warrant an extension.

zib-LaboratoryTestResult:
zib deviations:
Observation.status:
- cardinality: 1..1 instead of 0..1
reason: Although the equivalent concept is optional in the zib, this element is required in FHIR.
Observation.code:
- cardinality: 1..1 instead of 0..1
reason: This element is mapped to the concepts PanelOrBattery and TestCode at the same time. PanelOrBattery is marked as optional in the zib, but this is strictly not true; it must be absent if the zib instantiates a singular laboratory test, but is required if the zib instantiates a panel. Therefore, both mappings to this element are in fact required.
Observation.value[x]:
- datatype: Quantity instead of ANY
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 these concepts only have meaning when they apply to a Quantity. See https://bits.nictiz.nl/browse/ZIB-1703.

zib-LaboratoryTestResult.Specimen:
zib deviations:
Specimen.identifier:
- cardinality: 0..* instead of 0..1
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.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.
Specimen.container.extension:specimenNumberExtension.value[x]:
- 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.
---
# The following issues are not "real" deviations stemming from design choices, but rather problems that pop up due to
# shortcomings in tooling, the used terminology server, etc.
# These might occur in one or more profiles, or in none if they have been fixed in the meantime.

issues should occur: false

zib-AddressInformation:
zib deviations:
Address.line.extension:houseNumberIndication.value[x]:
- datatype: string instead of CD
reason: 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 zib concept HouseNumberIndication with CD datatype is mapped to a FHIR string datatype with a constraint added (the value can only be 'by' or 'to' or 'OTH').
Address.line.extension:*.value[x]:
- cardinality: 1..1 instead of 0..1
reason: The value of the extension is required, but the extension itself is optional, making the effective cardinality 0..1 as required by the zib.

zib-HealthcareProvider:
ignored issues:
Location.address:
- message: "Constraint failed: sd-pg-02: 'If mapping.map exists and the mapping is not implicit, short should exist'"
reason: The required short description is given by the datatype profile, so it is absent from the differential.
- message: "Constraint failed: sd-pg-04: 'If mapping.map exists and the mapping is not implicit, alias should exist.'"
reason: The required alias is given by the datatype profile, so it is absent from the differential.
63 changes: 63 additions & 0 deletions nl-core/StructureDefinitions/ext-EdifactReferenceNumber.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
<?xml version="1.0" encoding="utf-8"?>
<StructureDefinition xmlns="http://hl7.org/fhir">
<id value="ext-EdifactReferenceNumber" />
<text>
<status value="empty"/>
<div xmlns="http://www.w3.org/1999/xhtml">No narrative is provided for definitional resources. A human-readable rendering can be found in the implementation guide(s) where this resource is used.</div>
</text>
<url value="http://nictiz.nl/fhir/StructureDefinition/ext-EdifactReferenceNumber" />
<name value="ExtEdifactReferenceNumber" />
<title value="ext EdifactReferenceNumber" />
<status value="draft" />
<publisher value="Nictiz" />
<contact>
<name value="Nictiz" />
<telecom>
<system value="url" />
<value value="https://www.nictiz.nl" />
<use value="work" />
</telecom>
</contact>
<description value="This extension can be used to register the reference number of the Edifact message from which (a part of) this healthcare information originates." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
<fhirVersion value="4.0.1" />
<mapping>
<identity value="lu-dataset-laboratory-exchange-20210222" />
<uri value="https://decor.nictiz.nl/ad/#/lu-/datasets/dataset/2.16.840.1.113883.2.4.3.11.60.25.1.2/2021-02-22T00:00:00" />
<name value="ART-DECOR Dataset Lab Exchange 20210222T00:00:00" />
</mapping>
<kind value="complex-type" />
<abstract value="false" />
<context>
<type value="element" />
<expression value="Observation" />
</context>
<type value="Extension" />
<baseDefinition value="http://hl7.org/fhir/StructureDefinition/Extension" />
<derivation value="constraint" />
<differential>
<element id="Extension">
<path value="Extension" />
<max value="1" />
</element>
<element id="Extension.url">
<path value="Extension.url" />
<fixedUri value="http://nictiz.nl/fhir/StructureDefinition/ext-EdifactReferenceNumber" />
</element>
<element id="Extension.value[x]">
<path value="Extension.value[x]" />
<short value="EdifactReferenceNumber" />
<definition value="A reference number of the Edifact message from which (a part of) this healthcare information originates." />
<comment value="Edifact MEDLAB 1.0 has the intended reference number in segment IDE 'Identificatie materiaal/aanvraag' field 2 Identificatienummer" />
<alias value="EdifactReferentienummer" />
<type>
<code value="string" />
</type>
<mapping>
<identity value="lu-dataset-laboratory-exchange-20210222" />
<map value="lu-concept-v2-4409" />
<comment value="EdifactReferenceNumber" />
</mapping>
</element>
</differential>
</StructureDefinition>
36 changes: 36 additions & 0 deletions nl-core/StructureDefinitions/nl-core-AddressInformation.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
<?xml version="1.0" encoding="UTF-8"?>
<StructureDefinition xmlns="http://hl7.org/fhir">
<id value="nl-core-AddressInformation"/>
<text>
<status value="empty"/>
<div xmlns="http://www.w3.org/1999/xhtml">No narrative is provided for definitional resources. A human-readable rendering can be found in the implementation guide(s) where this resource is used.</div>
</text>
<url value="http://nictiz.nl/fhir/StructureDefinition/nl-core-AddressInformation"/>
<name value="NlcoreAddressInformation"/>
<title value="nl core AddressInformation"/>
<status value="draft"/>
<publisher value="Nictiz"/>
<contact>
<name value="Nictiz"/>
<telecom>
<system value="url"/>
<value value="https://www.nictiz.nl"/>
<use value="work"/>
</telecom>
</contact>
<description value="Address information includes data where a person resides (temporarily, permanently) or where a building is located."/>
<purpose value="A derived profile from [zib-AddressInformation](http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation) to provide a version better suited for implementation purposes. This profile augments the base profile with elements found in the various use cases that have adopted the zib."/>
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise."/>
<fhirVersion value="4.0.1"/>
<kind value="complex-type"/>
<abstract value="false"/>
<type value="Address"/>
<baseDefinition value="http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation"/>
<derivation value="constraint"/>
<differential>
<element id="Address">
<path value="Address"/>
<alias value="nl-core-AddressInformation"/>
</element>
</differential>
</StructureDefinition>
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
<?xml version="1.0" encoding="utf-8"?>
<StructureDefinition xmlns="http://hl7.org/fhir">
<id value="nl-core-AnatomicalLocation-BodyStructure" />
<text>
<status value="empty" /><div xmlns="http://www.w3.org/1999/xhtml">No narrative is provided for definitional resources. A human-readable rendering can be found in the implementation guide(s) where this resource is used.</div></text>
<url value="http://nictiz.nl/fhir/StructureDefinition/nl-core-AnatomicalLocation-BodyStructure" />
<name value="NlcoreAnatomicalLocationBodyStructure" />
<title value="nl core AnatomicalLocation BodyStructure" />
<status value="draft" />
<publisher value="Nictiz" />
<contact>
<name value="Nictiz" />
<telecom>
<system value="url" />
<value value="https://www.nictiz.nl" />
<use value="work" />
</telecom>
</contact>
<description value="An anatomical location specifies the location (e.g. foot) and laterality (e.g. left) of a body part." />
<purpose value="A derived profile from [zib-AnatomicalLocation-BodyStructure](http://nictiz.nl/fhir/StructureDefinition/zib-AnatomicalLocation-BodyStructure) to provide a version better suited for implementation purposes. This profile augments the base profile with elements found in the various use cases that have adopted the zib." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
<fhirVersion value="4.0.1" />
<kind value="resource" />
<abstract value="false" />
<type value="BodyStructure" />
<baseDefinition value="http://nictiz.nl/fhir/StructureDefinition/zib-AnatomicalLocation-BodyStructure" />
<derivation value="constraint" />
<differential>
<element id="BodyStructure">
<path value="BodyStructure" />
<definition value="The nl-core AnatomicalLocation is mapped to both a profile on CodeableConcept (&lt;http://nictiz.nl/fhir/StructureDefinition/nl-core-AnatomicalLocation&gt;) and this BodyStructure profile. While the CodeableConcept profile covers anatomical location, the BodyStructure resource is used to capture both the location and its laterality.&#xA;&#xA;When laterality is required, this BodyStructure profile should be used. In cases where laterality is either unnecessary or embedded within the location code, the CodeableConcept can be used within the resource.&#xD;&#xA;&#xD;&#xA;**Note:** Receiving systems must support both the BodyStructure resource and the CodeableConcept in host resources, as either mechanism may be employed. Providing systems can select the appropriate mechanism based on their data requirements." />
<alias value="nl-core-AnatomicalLocation-BodyStructure" />
</element>
</differential>
</StructureDefinition>
46 changes: 46 additions & 0 deletions nl-core/StructureDefinitions/nl-core-AnatomicalLocation.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
<?xml version="1.0" encoding="utf-8"?>
<StructureDefinition xmlns="http://hl7.org/fhir">
<id value="nl-core-AnatomicalLocation" />
<text>
<status value="empty" /><div xmlns="http://www.w3.org/1999/xhtml">No narrative is provided for definitional resources. A human-readable rendering can be found in the implementation guide(s) where this resource is used.</div></text>
<url value="http://nictiz.nl/fhir/StructureDefinition/nl-core-AnatomicalLocation" />
<name value="NlcoreAnatomicalLocation" />
<title value="nl core AnatomicalLocation" />
<status value="draft" />
<publisher value="Nictiz" />
<contact>
<name value="Nictiz" />
<telecom>
<system value="url" />
<value value="https://www.nictiz.nl" />
<use value="work" />
</telecom>
</contact>
<description value="An anatomical location specifies the location (e.g. foot) and laterality (e.g. left) of a body part." />
<purpose value="A derived profile from [zib-AnatomicalLocation](http://nictiz.nl/fhir/StructureDefinition/zib-AnatomicalLocation) to provide a version better suited for implementation purposes. This profile augments the base profile with elements found in the various use cases that have adopted the zib.&#xD;&#xA;&#xD;&#xA;Profilers can use this profile in places where zib AnatomicalLocation is instantiated. In addition to using this profile, the binding should be set to ValueSet &quot;LocatieCodelijsten&quot; (&lt;http://decor.nictiz.nl/fhir/ValueSet/2.16.840.1.113883.2.4.3.11.60.121.11.11--20200901000000&gt;) with a binding strength of _required_." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
<fhirVersion value="4.0.1" />
<kind value="complex-type" />
<abstract value="false" />
<type value="CodeableConcept" />
<baseDefinition value="http://nictiz.nl/fhir/StructureDefinition/zib-AnatomicalLocation" />
<derivation value="constraint" />
<differential>
<element id="CodeableConcept">
<path value="CodeableConcept" />
<alias value="nl-core-AnatomicalLocation" />
</element>
<element id="CodeableConcept.extension:bodyStructureReference">
<path value="CodeableConcept.extension" />
<sliceName value="bodyStructureReference" />
</element>
<element id="CodeableConcept.extension:bodyStructureReference.value[x]">
<path value="CodeableConcept.extension.value[x]" />
<type>
<code value="Reference" />
<targetProfile value="http://nictiz.nl/fhir/StructureDefinition/nl-core-AnatomicalLocation-BodyStructure" />
<targetProfile value="http://hl7.org/fhir/StructureDefinition/BodyStructure" />
</type>
</element>
</differential>
</StructureDefinition>
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
<?xml version="1.0" encoding="utf-8"?>
<StructureDefinition xmlns="http://hl7.org/fhir">
<id value="nl-core-ContactInformation-EmailAddresses" />
<text>
<status value="empty" /><div xmlns="http://www.w3.org/1999/xhtml">No narrative is provided for definitional resources. A human-readable rendering can be found in the implementation guide(s) where this resource is used.</div></text>
<url value="http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactInformation-EmailAddresses" />
<name value="NlcoreContactInformationEmailAddresses" />
<title value="nl core ContactInformation EmailAddresses" />
<status value="draft" />
<publisher value="Nictiz" />
<contact>
<name value="Nictiz" />
<telecom>
<system value="url" />
<value value="https://www.nictiz.nl" />
<use value="work" />
</telecom>
</contact>
<description value="Contact information includes a person's telephone numbers en e-mail addresses." />
<purpose value="A derived profile from [zib-ContactInformation-EmailAddresses](http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-EmailAddresses) to provide a version better suited for implementation purposes. This profile augments the base profile with elements found in the various use cases that have adopted the zib.&#xD;&#xA;&#xD;&#xA;To implement the entire zib, the complementary profile [nl-core-ContactInformation-TelephoneNumbers](http://nictiz.nl/fhir/StructureDefinition/nl-core-ContactInformation-TelephoneNumbers) should be used. Both profiles can be added in a slice with the discriminator set to `profile`/`$this`." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
<fhirVersion value="4.0.1" />
<mapping>
<identity value="zib-contactinformation-v1.3.1-2024EN" />
<uri value="https://zibs.nl/wiki/ContactInformation-v1.3.1(2024EN)" />
<name value="zib ContactInformation-v1.3.1(2024EN)" />
</mapping>
<kind value="complex-type" />
<abstract value="false" />
<type value="ContactPoint" />
<baseDefinition value="http://nictiz.nl/fhir/StructureDefinition/zib-ContactInformation-EmailAddresses" />
<derivation value="constraint" />
<differential>
<element id="ContactPoint">
<path value="ContactPoint" />
<alias value="nl-core-ContactInformation-EmailAddresses" />
</element>
</differential>
</StructureDefinition>
Loading