-
Notifications
You must be signed in to change notification settings - Fork 142
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
Comments
Ok, let's discuss it on Tuesday. |
SORMAS Performance Indicators for Epi Week 11 12.pptx Attached is the analyst power point presentation for the performance indicator |
Suggestion for the timeliness comparison:
Proportion of actual cases:
|
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 KPI: |
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?
Are there enough tracers?
Is tracing and isolation successful?
|
@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. |
Good to hear. Putting those crucial indicators on the dashboard might help push tracing efforts into the right direction. |
@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
The text was updated successfully, but these errors were encountered: