...

• Support Eligibility when tapping a structure
  • Open Structure eligibility form, once saved, execute logic based on the business_status to enter the register family form or back to the map view
    • The business status would determine the next step and it would be calculated in the bottom of the form
      • You would need to pass the business_status from the first form to the second so that we can appropriate close the task
• QR Management
  • Add this as an identifier to the family entity
  • Make it so that we can search based on this QR code family entity (index the database)
  • QR Codes should be entered or edited at the following points
    • Eligibility form - This QR code will be tracked against the location if they are eligible and not home or not fully home (locationQrReference)
    • Register Family - This QR code will be tracked against the family (familyQrReference)
    • Edit Family - This allows us to capture or update the QR code for the family at any time
  • Search by QR Code
    • Any time we read a QR code for search we need to search the following identifiers
      • Step 1: familyQrReference
      • Step 2: locationQrReference
        • If we match on this, enter the register family form passing in the location.id and this locationQrReference value so that it can be turned into the familyQrReference.
          • Delete the locationQrReference so that we can't find this again in this table and we would automatically redirect to the familyQrReference
• Create/Modify forms:
  • Eligibility Form when you click on a structure
  • Modify the Register Family form
  • Modify the Register Family Member form
  • Modify the Distribution form from MDA
  • Include ability to view and edit completed forms 
• Allow people to search by families and return a list of families
  • (We need Roger to help with this)
  • Outstanding Questions on this:
    • Problem: If the family isn't registered against a structure the search from the map view will return nothing, but the search from the task list view will return a result.
      • Does the task list view meet this need?
        • Do we need to support searching by families that don't have a task for this plan?
      • What's the difference between the "all clients view" from Eswatini and the task list view?
      • Do we need both?
• Allow people to add families outside of structures
  • (We need Roger to help with this)
  • We definitely need them to be able to add a family if a search result in a list returns nothing or a QR search returns nothing.
  • Question
    • Do we need to allow them to add families from the map view without associating a structure?
    • How do we allow a user to add a family from the task list view (assuming that's the primary search view for families)?
• If they decide to support taking roll
  • Create a Take Roll Form - this form includes a button to read the QR code
  • Add a Take Roll Activity to the Plan.action section
  • Code the process for generating a take roll action when the family is registered
• Edge Cases/Outstanding Questions
  • What happens if we distribute a QR code to the location and to the family and we then need to merge them?
  • Linking Families to locations
    • (Supported) When we register a family in the field, we link the family to the location
    • (Supported) When we leave a QR code at a location that's eligible, but not home, we have the ability to link the family to that location when we read the QR code because the QR code that was distributed to the location (see QR code search Step 2)
    • (EDGE CASE) When we register a family from the task list view, we have no way of knowing the location they should be registered against.
      • The family should be linked to the jurisdiction from the plan.
      • Out of scope
        • We are looking at a floating family in the family module
        • We see that they are not linked to a structure through a visual indicator
        • We could have the ability to click the option menu to kick off a workflow that allows them to link the family to a structure
          • Click option menu
          • Open map view of the entire operational area
          • User click a location
            • We query to see if a family is already registered
              • If registered, we don't allow it and recommend that they archive that family first
              • If not registered, we highlight the location
          • User clicks save
          • We add the "residence" to the family
  • We need a status update on what we will deliver for Workflow 4. It is not included in this spec so far. Isabel will follow-up on this

Web

• New plan type of: NTD MDA in community
  • This plan type has the following tasks: 

  (Isabel will document this)

  Justification

  Notes

  Questions

  ...

  • • • Register Family (BOTH linked to location and also floating) - does not autogenerate
      • Register Family member - does not autogenerate 
      • Drug Distribution - autogenerates against any eligible, registered child
  • Follow the IRS model for plan, where we see a map of all eligible operational areas and point and click which we prioritize. 

  Justification

  
  

  Notes

  
  

  Questions

  Livashan Soobramoney pls help us to answer the questions below 

  1. Will health workers be visiting a combination of homes already registered and identified in Reveal and "unspecified structures" during this campaign, or only "unspecified structures?"
     1. The answer to this question directly impacts how we build our issue QR code workflow 
  2.  Our assumption is that QR codes will only be issued to any families registered at their homes - is this correct?
  3. The requirements above mentions a family list view in addition to a task list view - is there any reason that the user would need to look through a list of floating families
     1. What would that use case be?
     2. Is it sufficient to be able to search for families, see search results, and then enter the family module to view members and forms?
     3. The distinction between two list views (lists of floating families versus lists of tasks) could be a bit confusing to end users, so we'd prefer to maintain a single view unless there are other business requirements here we're missing  
  4. Has any additional conversation been had on workflow 4 that is not documented above? Our understanding is that a final decision had not been reached on an implementation path, is that correct?
     1. How realistic is it that users at health facilities will have connectivity in Zambia?
  5. Our assumption is that the reporting requirements in the Reporting Data Dictionary shared above have not been updated for this implementation - is this correct? 
     1. It references % of people screened, and % of case-triggered FIsTest Case
  6. Have any decisions been made about what drug will be dispensed in this trial? 
     1. When will the data dictionary be updated?
     2. We are assuming that this program will only be dispensing a single dose of the drug 
     3. No adverse drug reaction reporting is included above - pls confirm this
     4. Has "eligibility" been defined yet?

  
  

  
  

  
  

  #	Step	Pass / Fail	Comment
  1
  2
  3
  4
  5
  6
  7
  8
  Additional tester comments:

  ...