Add Case-Classification for Germany [3]

[markusmann-vg]

Situation Description

The case classification which we use for SORMAS does not fit the needs of German authorities.

Feature Description

There are new Case Classifications, that will be manually set by the user. The logic and automatic setup will be added later, when the requirements are clear. For now we need to add the following case classifications for the German system:

„nicht klassifiziert“ [0. nicht klassif.]	0	NOT_CLASSIFIED
„klinisch diagnostizierte Erkrankung“ [A. klin-diagnost.]	A	SUSPECT
„klinisch-epidemiologisch bestätigte Erkrankung“ [B. klin-epidem. bestät.]	B	PROBABLE
„klinisch-labordiagnostisch bestätigte Erkrankung“ [C. klin-labor. bestät.]	C	CONFIRMED
„labordiagnostisch nachgewiesene Infektion, klinisches Bild nicht erfüllt“ [D. labor. ohne klin. Bild]	D	CONFIRMED_NO_SYMPTOMS
„labordiagnostisch nachgewiesene Infektion, klinisches Bild unbekannt“ [E. labor. und unbek. klin. Bild.]	E	CONFIRMED_UNKNOWN_SYMPTOMS
„kein Fall“ [X. kein Fall]	X	NO_CASE

The migration of the old cases is described in the attached excel. There is a logic for the migration which has to be considered, wether an old case will be classified into 0 or A

caseclassification.xlsx

Pages that have to be considered for that change:

Cases

OUT OF SCOPE: #################### Dashboard - no 0,A,B - (C;D;E as confirmed in one number) Transmission Chain - no 0,A,B - (C;D;E as confirmed in one number) ####################

[MartinWahnschaffe]

Unclear:

1. How should the new clinical, epidemiological and lab confirmation fields be filled/migrated
2. How should the three fields and the case classification interact? We need to make sure that there is no inconsistent data in the system that would later need to be migrated
3. What are the possible values of "klinisch besätigt"?

[markusmann-vg]

Migration rule: We migrate all cases that were not classified to 0 => There will be no old unclassified cases which will be migrated to A

Customized setup of enums have to be used in Edit Forms, Dashboards & Statistics

[markusmann-vg]

We should add a error message for selected combinations, which are not valid

[bernardsilenou]

This is the corrected mockup

[markusmann-vg]

CaseClassification.2230.xlsx

[markusmann-vg]

IMPORTANT: ONLY for Germany and just for COVID 19

@markusmann-vg For Germany and for all diseases. Although we only use SORMAS for COVID now, but might change in the near future.

[bernardsilenou]

Will confirm from survnet and respond latter today pls

[bernardsilenou]

The categories are: yes, no, unknown, and NA when not selected. See picture please. The captions have been changed slightly, thus we need to translate accordingly.

[MateStrysewske]

@bernardsilenou Thanks!

[bernardsilenou]

@MateStrysewskeSym Danke

Just a note: For the German form , we display NA and Unknown just as we do for symptoms

[BarnaBartha]

@markusmann-vg @MateStrysewskeSym Can you please confirm/clarify the following:

• the "Kategorie der Falldefinition" = "Detaillierte Fallklassifizierung" = "Case classification" and that it becomes a simple field instead of an option group? In @bernardsilenou comment I see it as a field but in the moqups (https://app.moqups.com/3NUENEwuOE/edit/page/afc481082) it is still an optionGroup.
• the "Klinisches bild erfullt" is a dropdown for the YES NO UNKNOWN enum
• do we have to consider the CaseClassification.2230.xlsx for the migration or only for validation on edit later? If it has to be considered for the migration what happens to a confirmed case form the db that does not have any of the symptoms corresponding to C true ?
• "We should add a error message for selected combinations, which are not valid" - which are those combinations ? (I am guessing if clinicallyConfirmed epidemiologicallyConfirmed labConfirmed are all YEs than the case classification cannot be X ("kein-fall" / no case) - as that makes no sense) - we need more specifics here

[markusmann-vg]

a.) confirmed b.) confirmed c.) just for the validation and edit later part d.) You can use the validation checks, if the check shows, that a check should not be able to make, we throw an error message and reset the checkmark

[BarnaBartha]

English translations

„nicht klassifiziert“ [0. not classified]	0	NOT_CLASSIFIED
„klinisch diagnostizierte Erkrankung“ [A. clin-diagnost.]	A	SUSPECT
„klinisch-epidemiologisch bestätigte Erkrankung“ [B. clin-epidem. confirmed]	B	PROBABLE
„klinisch-labordiagnostisch bestätigte Erkrankung“ [C. clin-labor. confirmed]	C	CONFIRMED
„labordiagnostisch nachgewiesene Infektion, klinisches Bild nicht erfüllt“ [D. labor. w/o clin. picture]	D	CONFIRMED_NO_SYMPTOMS
„labordiagnostisch nachgewiesene Infektion, klinisches Bild unbekannt“ [E. labor. and unknown clin. picture]	E	CONFIRMED_UNKNOWN_SYMPTOMS
„kein Fall“ [X. no case]	X	NO_CASE

@markusmann-vg @bernardsilenou As discussed with @MateStrysewskeSym this should not be in the scope of this ticket, as it requires another abstraction on top of the i18 property files or moving of all fields that have to be translated to the database and thus allow indefinite customisation. This is a bigger effort and should be planned & estimated separately. For now I will just update the german translations - means all systems no matter the locale will see the new translations for case classification if they use the german language.

[BarnaBartha]

• Migration script for German servers to migrate 0 -> A:

  UPDATE cases
  SET caseclassification = 'SUSPECT'
  FROM cases c
       LEFT JOIN symptoms s ON c.symptoms_id = s.id
  WHERE c.disease = 'CORONAVIRUS' and c.caseclassification = 'NOT_CLASSIFIED'
  and (s.pneumoniaclinicalorradiologic = 'YES' or
     s.difficultybreathing = 'YES' or
     s.sorethroat = 'YES' or
     s.cough = 'YES' or
     s.runnynose = 'YES' or
     s.respiratorydiseaseventilation = 'YES' or
     s.acuterespiratorydistresssyndrome = 'YES');

  Note: as discussed this does not include the migration C -> D / E, but if needed such script can be provided.

• Migration script needed when a German server becomes a non-german server For example locale is changed from de -> en.

  UPDATE cases
  SET caseclassification = 'CONFIRMED'
  FROM cases c
  WHERE c.caseclassification = 'CONFIRMED_NO_SYMPTOMS' or c.caseclassification = 'CONFIRMED_UNKNOWN_SYMPTOMS'

  Note that this should not be the case for productive systems but it is a common scenario for development systems.