Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

Converting single case reporting to default aggregate case reporting format #45

Closed
aninek opened this issue Sep 26, 2017 · 2 comments
Closed
Assignees
Projects
Milestone

Comments

@aninek
Copy link
Collaborator

aninek commented Sep 26, 2017

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 Sex age
3 1 1
4 1 2
5 2 1
6 2 2

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.

Event Male<5 Male>5 Female<5 Female>5
3 1 0 0 0
4 0 1 0 0
5 0 0 1 0
6 0 0 0 1

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.

@aninek aninek created this issue from a note in Reporting (Backlog) Sep 26, 2017
@aninek aninek changed the title Converting health risk reporting to database Converting health risk reporting to default reporting format Sep 27, 2017
@aninek 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 aninek mentioned this issue Sep 28, 2017
@karolikl karolikl removed this from Backlog in Reporting Oct 1, 2017
@karolikl karolikl self-assigned this Oct 1, 2017
@karolikl
Copy link
Collaborator

@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?

At the moment, this is what is listed:
image

@aninek
Copy link
Collaborator Author

aninek commented Nov 15, 2017

@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.

@karolikl karolikl added this to the MVP milestone Dec 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Reporting
  
Awaiting triage
Development

No branches or pull requests

2 participants