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 2 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


Definitions

Eligible child

'Floating family' 


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.

Workflow

Workflow 1 - Main

  1. Visit home (tap on house) 
    1. Find child at house and register and treat
    2. Family home but child not
      1. Register family, do not treat
    3. No one home
      1. Do not collect data - leave QR code  RVL-475 - Getting issue details... STATUS
  2. Tasks (Data Dictionary)- Family reg, Individual reg, Drug distribution


Edge Case 1

Child found somewhere else in village and house is already registered. Treat and link back to house.

a) Child has QR code paper for house - link through  QR code lookup. RVL-475 - Getting issue details... STATUS

b) Child has no QR code - link through list view lookup


Edge Case 2

  1. Find someone in village who belongs to unregistered household  RVL-476 - Getting issue details... STATUS
    1. Common because there are lots of people who go out to the field/fishing
  2. Link that household back to location  RVL-828 - Getting issue details... STATUS

Edge Case 3

  1. Find someone in the community who doesn’t belong to community, register without a locaiton  RVL-476 - Getting issue details... STATUS
    1. This is very infrequent, but there are orphans

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

  • View to select a task/add a task without a structure, attaches the family to OA. This is likely from the household list view
  • View to link 'floating family' with location. Using QR code

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