eanders
commented
7 months ago @JulesABrown & @MollyMcEvilley we are also seeing this, though flagged as flags:
- 528-1283
- 528-1606
There is a discrepancy between the HHType field and the HHAdultAge field of your LSAExit file. In the HHType field, you reported that the households in this row were neither AO (adult-only) nor AC (adult-child) households. Yet in row 1283.0 you reported in the HHAdultAge field that they were AO or AC households. This is not an issue that can be resolved by looking at your LSAExit file, since client level information like Client ID is not stored there. You may need vendor assistance to resolve this error.
We haven't dug in nearly as deeply as @nataliesus , but on the surface, that appears to be the same issue, and actually the flag number is probably just 528, since the bit after the dash appears to simply match the count.
Hi @JulesABrown , @MollyMcEvilley ,
I would like to confirm with you if Flag 528 is a vendor flag.
Upload URL: https://hdxsandbox.abtsites.com/dataset/652/flag-report
Our Data:
tlsa_Enrollment: there is a household with 2 clients: -- HoH is a child; Exit Date falls within Cohor = -1 -- other HH member is an adult; Exit Date falls within Cohor = -2
tlsa_HHID (ExitCohort = -1):
Step 3.6.3: tlsa_HHID.Exit1HHType = 3 (CO), because only HoH is selected (adult hh member is not selected because they were exited on Cohor = -2):
Step 7.2.1: tlsa_Exit.HHType = hhid.Exit1HHType = 3
Step 7.9.3: tlsa_Enrollment is not limited by cohorts, so client who exited within Cohor = -2 is selected to age calculation and cause MaxAge = 44. As a result, MaxAge = 44 and MinAge = 17 that gives us ex.HHAdultAge = 25 (AC).
As a result, with valid data, we do have a scenario when ex.HHAdultAge = 25 (AC) and ex.HHType = 3 (CO).
Could you please advise what we should do next with vendor flag 528?
Thank you! Natalie