Page Comparison

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.

...

• Akros provides a plan template for MDA (spreadsheet)

  • Activities:

    • Register Families

    • MDA Round 1

• 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 registers family (current behaviour)

  • The user enters the family module and sees the list of tasks (current behaviour)

    • There are 2 tasks is 1 task 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 When the form is saved, we need to generate an adherence task for each family member that received treatment (treatment = “Received”). This task is labeled MDA Round 1 Adherence

• The user navigates back to the map view (current behaviour)

• The structure is color coded as defined in the color coding business logic

  spreadsheet

  section below

• 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

Software to be Developed

We need to develop the following items at a high level:

Android MVP

• We need to create the following forms:

• Zambia Register Family

• Zambia Add Family Member

• Zambia MDA Dispense

  • Note: this form has a cascading drop-down of three fields from a list that’s defined server side

Zambia MDA Adherence

Adherence visit

• The user taps the green or orange structure from the map view and is directed to the family module task list view

• The user taps the MDA Round 1 Adherence tasks for each family member and completes the form

• The user saves the form and is returned to the family module task list and they see a status change of the task button

• The user navigates to the map view and the structure has turned blue

Software to be Developed

We need to develop the following items at a high level:

Android MVP

• We need to create the following forms:

  • Zambia Register Family

  • Zambia Add Family Member

  • Zambia MDA Dispense

    • Note: this form has a cascading drop-down of two three fields from a list that’s defined server side.

  We

  • Zambia MDA Adherence

    • Note: this form has a cascading drop-down of two fields from a list that’s defined server side.

• We need to add an activity to the Focus Investigation Plan

  • This activity is executed on the person level, just like the Blood Screening

• Improve how tasks are generated in the Android client based on form save events:

  • We need the ability to generate tasks in the android client as follows

    • Generate a MDA Dispense task when a Register Family or Add Family Member form is created for all people registered

    • Generate the adherence task once a MDA Dispense form is created based on form business logic.

  • We need to remove the hard coded bednet distribution task in the Android client when a family is registered

  • We need to remove the hard coded blood screening task in the Android client when a family member is registered.

• We need to display these make sure the tasks in the list view and enter directly into the form if tapped from the list vieware grouping as is currently done in focus investigation.

• Update the business logic for color coding.

Android To Do After MVP

• Ineligible Structure Marking (currently in the Register Family Form)

• Add support for MDA Round 2 (to be scoped)

• Sorting, filtering and searching task list view (to be scoped)

• (not explicitly in scope) View form submission of MDA Dispense and Adherence tasks (current FI behaviour in Thailand that may be necessary form MDA)

• General Improvements:

  • assign the correct plan activity when in a task when it’s generated (Currently, client side generated tasks have hardcoded “focus” that targets the activity type “IRS” instead of the UUID of the activity.)

  • make task generation dynamic in the client side based on the activities that are listed in the plan so we don’t have to hard code this activity as MDA

...

• Zambia Register Family

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

• Zambia Add Family Member

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

Business Status Changes

The current IRS structure level business status in Zambia is as follows: (copied from this sheet)

The MDA business status needs to be targeted at the structure level in Zambia is as follows: (adapted from this sheet)

The target here is to have green, red and orange by the end of the first day. Then, when they go back for the adherence visits, they are looking to turn everything blue.

The MDA Dispense business status at the person level should be as follows:

The MDA Adherence business status at the person level should be as follows:

Note, we do not have a not eligible color for the MDA Adherence task because they should not be generated for people who are not eligible in the MDA Dispense form.