...
# | Step | Status |
---|---|---|
1 | Responsible prepares rough business analysis/reqs doc | |
2 | Get CHAI review | |
3 | Get Akros Review | |
4 | Get Ona feedback | |
5 | Responsible - 1 iteration for feedback | |
6 | Ona sign off | |
7 | Ona tech spec scoping | |
8 | Ona LOE | |
9 | Ona scheduling |
Definitions
Eligible child
'Floating family' The following tickets are detailed in this document:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-476
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.
...
- 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
Workflow 1 - Main
...
- Register family, do not treat
...
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
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- 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.
Jira Legacy server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-
...
Edge Case 1
Child found somewhere else in village and house is already registered. Treat and link back to house.
...
856 - 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
- Visit home, tap on house from map view, following questions appear before kicking off family registration
- Confirm house is residential, someone is home to give info, and consent is given, is main house?
- 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)
- After answering yes to all of Workflow 0
- Access family module, register family
- Register each child, including children that are not present
- Treat each eligible, present, child
Workflow 2 - Leave QR code when no one is home
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
b) Child has no QR code - link through list view lookup
Edge Case 2
- In 'Add family' workflow (1), after answering 'no' to 'is anyone home'
- User is taken to a QR scanning view.
- "Scan the QR code that will be associated with this location"
- User scans QR code
- User leaves two QR stickers at house.
Workflow 3 - FLOATING FAMILY, NOT AT HOUSE: Linking to Location and entering Family Module
- Find someone in village who belongs to unregistered household
Jira Legacy server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-476 - Common because there are lots of people who go out to the field/fishing
- Link that household back to location 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
- Attempt to link to existing household first by searching map and list view
- Searchable features: all household names
- Access family module from list view through a button "Register floating family"
828Jira Legacy server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-
Edge Case 3
- Find someone in the community who doesn’t belong to community, register without a locaiton
476 - "Does this family/child have a QR code"
- If yes, open QR code scanner to link (Details in QR linking below)
- If no, "Are you sure this family/child does not belong to an already registered house?"
- "Does this family/child have a QR code"
- Proceed to rest of Workflow 1
Use QR code to link family to location
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
|
Assumptions:
We will not be able to unlink and relink to "fix" where linkages were made incorrectly in the MVP.
- In registering floating family workflow, when triggered to open QR scanner:
- Potential results from scan
- Success
- QR code matches this village and is not yet linked
- Confirmed match, show view of household location on map
- "Confirm link?"
- If yes, make link and proceed with workflow
- If no, warning message "This QR code links with the house shown on the map; are you sure you do not want to link?"
- Do not link → back to question in form asking "Does this family have a QR code"?
- Confirmed match, show view of household location on map
- QR code matches this village and has already been linked
- "This code is already linked with this structure. Proceed?"
- "Yes" → enter family module
- "No, go back" → back to question in form asking "Does this family have a QR code"?
- "This code is already linked with this structure. Proceed?"
- QR code matches this village and is not yet linked
- Failure
- QR code does not match this village
- "Okay"→ back to question in form asking "Does this family have a QR code"?
- QR code does not match this village
- Success
Workflow 4 - Point-distribution
- 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
- We expect this to happen potentially multiple times
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
- 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 . Using → Icon from list view?
- QR code scan creen
Justification
Notes
Questions
...