I want to build a tracker in which I have to register the head of household, the number of people living in the household disaggregated by age and sex. As the number of people living in the household disaggregated by age and sex is unlikely to change over time as we follow up with the households, I am thinking of creating these disaggregations as tracked entity attributes as follows:
Profile
• Name of the head of household • Number of people living in the household • Female 10-14 • Female 14-19 • Female 20-24 • Female >25 • Male 10-14 • Male 14-19 • Male 20-24 • Male >25
Would it be right or advisable to do this? Looking forward to some advice
Hi @hernandezmachava,
Thank you for your patience and interest in getting the community involved in the discussion. I’m still a beginner and trying to learn - just finished the Tracker Use Academy Level 1! But I hope that my contribution will also be helpful.
I believe that you don’t need all those separations and all that long list. Only one attribute for Age is enough, and one attribute for Sex (Option set) because then you are able to filter these attributes as you like. Additionally, I would recommend that you make a program rule for “number of people living in the household” so that it’s not entered manually but that it is calculated by the total count of males and females in the household.
It really valuable contribution, but if we define age and sex as attributes, won’t these attributes be linked to the head of household? As seen in the image above, we want to capture the name of head of household and the number of people living in the household and in this case I think defining age and sex as attributes they won’t be linked to household members, but to the head of household.
With this scenario, will it be possible to calculate the following:
Okay but since you are using Tracker, what is going to be the TEI? The head of household? I would suggest instead making the household as the TEI and then everything is linked to the household itself.
I began to question if we could actually use only one attribute for age and one for sex unless we consider each member in the household a TEI with an attribute that says head of household yes/no.
The thing is that it seems that you are taking an aggregate approach in tracker which is why it might seem complicated so if we want to use tracker maybe we should define exactly what will be the:
Program:
Entity:
Stages/events:
Sections:
Attributes:
The program and stage/event name would be Hygiene and sanitation.. I think the stage would be repeatable as for each visit the community worker will make, he/she will collect over time information about whether the household has the following:
1. Traditional pit latrine 2. improved pit latrine 3. tip - tap 4. Copa 5. garbage dump
Here I think we can define these five items as data elements of yes/no data type.
For the entity, we can stick to head of family. The problem remains that we need to capture this information about the people who live with the head of family. I see that it is an aggregate approach, but it is a requirement. Any other ideas of how to address this situation?
• Female 10-14 • Female 14-19 • Female 20-24 • Female >25 • Male 10-14 • Male 14-19 • Male 20-24 • Male >25.
But I hope that my contribution will also be helpful.