Disease Configuration Admin Interface

Disease Configuration Admin Interface

Introduction

The disease configuration user interface allows SORMAS administrator users to configure different parameters for diseases

How to configure diseases

  1. Log as a user with administrative rights

  2. On the left main menu, click Configuration

configuration menu
configuration main menu
  1. Select Disease Configuration sub-menu

disease-configuration-sub-menu.png
  1. The disease configuration page will open as shown below:

diseas-config-page.png
  1. Click Edit icon on a disease row to bring up the disease configuration editing popup window

diseas-config-popup.png
  1. The configuration parameters are as follows

S/N

Field

Description

S/N

Field

Description

1

Active

Defines whether the disease is used in SORMAS at all. E.g. it's possible to use SORMAS only for a single disease by disabling all other diseases.

2

Primary

Primary diseases can be selected when creating a case or contact. Secondary diseases are currently only used for pathogen tests. Only relevant for case-based diseases.

3

Case surveillance

Whether this disease can be used for data related to case surveillance, e.g. cases, contacts, or pathogen tests.

4

Aggregate reporting enabled

Whether this disease can be used for aggregate reporting.

5

Follow-up enabled

Whether follow-up is enabled for this disease, i.e. the follow-up status can be managed and visits can be created

6

Follow-up duration

Defines a follow-up duration in days to automatically calculate the follow-up until date for contacts.

7

Case follow-up duration

Defines a follow-up duration in days to automatically calculate the follow-up until date for cases

8

Event participant follow-up duration

Defines a follow-up duration in days to automatically calculate the follow-up until date for event participants. Please note that event participant follow-up is not yet implemented.

9

Extended classification

Use dedicated fields for clinical, epidermilogical and laboratory confirmation to classify a case

10

Extended classification multi

Only relevant when extendedClassification is used. When this is set to false another field called "basis for confirmation" is used to define which of the three confirmation fields is relevant for the classification.

11

Automatic sample assignment threshold

When a new external message is sent to the system and automatically processed, and a case is found for which the person is unambiguously identified as the same person as the one in the message, if the sample collection date of this case falls into this threshold (defined in days), the sample and pathogen test from the external message are automatically associated with that case instead of a new one being created.

12

Age groups

Only relevant for primary disease that are enabled for case surveillance. Define age groups to be used for aggregated reporting

  1. After saving the configuration. The system reloads the disease configuration. There is no need to restart the server is most cases.