What is the right way to setup a Child Case

Users
1

I am trying to setup child cases. I am not able to see the Case List properly. Besides, I have other doubts also

We have create two Modules/Menus

  1. MotherVisit as the first menu and the case type is called MotherVisit
  2. Second BabyList, the case type here is also called MotherVisit. .
  3. Right now we have one for in each menu. The first menu (MotherVisit) has the form called Mother Registration
  4. The second menu has the form called Baby Registration
  5. In the BabyRegistration form, I have selected it to be a ChildCase.
    Now my questions are
  6. Is it the right way to setup the ChildCase i.e both menus have same case type
  7. When we select a form to be childcase, we get two places for mapping case properties, one outside the Child details and one inside. What is the difference
  8. How will I get the data? I believe i will have to download both form data and then link it. What is the linking field
  9. We have started data collection. How to change the data in the new format (ChildCase)
2

I don't understand why you kept the mother and baby registration in two different menus. You could just keep them both in the same since the case type is the same. However, it will not make any difference even if it is in two different menus since the case type is the same.

I don't understand what you mean by child case. Are you referring to the case management where you have to select the case type to which you want to transfer the data, ie from one case type to another? If this is the case then you do not need to use that feature because if you use the same case type, the data will automatically be reflected in the other form menus in the devices of the data entry person.

I don't understand your 7th point

Yes the data you will get is from 2 different exports since your forms are different (this is for form type export) and then you can link it using a unique ID, most preferably caseid in SQL or whatever you guys might be using. However, if you download the case data of this case type, all of the data from the 2 forms will be in one export since the case type is the same.

Since you have started data collection, I would not recommend any major changes in case management or changing the case type. This will result in loss of data.

I think you can let it be as it is as your format seems fine.

3

Hi @hussain,

I am new to commcare, and I have read some tutorials, but I don't have experience building Apps, so I were wondering if you could help me with the use case below, Whether I would keep household and beneficiaries in separate modules, how case properties should be dealt with, etc.

I want to register Households, which have the following attributes: Household ID
GPS Coordinates, I also want to register household members as beneficiaries. So, the scenario will be as follows:
Entity: Household
Attributes:
Household ID
GPS Coordinates

Household members
-Member 1: Name, DOB, etc
-Member 2: Name, DOB, etc

Thanks in advance

4

You may keep household and other beneficiaries in separate modules if you wish to keep the case types of both different or else if you want it to be the same case type then it can be in the same module.
You can keep the same case type for household and other beneficiary registration, then you will have to send the beneficiaries to their respective case types once the registration of the beneficiary is done.
You will need to read some stuff about case management on the commcare help site.

5

@hernandezmachava

This depends on your scope or data flow.

If it's just registration, you need to draw a clear flow since :
HH - Registration
HH Add Member (New born just if blesses)

So you will need 2 case types while working on this.
Case to create and case to update parent case for child or new member to HH when certain conditions are true.

6

Hi @Kiptoos and @hussain,

We want to build an application that does monthly household visits, The application needs to register households, and each individual household member. We would like to use repeat groups to register the household members. How to correctly configure the repeat groups and child cases?

From the tutorials, I get a little bit confused.

This is the structure we are thinking to create

  • Household Module
    • Household Registration Form
    • Household Member Registration Form

Thanks

7

It is a good idea to have a household registration form and a household member registration form but it is not a good idea to use repeat groups for this and it is also not needed.

Repeat groups will give you a separate sheet while exporting and it becomes difficult to map if until and unless you carefully add unique ids to the repeat group as well. But repeat groups are unnecessary here.
You can create a single member registration form and then link that particular member with their respective household using a lookup question. There is a way to pull the data filled in the previous form into a lookup question using instance queries (you do not need to add any excel files for lookups).

I would strongly advise you against using repeat groups.