NOTE: Inactive Structure Marking IS A SEPARATE SCOPING DOCUMENT

Status

Definitions

• Inactive structure: a non-valid structure that was created erroneously and should be removed from play completely (e.g., duplicate residential structure record created by accident)
  • This is effectively soft deleting the structure
  • CR comment: Correct. 
• Ineligible structure: a valid structure that is ineligible to participate in an intervention for a valid reason (e.g., a residential structure where the inhabitants are not currently residing but may return in the future) 
  • This is a form field specific to the activity

Overview

This functionality was requested by the Thai team for Focus Investigation. Fields workers should be able to mark a structure as ineligible for household registration, and therefore  subsequent tasks should be marked: task.businessStatus = Not Eligible

Requirements

1. Users should be able to mark a structure as ineligible during household registration
2. This should be an option in the household registration form similar to IRS (screenshot below)
3. Marking the structure as ineligible should turn the structure black, hide/skip subsequent questions in the form and set all tasks assigned to the structure as Not Eligible
4. Any structures that have been marked as ineligible should should be removed from the target denominator for the FI  (Number of Structures)
   1. Q: Although this structure will still have been visited and number of structures visited may be a metric 
5. Any task linked to the structures that have been marked as ineligible should be removed from the target denominator for the FI (Number of Households registered)
6. Any subsequent tasks (RACD, bednets etc) that have been marked as ineligible should be removed from the target denominator for the FI (Number of bednets to distribute)
7. A structure cannot be marked ineligible if a household has been registered, or has had any tasks associated with it that are not in an initial state (IN_PROGRESS as BusinessStatus?)
8. A structure cannot be marked as eligible if it has been marked as ineligible (this would mean that all tasks would have to be changed from Not Eligible to In Progress - is this valid?)
9. If an ineligible structure is clicked/touched a card is displayed indicating that the structure is ineligible with the date it was marked ineligible
10. LIFECYCLE: Restricted to the plan. Ineligibility will not persist across interventions (an IRS plan in the same OA will not have the structure marked as ineligible) and ineligibility will not extend to the following FI
11. Both enumerated and field-added structures may be marked as ineligible
12. Workflow to determine a structure is ineligible:
    1. The user visits the structure seen in the map view of the mobile client and determines that this structure is not eligible for the intervention.
    2. Tap the structure.
       1. If no household has been registered:
          1. New field: Select type of structure:  Agreed to remove this Vivek Agrawal & Pierre Dane
             1. Residential structure
             2. Non-residential structure
             3. Non-existent structure - mark as inactive
          2. New field: Is this structure eligible for the intervention? (These options could be expanded e.g. Ineligible - Non-residential, Ineligible - Does not exist, Ineligible - Other)
             1. Eligible structure
             2. Ineligible structure
       2. If household has been registered: 
          1. Tap the three dots in the upper right-hand corner
          2. Select 'Household ineligible for intervention'  Agreed to remove this Vivek Agrawal & Pierre Dane

Views

We anticipate the following views to be impacted on with the creation of this feature:

• Android - Add structure registration form
• Android - New options in family view to:
  • Mark as ineligible for current household (for this intervention i.e. FI)
• Android - New form in family view to move registered household to new structure
• Android - Maps - Add colour coding for ineligible (black) & inactive structures (light grey)
• Android - Maps - Add a card view for ineligible structures
• Web - Maps - Display ineligible structures in black in the web view
• Web - Maps - Ability to show/hide or filter the ineligible structures  for a given task view (nice-to-have - will be part of a larger ticket for filtering of task types and statuses) . 

Justification

Dependencies

Questions

Notes

• The ability to mark a structure as ineligible is the priority feature - the feature to mark structures as inactive can be developed in a future release and should be created as a separate scoping document (once this document has been completed
• The list of reasons for a structure being ineligible are specific to the intervention
• This will be a form field added in the data dictionary
• Q: How does the form field link to the task status? In some cases could marking a structure as ineligible mean that the task is complete/green?
• As this is for Thailand FI, the immediate use case is to be able to add fields to the household registration form
• We need to provide the ability to update the task status as the first question
• Tasks assigned to OA, location or a person
• Q: Would get into a tricky spot if moving from ineligible to eligible - might be better to create a new register family task. generate a new task for registration? 
  • Not priority right now - assume this can't be done in this iteration
• If marked a structure as ineligible can you open and see the profile? No - .... what displays/ need to know why on the card. 
• Map view only displays high-level tasks
  • Register Family - mark structure as ineligible, define post save action, if structure not residential then skip all other fields, post save action will be - if there are tasks, mark these as won't fo/eligible. If there are people registered - what to fo (e.g blood) Maybe cant mark as ineligible
  • Can you or cant you mark something as ineligible (Inactive is a mistake - should
• ef have 2 plans, IRS and Focus eligible for one plan and not other, inactive removes structure

Test Case