Addition of indicator : Number of events identified in a backward-tracing logic

[carolinverset]

Definition of the proposed indicator :

• Usually we look for the contacts of a case in a top-down logic to isolate the persons who have been in contact with the source case: forward-tracing.
• To increase the efficiency of the device, forward-tracing is supplemented by backward-tracing, which consists in identifying the source of contamination of the case. To do this, we go back in time (- 10 days) to identify the events in which the case participated. Other people who participated in the same event are called the co-exposed people. These co-exposures were potentially exposed during the event that caused the contamination of the case. As far as possible, they will be contacted, alerted and tested.

Nature of the indicator:
Number of events identified in a backward-tracing logic

Construction of the indicator:

• The variable to differentiate between backward- and forward-tracing events is under development and will be available from version 1.62 (end of sprint: July 7).
• Consequently, this variable will not exist in the database from version 1.62 which will be deployed at best at the end of July.
• Given the strong health and political stakes, this indicator must be developed as quickly as possible even if the final variable is not yet available.
• To date, the teams use the category of the event = "screening" to indicate that it is a backward-tracing event. As soon as the final variable is available, the teams will use the "event investigation status" variable to define the nature of the investigation of an event.

It is therefore necessary to provide two stages in the construction of the indicator making it possible to count the number of "backward" events:

1. from the variable event.event_status = screening now
2. from the variable event.eventinvestigationstatus = backward upon implementation.

Return of the indicator:
(cf screenshot)

• Indicator to be positioned in the "Backward-tracing" part in a "BWD dashboard event" tab.
• The same construction as the "event dashboard" is recommended.
• The same indicators of the upper bar are to be used but limiting to the only backward-tracing events.

Additional context
@MostafaHazmoun @bernardsilenou @stephaneghozzi