search

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
291 stars 141 forks source link

Extension and refinement of event based surveillance #2092

Open bernardsilenou opened 4 years ago

bernardsilenou commented 4 years ago

Situation Description

  1. In the current system, we can notify event and follow them prospectively and latter convert event persons to cases (prospectively) 2; We can also create a case and under the epidemiological data section of the case, notify the event that the case person may have been exposed (retrospectively).

Issue: The event in 1 has no link with the even in 2 in the system, even if the events are the same in real life. In addition, the event in 2 does not appear under the event tab in menu bar.

Feature Description

This is a proposed design:

  1. Events created in 2, should appear also under the list of events in 1 in menu bar, even if there is aonly one person that has been converted to a case.
  2. If a user then create another case and in the epi data sector notified the same event, the system should search for duplicate events and link the newly created event with the old one if the user validate it. This will be similar to duplicate person detection. This will permit us to be able to identify by creating cases, the cases that resulted from the same event even if we had no idea about the event in the first place. This information will be useful to identify common exposures among the cases.
  3. We should also be able to retrospectively assigned a relation ship between an existing case person or contact person to an event using the same logic we used to assigned contacts created in the line list of contact to their source case.
  4. The duplicate search of events will not be limited to the region and district of the case (or contact).
  5. Users will be able to also add more persons to event created through the case, just as the default event.
  6. Duplicate search for event can be based on: region, district, community, date of event (not exact date match but with tolerance of about 7 days max due to memory bias) and disease (optinal).
  7. We can also add a type field to event: e.g party, church, school activities, travel in same car/ avian, etc this will help to limit the search. 10.More ideas ??

Possible Alternatives

Additional Information

This might be difficult to have such a feature for mobile users. We can focus on web users for now.

JaquM-HZI commented 3 years ago

@bernardsilenou do you think with all the new grouping and hierarchy part within events this issue is solved?