Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SORMAS Performance Indicator Matrix #904

Open
ghost opened this issue Dec 4, 2018 · 9 comments
Open

SORMAS Performance Indicator Matrix #904

ghost opened this issue Dec 4, 2018 · 9 comments

Comments

@ghost
Copy link

ghost commented Dec 4, 2018

@MartinWahnschaffeSymeda @bernardsilenou @MateStrysewskeSym I was not at the last sprint meeting. Was this discussed during the last meeting? If not, we need to discuss this and see what we can generate as reports from the SORMAS dashboard. Thanks

image

@ghost ghost self-assigned this Dec 4, 2018
@ghost ghost added this to the Sprint 52 - 1.10.0 milestone Dec 4, 2018
@MartinWahnschaffe
Copy link
Contributor

Ok, let's discuss it on Tuesday.

@foyiri
Copy link

foyiri commented Apr 30, 2019

SORMAS Performance Indicators for Epi Week 11 12.pptx

Attached is the analyst power point presentation for the performance indicator

@MartinWahnschaffe
Copy link
Contributor

MartinWahnschaffe commented Jul 1, 2019

Suggestion for the timeliness comparison:

  • use onset date as reference (ignore cases that don't have it)
  • rows are regions/districts
  • colums are: admission date, report date, creation date, district date, region date, national date

Proportion of actual cases:

  • we could allow users to add an "external report" to report case counts aggregated in other systems and allow the user to compare this

SORMAS Performance Indicators for Epi Week 17 & 18.pptx

@MartinWahnschaffe MartinWahnschaffe added the needs-refinement Refinement or further specification required label Aug 7, 2019
@bernardsilenou
Copy link

We should add proportion of sormas field notification (PSFN) among the list of performance indicators in the table above. We should categorize the performance indicators based on user, region,
More or on PSFN can be found in the attached document
SORMASPerformanceIndicatorGZI_bsi_190816_gek.pdf

@bernardsilenou
Copy link

bernardsilenou commented Jun 9, 2020

More KPI:
Time from date of symptom onset to date of notification
Time from date of lab sample taken to date of lab result entered in system
Time from date of notification to date of first visit of all contacts of the respective case
Time from date of lab sample taken to date of lab result entered in system
Time from date of symptom onset to first date of presenting to health facility
Time from date of hospitalization (stationary care) to date of discharge from stationary care
Percent of cases admitted to stationary care at health facility (this means only those who are kept at health facility for treatment at least one night)
percentage of cases with emergency visit only but not hospitalized

@JohWl
Copy link

JohWl commented Jul 25, 2020

I am no user/professional tracer, so forgive me if these are already implemented, I can just derive from the 1.42 online demo:

Are people taking it seriously?

  • Time from date of symptom onset to test

Are there enough tracers?

  • Time from positive test result to quarantine all contacts
  • Number of contacts per case

Is tracing and isolation successful?

  • Percent of cases with known source
  • Percent of cases testing positive within/before quarantine

@bernardsilenou
Copy link

@JohWl most of the indicators have been implemented. For those that have not been implemented, users can easily calculated them by exporting the data from sormas database because sormas documents all the date variables needed.

@JohWl
Copy link

JohWl commented Jul 29, 2020

Good to hear. Putting those crucial indicators on the dashboard might help push tracing efforts into the right direction.

@bernardsilenou
Copy link

@MartinWahnschaffe MartinWahnschaffe removed the needs-refinement Refinement or further specification required label Oct 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants