Open FredrikSchaefer opened 3 years ago
Statements from RKI indicate that currently the Gesundheitsamtskennung
(alias SurvNet-Code
) which is based on the Kreiskennziffer
is used instead of the Gemeindekennziffer
, but they are working on also allowing the Gemeindeschlüssel
(which hopefully is the same as the Gemeindekennziffer
). A webservice to determine the Gemeindeschlüssel
of a health department is in development right now.
To intensify the confusion: In some DEMIS-notifications from a test server, there are three health departments specified. with the according XML:
<meta>
<lastUpdated value="2021-02-11T16:45:32.654+01:00"/>
<profile value="https://demis.rki.de/fhir/StructureDefinition/NotificationBundleLaboratory"/>
<tag>
<system value="https://demis.rki.de/fhir/CodeSystem/ResponsibleDepartment"/>
<code value="1.test-oegd08"/>
</tag>
<tag>
<system value="https://demis.rki.de/fhir/CodeSystem/ResponsibleDepartmentSubmitter"/>
<code value="1.test-oegd08"/>
</tag>
<tag>
<system value="https://demis.rki.de/fhir/CodeSystem/ResponsibleDepartmentNotifier"/>
<code value="1.test-oegd03"/>
</tag>
<tag>
<system value="https://demis.rki.de/fhir/CodeSystem/ResponsibleDepartmentPrimaryAddress"/>
<code value="1.test-oegd08"/>
</tag>
</meta>
We discussed the community part: @FredrikSchaeferVitagroup sormas_gemeinden_master.xlsx
Hi,
for Berlin the Gemeindekennziffer
and Kreiskennziffer
are the same. Berlin uses Lebensweltlich orientierte Räume (LOR)
instead. These are already implemented in SurvNet and are stored in [Data].[AdditionalAttribute]
with [AttributeName] = 'PLZ-LOR'
. The corresponding XML entry in the export file looks like this:
<Group Name="AdditionalAttribute"><Field Name="AttributeName" Value="PLZ-LOR" /><Field Name="AttributeValue" Value="<AttributeValue><TextItem Name="PLZ" Label="PLZ" Sort="1" Max="20" Value="11111" /><TextItem Name="LOR" Label="LOR" Sort="2" Max="20" Value="11111111" /></AttributeValue>" /></Group>
or without replaced HTML entities:
<Group Name="AdditionalAttribute"><Field Name="AttributeName" Value="PLZ-LOR" /><Field Name="AttributeValue" Value="<AttributeValue><TextItem Name="PLZ" Label="PLZ" Sort="1" Max="20" Value="11111" /><TextItem Name="LOR" Label="LOR" Sort="2" Max="20" Value="11111111" /></AttributeValue>" /></Group>
The 8-digit LOR number can be generated from coordinates or from the address and are available here: https://www.stadtentwicklung.berlin.de/planen/basisdaten_stadtentwicklung/lor/de/download.shtml
Currently, the 2019 version is still being used because no demographic information is available for the current version (2021).
Could this be implemented in Sormas and exported to SurvNet for Transmission? I am happy to provide more details.
Greetings, Alex
Presiquisite: https://github.com/hzi-braunschweig/SORMAS-Project/issues/3254
Situation Description
A DEMIS-Notification includes information about two health departments.
Bundle.meta.tag.ResponsibleDepartment
. It shows as "Zuständiges Gesundheitsamt".Bundle.meta.tag.ResponsibleDepartmentSubmitter
. It relates to "Gesundheitsamt des Einsenders" in the HTML representation of a labMessage.Feature Description
1.test-oegd08
show up.Additional Information
This mapping has a downside, it is confusing: In SORMAS, there seems to be a region for a case, which refers to the case persons place of residence ("Wohnort"). Then, there is responsible region in SORMAS, which relates to a region that is not the case persons place of residence, but still responsible. According to the german IfSG, foremost the health department of the persons place of residence ("Wohnort") is supposed to be responsible. Thus, we map what is mostly called responsible department in DEMIS to something explicitly not called responsible region (but just region), while we map something explicitly not called responsible department (but submitting department) in DEMIS to something called responsible region in SORMAS. The same is true for district.
Open Questions
Gemeindekennziffer
or whatever equivalent is contained in a DEMIS-Notification to Districts and Regions?