SORMAS-Foundation / SORMAS-Project

SORMAS (Surveillance, Outbreak Response Management and Analysis System) is an early warning and management system to fight the spread of infectious diseases.

https://sormas.org

GNU General Public License v3.0

293 stars 143 forks source link

Show cluster risk level on event and actions directory and add filter #3951

Closed kwa20 closed 3 years ago

kwa20 commented 3 years ago

Situation Description

3271 added a risk level to events that are clusters. However, users cannot see risk level information on the directories and will therefore have to open events individually to find out their risk level. To have a more informative overview about the clusters, adding this information as well as a filter would be quite useful (e.g. different people might want to focus on different risk levels).

Feature Description

I suggest to add the risk level on the event and actions directories inside the event status. Since the risk level is only assigned to clusters, a separate column is not necessary because it would have many empty rows.

Possible Alternatives

Additional Information

bernardsilenou commented 3 years ago

@kwa20 since this is a variable by itself, i think it would be good to have it as a new column and also add filter. Thus this would require that the variable "risk level" apply to all event statuses. @carolinverset @ftavin Is it fine by you to activate the risk level for all event statuses?

kwa20 commented 3 years ago

@bernardsilenou Would a risk level make sense for a events with a signal or screening status though?

bernardsilenou commented 3 years ago

@bernardsilenou Would a risk level make sense for a events with a signal or screening status though?

The risk level is a categorization of the probability of the disease to spread among event participant. If the event is a cluster (>= n cases), then it make sense to have a risk level. To me it also make sense to have the risk level for an event that is not a cluster, for e.g. Many people drank gluhwien from a seller and we latter realized the drink had expired and could lead to sever sickness. There is yet no case but due to the exposure (drink), we would wan to classify the event as high risk and take certain measures.

For screening it may not make sense. Since it caused not harm if it exist, then I would say we just add to all event status.

ftavin commented 3 years ago

@bernardsilenou

ok, #4047 will first activate the risk level for all event statuses. Afterwards, this issue should be done

carolinverset commented 3 years ago

@ftavin @bernardsilenou I'm agree with you. Ok for activate risk level for all event statuses

AndyBakcsy-she commented 3 years ago

Verified the ticket on the latest version of SORMAS Version: 1.55.0-SNAPSHOT on test.sormas.netzlink.com This ticket might be related to #4149