You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
aninek
changed the title
Converting health risk reporting to database
Converting health risk reporting to default reporting format
Sep 27, 2017
aninek
changed the title
Converting health risk reporting to default reporting format
Converting single case reporting to default aggregate case reporting format
Sep 27, 2017
@aninek, at the moment all single case reports and aggregated case reports are displayed in the same way, meaning you're not able to see the actual age (you only see over5/under5).
My worry is that you, in fact, want to see the specific age supplied in the single case reports. Could you please provide some insights into this?
@karolikl We have gone around in circles on this, but have landed on <5 and >5 being sufficient data for outbreak investigation/deciding on response. Limiting to <5 and >5 age groups also means single case reports will be less identifiable (e.g. perhaps only 1 13 year old boy living in the community, but many >5 years), which is good. So in conclusion: we only need under five or over five.
Purpose:
All text messages will be stored in #48 as "Original message". Accurate volunteer reports will follow either of the two reporting structures:
We want to map how two hash reports fit into the the four hash database.
Conversation:
Event is defined by Event UID in Event database #33
Sex is defined as Male =1, Female =2
Age is defined as <5 =1, >5=2
Database structure: Converting previous two hash text messages into four hash database.
Related background tickets:
Constraints:
Original report is always kept as its own variable.
Confirmation:
All example two hash text messages sent and recorded in 4 hash system database.
The text was updated successfully, but these errors were encountered: