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 3 Next »

Responsible team memberAnnie Martin
Current Team Member
StatusStill drafting
Targeted release Date

Scoping Complete Date



Jira Issue

LOE

Priority

Status

#

Step

Status

1Responsible prepares rough business analysis/reqs doc
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

The following tickets are detailed in this document:

RVL-858 - Getting issue details... STATUS

RVL-856 - Getting issue details... STATUS

RVL-506 - Getting issue details... STATUS

RVL-476 - Getting issue details... STATUS

Requirements

  • 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.

Assumptions

  • You will never treat a child without a caregiver to consent. All workflows rely on registering a family/family head.
    • You cannot register a child without a family to link to them.

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.

Plan: NTD MDA in community  RVL-858 - Getting issue details... STATUS

  • This should follow the IRS model for plan, where we see a map of all eligible operational areas and point and click which we prioritize. 

Location types: Residential structure

Activities/Tasks available:

  • 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 entities.  RVL-856 - Getting issue details... STATUS
  • Drug Allocation (team level task not linked to location)
  • Drug Return (team level task not linked to location)

Workflow 0 - Confirm household eligibility and presence

  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 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 no one is home  RVL-475 - Getting issue details... STATUS

  1. In 'Add family' workflow (1), after answering 'no' to 'is anyone home'
    1. User is taken to a QR scanning view. 
    2. "Scan the QR code that will be associated with this location"
      1. User scans QR code
      2. User leaves two QR stickers at house.

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

  1. Find someone in village who belongs to unregistered household  RVL-476 - Getting issue details... STATUS  or does not belong to that community (homeless, orphaned children) or comes to you at a location in the village that is not the household location
  2. Attempt to link to existing household first by searching map and list view
    1. Searchable features: all household names
  3. Access family module from list view through a button (question) "Register floating family"  RVL-476 - Getting issue details... STATUS
    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?"
  4. Proceed to rest of Workflow 1


Use QR code to link family to location  RVL-828 - Getting issue details... STATUS

Assumptions:

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

  1. In registering floating 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

Mock-Ups


Views/UI

  • Add floating family 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 from list view?
  • QR code scan creen

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

  • What are the number of tablets typically given? Need for categories for drug distribution
  • Do you still give one set of drugs if you run out of the other?
  • Need to confirm age eligibility with the ministry
  • Drug allocation - record by packets rather than tablets? What is the max number (for validation rules). Need to understand how many pills each packet contains
  • Do we want to have school in our hierarchy?


Test Case

#

Step

Pass / Fail

Comment

1




2




3




4




5




6




7




8




Additional tester comments:






  • No labels