Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

NOTE: Inactive Structure Marking IS A SEPARATE SCOPING DOCUMENT



Responsible Person:
Other parties to review/input:
FYI:
Targeted release date:

fix verified date
Loading...
Refresh

Jira Status:

status
Loading...
Refresh

Status

#
Step
Status
1Responsible prepares rough business analysis/reqs doc

IN PROGRESS Pierre Dane; initial reqs added by Christina Riley

2Get CHAI review
3Get Akros Review
4Get Ona feedback
5Responsible - 1 iteration for feedback
6Ona sign off
7Ona tech spec scoping
8Ona LOE 
9Ona scheduling

Definitions

  • DT comment: Christina Riley, can you please review and validate these 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

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)
  • No structures are ever deleted from Reveal, they can only be marked as inactive

Requirements

Inactive

  1. Any structures that have been marked as inactive should be removed from the target denominator for all interventions
  2. Inactivity is not intervention-specific and applies to all interventions.
  3. Structures that are eligible to be marked as inactive include:
    1. Structures created during enumeration that do not actually exist in the field.
    2. Structures erroneously added in the field (e.g. duplicates of other structures, inaccurate locations of existing structures, other user-error additions, etc.).
  4. Workflow to determine a structure is inactive:
    1. The user navigates to the structure seen in the map view of the mobile client and determines that this structure does not exist.
    2. Tap the structure.
      1. If no household has been registered:
        1. New form (before household registration):
          1. New field - Structure registration: Select type of structure:
            1. Residential structure
            2. Non-residential structure
            3. Non-existent structure - mark as inactive
      2. If household has been registered: CR comment - this is assumed that a family has been incorrectly registered to this structure and should be moved to a correct structure
        1. Tap the three dots in the upper right-hand corner
        2. Select 'Move family registration'
        3. Search & select the relevant structure from the displayed map view or list view (note that the structure have been enumerated)
          1. Recommend having a radius of selection, i.e. can only move family registration to a structure within 100m
            1. What to do for structures outside of this radius? Is it possible to create a holding table for registered families without a structure?
          2. If no family already registered to new structure - Save
          3. If family already registered to the structure:
            1. Is this a multi-structure household?
        4. Tap the SAME structure that has been identified as inactive (now there should be no family registered)
          1. New field - Structure registration: Select type of structure:
            1. Residential structure
            2. Non-residential structure
            3. Non-existent structure - mark as inactive

Ineligible

  1. Any structures that have been marked as ineligible should be removed from the target denominator for the intervention
  2. Ineligibility is intervention-specific:
    1. Non-residential structures should not be considered for IRS
    2. Non-residential structures should not be considered for RACD
    3. Residential structures that are not sprayable
    4. PAOT during a non-FI intervention campaign (i.e. routine bednet, MBS, IRS)
  3. Both enumerated and field-added structures may be marked as ineligible
  4. Workflow to determine a structure is ineligible:
    1. The user navigates to 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:
          1. Residential structure
          2. Non-residential structure
          3. Non-existent structure - mark as inactive
        2. New field: Is this structure eligible for the intervention?
          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'

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 intervention
    • Move registered household to new structure
  • 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
  • Android - Maps - Add a card view for inactive structures
  • Web - Maps - Display ineligible structures in black in the web view with ability to toggle on/off


Justification


Dependencies


Questions


Test Case

#

Step

Pass / Fail

Comment

1




2




3




4




5




6




7




8




Additional tester comments:







  • No labels