...

...

• Ability to look-up households per list view lookup 
• Need some kind of searchable unique identifier to uniquely identify people to avoid counting them twice. (QR code)
• Need a way to link family that doesn’t have locations.
• Search needs to search floating families

Assumptions

• You will never treat a child without a caregiver to consent.
• You will never treat a child without linking them to a family entity. All workflows rely on registering a family/family head.
  
  • You cannot register a child without a family to link to themOn-ground protocols will determine and train on what defines a family entity.
• We will not be able to unlink and relink to "fix" where linkages were made incorrectly in the MVP with QR codes.

Workflow

There are two main templates that will inform these workflows. The Web UI reporting and plan template contains the details of the plan and activity as well as requirements for web based dashboards. The Data collection data dictionary defines the forms and data needed for register family, register child and drug distribution workflow, as well as two aggregate forms.

...

• Register Family (linked to location by also floating, detailed in workflow 3) - does not autogenerate
• Register Child - does not autogenerate 
• Drug Distribution - autogenerates against any eligible, registered child. We need to define eligibility criteria and generate tasks based on these criteria and NOT for all person-entities. 

  Jira Legacy
  server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-856

• Drug Allocation (team-level task not linked to location)
• Drug Return (team-level task not linked to location)

...

1. Visit home, tap on house from map view, following questions appear before kicking off family registration
   1. Confirm house is residential, someone is home to give info, and consent is given, is main house? 
   2. If no to any of above, follow skip logic and do not enter family module and family registration 

Workflow 1a, 1b, 1c - WHEN AT HOUSE: Register/Edit Family, Register/Edit Child, Distribute Drugs (all within Family Module)

1. After answering yes to all of Workflow 0
   1. Access family module, register family
   2. Register each child, including children that are not present 
      1. Treat each eligible, present, child 

Workflow 2 - Leave QR code when

...

not everyone home 

Jira Legacy
server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-475

1. In 'Add family' workflow (1), after answering 'no' to 'is anyone homeeveryone home' and 'yes' to 'is main house'
   1. User is taken to a QR scanning view. 
   2. "Scan the QR code that will be associated with this locationfor this structure and leave stickers at house"
      1. User scans QR code
      2. User leaves two QR stickers at house.
2. QR codes need to have the operational area code written on them.

Workflow 3 - FLOATING FAMILY, NOT AT HOUSE: Linking to Location and entering Family Module

Find someone

...

who belongs to unregistered household 

...

• This could happen in the village at a location

...

• that is not the household location

1. Attempt to link to existing household first by searching map and list view
   1. Searchable features: all household names
2. If have QR code: Access family module from list view through a button  "Register floating familyFamily lookup" 

   Jira Legacy
   server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-476

   1. "Does this family/child have a QR code" 
      1.  If yes, open QR code scanner to link (Details in QR linking below)
      2. If no, "Are you sure this family/child does not belong to an already registered house?"
      3. Proceed to family module (workflow 1)
3. If no QR code: Attempt to link to existing household first by searching map and list view
   1. Searchable features: all household names
      1. If find family, proceed to family module (Workflow 1)
      2. If no family found, register as new floating family without QR code

Workflow 4 - FLOATING FAMILY NOT WITHIN VILLAGE (Point-distribution?)

The program would like to conduct 'mop-up' from a central location. This means that families may show up with their QR code or with no QR code at a health facility. This requires the following features

1. Register new floating families to a location level higher than operational area level
2. Global look-up with search functionality in list view
3. Global look-up with QR code

Option 1 - Implement 1,2,3 (likely beyond MVP, significant effort)

Working at the health facility level, select hamburger menu option for that catchment.

1. Workflow looks identical to Workflow 3, except
   1. List view will show all families (floating and not) in the catchment
   2. Searches will then happen at this level
   3. There will be no map view

Option 2 - Implement 1, 2 

Working at the health facility level, select hamburger menu option for that catchment.

1. If have QR code paper
   1. Contains written operational area on QR code
      1. Switch to that OA on hamburger menu, proceed with Workflow 3
   2. Does not contain written operational area on QR code
      1. Family must be registered as a floating family.
2. If no QR code: stay at health facility level in hamburger menu with a full list view.
3. Attempt to link to existing household by searching list view (global look-up)
   1. Searchable features: all household names
      1. If find family, proceed to rest of Workflow 1
      2. If no family found, register as new floating family without QR code

Option 3 - Implement 1

Working at the health facility level, select hamburger menu option for that catchment.

1. If have QR code paper
   1. Contains written operational area on QR code
      1. Switch to that OR on hamburger menu, proceed with Workflow 3
   2. Does not contain written operational area on QR code
      1. Family must be registered as a floating family.
2. If no QR code: stay at health facility level in hamburger menu with a full list view.
   1. Family must be registered as a floating family. 

Use QR code to link family to location 

Jira Legacy
server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-828

...

We will not be able to unlink and relink to "fix" where linkages were made incorrectly in the MVP.

1. In registering floating looking up family workflow, when triggered to open QR scanner:
2. Potential results from scan
   
   1. Success
      1. QR code matches this village and is not yet linked
         1. Confirmed match, show view of household location on map
            1. "Confirm link?"
            2. If yes, make link and proceed with workflow
            3. If no, warning message "This QR code links with the house shown on the map; are you sure you do not want to link?"
               1. Do not link → back to question in form asking "Does this family have a QR code"?
      2. QR code matches this village and has already been linked
         1. "This code is already linked with this structure. Proceed?"
            1. "Yes" → enter family module
            2. "No, go back" → back to question in form asking "Does this family have a QR code"?
   2. Failure
      1. QR code does not match this village
         1. "Okay"→ back to question in form asking "Does this family have a QR code"?

Workflow 4 - Point-distribution

1. Need to be able to distribute from a health facility point distribution, using the QR code, need to do the 'no location' family...

Other forms

• Drug distribution tracking to distributor team
  • We expect this to happen once or a few times - may need to "top up"
  • This should be a form that is not linked to task model OR is an "on demand" form
    • Want to see on application indicator for #drugs received against #drugs distribution, this should sum if there are multiple submissions on the form
    • Need to keep form blank for the next round of edits
• Drug return form
  • We expect this to happen potentially multiple times
    • Should play into the same indicator

Reporting

The mobile client indicators are defined in the Data collection data dictionary

The web indicators are defined in the Web UI reporting and plan template

Mock-Ups

Views/UI

• Add list of floating family families view (likely from list view)
• QR code
  • Scanning screen (think this already exists in OpenSRP)
  • Visualize matched house screen (show on the map view, the location of the house that matches with the QR code
  • Follow-on/confirmation questions
• View to link 'floating family' with location → Icon family-look up → icon from list view?
  • to look up families with QR code
  scan creen
  • to add floating families

Justification

Notes

Questions

• How do we capture children that have no caregiver and we do not treat but we need to measure them?
• Differentiating between homeless family and no family
• *add to data dictionary, homeless question
• *UI re
• How much family member info do we need to put in
• This needs to be extremely limited
• Is it easier to resolve 2 QR codes into one or to find a person’s record again.
• Person QR code and location QR cod
• Do we have to collect the surname of a child to meet OpenSRP

For ministry

...

Test Case

...