This document defines the scope for the Mass Drug Administration feature set that is being initially deployed in the Zambia implementation. These workflows can be more broadly used across multiple country implementations.
...
Mass Drug Administration is abbreviated MDA and includes the process of administering two rounds of pills to every person in an operational area. MDA focuses on reducing the number of people who have dormant malaria virus so that the operational area ….(Craig Appl can you finish the sentence here)
Round 1: Healthcare workers go door-to-door, register each family and family member. Once registered, they watch the person take the first dose and instruct them to take other doses (MDA Dispense). A few days later, the healthcare worker visits each house again and asks if everyone in the house took all of the medicine (adherence).
Round 2: The healthcare workers return to the operational area 30 days later to do the same thing they did in round 1. This round requires less work because the majority of people area already registered. They go door-to-door and verify that everyone in the household was registered. If they weren’t registered, they register them. They distribute another round of pills, watch each family member take them and instruct them to take the other doses (MDA Dispense). A few days later, the healthcare worker does an adherence follow-up.
...
Akros provides a plan template for MDA (spreadsheet)
Activities:
Register Families
MDA Round 1
On Ona develops the plan and POSTs it to the OpenSRP server
The plan generates tasks
Register Families on all enumerated structures (current behaviour)
(We don’t need to generate tasks on family members because no family members are registered)
Akros configures users in the Web UI to assign users to the operational area
Ona uploads the dynamic list of users to populate the form drop-downs
The user logs in to the Android client (current behaviour)
The user sees the list of all enumerated structures in yellow (current behaviour)
They can add points as is normal (current behaviour)
The user taps a structure and register registers family (current behaviour)
The user enters the family module and sees the list of tasks (current behaviour)
There are 2 tasks assigned to the head of household for this structure. One task is labeled MDA Round 1 Dispense and the second is labeled MDA Round 1 Adherence.
The user can add family members (current behaviour)
There are 2 tasks assigned to each family member. One task is labeled MDA Round 1 Dispense and the second is labeled MDA Round 1 Adherence.
The user taps the button on the right labeled MDA Round 1 Dispense
Note, we will not have business logic that restricts a user from completing the MDA Round 1 Adherence form before the MDA Round 1 Dispense form.
The user completes the form.
The button on the right changes to Complete (current behaviour)
The user completes all MDA Round 1 Dispense tasks for all family members.
The user navigates back to the map view (current behaviour)
The structure is color coded as defined in the color coding business logic spreadsheet
The user can tap the list view to view a list of tasks (current behaviour)
Tasks are grouped by household (current behaviour)
The user syncs the tablet
The supervisor logs into the Web UI to view reports (current behaviour)
The supervisor navigates to the Focus Investigation Reporting Page (current behaviour)
The supervisor sees the plan and clicks on it. (current behaviour)
The supervisor drills down to the selected operational area
The supervisor clicks the operational area and views the map view with the two activities
...
After save we need to develop two tasks following the template:
Task 1
“code”: “MDA Dispense”
“description”: {Needs to be updated}
Task 2
“code”:”MDA Adherence”
“description”: {Needs to be updated}
After save we need to develop two tasks following the template:
Task 1
“code”: “MDA Dispense”
“description”: {Needs to be updated}
Task 2
“code”:”MDA Adherence”
“description”: {Needs to be updated}