Case classification ‐ automation

1) Case classification feature description and activation guidance

(this section does not describe the logic of the classification calculation, this is explained in section 2))

A. Automatic case classification

Cumulative requirements for activation the automatic case classification feature:

1) Disease classification

In order to be able to trigger the automatic case classification the disease selected on the case MUST have classification rules
An indication for the user that classification rules exist is the presence of the “Info” button next to the “Case classification” field in the case's main form. This button will trigger a pop-up window that shows the rules based on which the automatic classification is computed. The rules correspond for the case disease.

Currently the following diseases have case classification rules:

  - EVD (Ebola virus disease), 
  - CSM (Meningitis), 
  - LASSA (Lassa fever), 
  - YELLOW_FEVER (Yellow Fever), 
  - DENGUE (Dengue Fever), 
  - NEW_INFLUENZA (Influenza (New subtype)), 
  - MEASLES (Measles), 
  - CHOLERA (Cholera), 
  - MONKEYPOX (Mpox), 
  - PLAGUE (Plague), 
  - CONGENITAL_RUBELLA (Congenital Rubella), 
  - CORONAVIRUS (COVID-19)

2) Server configuration

Property name: “feature.automaticcaseclassification” - must be activated
Property location - “sormas.properties” file
Default value is “true”

When automatic case classification is triggered?

On case changes during save (if the case classification option is manually set then the automatic classification is not triggered anymore)
On case samples changes
On case contacts changes
On case person changes

B. Manual case classification

Availability

The button for manual case classification it is available without automaticCaseClassification feature turned on
Currently only on German servers

User right needed

In order to be able to see the “Case classification calculation” button the user must have “CASE_CLASSIFY” right

Types of manual classifications:

Single case classification

it is currently available only on German servers
the button “Calculate case classification” triggers an automatic calculation of the case classification
the user has the possibility to overrule the automatic calculation by selecting the desired classification instead and save the case

Bulk case classification

Can be applied to multiple selected cases in a single operation
The user can only manually select one “case classification” which will be applied on all selected cases. The automatic case classification cannot be trigger with the bulk approach.

C. Other aspects of the “case classification” feature

Case classification available options

Depends on country server configured the available options for the user are different as follows:
All server types have the following case classifications:
- Not yet classified, suspect, probable, confirmed, not a case.
Only German server type
- Has additional 2 classifications: confirmed No Symptoms, confirmed unknown symptoms.

2) Case classification calculation logic

Below you have the 2 separate description on how the case classification mechanism works on Luxemburg compared to other servers.

the “caseClassificationCalculationButton” is currently visible only on German servers.

Case classification description for all servers except Luxembourg

there are 2 fields where the case classification value is stored
- systemCaseClassification
- caseClassification (this value is seen in UI by the user)

On case save:

if the Automatic CaseClassification server configuration is true then
- if the value of the case classification is Not_A_Case then:
  - no changes will be saved on either systemCaseClassification or caseClassification fields
- if the value of the case classification is NOT Not_A_Case then:
  - automatic classification is executed
  - if the automatic case classification differs from existing systemCaseClassification
    - then the value is changed and also the caseClassification is changed which is seen in the UI by the user no matter what the user sets in the caseClassification field
  - if the automatic case classification returns the same value as the one already existing on the systemCaseClassificationase field then
    - the new value set by the user in the case classification field is the one that is saved
so in case other changes made on the case trigger changes in case classification it does not matter what the user sets manually on the case classification field the system will always save the automatic classification value
if the user is not satisfied with the automatic case classification value can go and change it manually but only of no other changes that would trigger changes in classification are made

Case classification description for Luxembourg users:

there are 2 fields where the case classification value is stored
- systemCaseClassification
- caseClassification (this value is seen in UI by the user)