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 140 forks source link

COVID-19 as an aggregate disease for dashboard real-time update #1686

Open Chinedar opened 4 years ago

Chinedar commented 4 years ago

-->

Situation Description

Currently, we have to linelist or enter cases for covid19 when we have all or some of the details of cases. The peculiarity of the Nigerian system affecting real time reporting especially from non-reporting states yet to be deployed necessitates this need.

Feature Description

An aggregate entry point on the system where we can enter the aggregate case count (and positive result count) as they are confirmed in-country to update the dashboard real-time, while we then source for the case full details from these points that are not SORMAS deployed.

Possible Alternatives

Additional Information

MateStrysewske commented 4 years ago

@Chinedar Can you explain how this should work, especially concerning these two questions:

1) Would the aggregate counts simply be added to the case counts on the already existing dashboard or would you need a separate dashboard for it? 2) If more details for a case that was already collected as an aggregate earlier become available, how would we ensure to not have this as a quasi-duplicate in the system? Right now, this would mean that the case would appear twice on the dashboard, once as an aggregate number and once as an actual case.

Chinedar commented 4 years ago

So what would work to avoid the quasi-duplicate is to have a custom separate dashboard for it. This custom covid dashboard would be populated via the aggregate entry point and a validation mechanism could be added to ensure the case based update/count meets up with what is reported via the aggregate entry. If this is not realistic, then we'll keep up the push to ensure cases are reported real-time or near real-time at the least. Thanks.

On Mon, 30 Mar 2020, 06:33 Maté Strysewske, notifications@github.com wrote:

@Chinedar https://github.com/Chinedar Can you explain how this should work, especially concerning these two questions:

  1. Would the aggregate counts simply be added to the case counts on the already existing dashboard or would you need a separate dashboard for it?
  2. If more details for a case that was already collected as an aggregate earlier become available, how would we ensure to not have this as a quasi-duplicate in the system? Right now, this would mean that the case would appear twice on the dashboard, once as an aggregate number and once as an actual case.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hzi-braunschweig/SORMAS-Project/issues/1686#issuecomment-605791132, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIPKP5FMCN67LVOGSKAAMU3RKAVI5ANCNFSM4LV4YDHQ .

bernardsilenou commented 4 years ago

I think we should focus on what can be done to have 'detailed accurate case based data' even if there is some delay in the process. We can have the real time aggregate counts but it does not give us any credit because any system can to that also. @Chinedar Courage to you and involve the Boses on this please.