Status

The following tickets are detailed in this document:

...

• These children are people , not constrained to families
• We will define operational areas based on the location of the schools. An OA boundary with be automatically drawn by taking an 8km radius around the school and there will be only one school per operational area
  • The relationship between the school and the operational area will be assigned in the process of loading locations. A school will be marked as distribution point that will have a parent attribute of the operational area.
• Therefore, we will not treat a school as a household type location; distribution point will be the location type
• We will manage classrooms as an attribute to the school <Ona: How will we manage this list?> 
• Children who are registered ad-hoc will not be linked to a location. No longer relevant since Workflow 0 not being done. Children registered ad hoc in the school workflow will be associated with that school.
• schools to be within operational areas.
• We do not need to collect the classroom attribute; if any classroom data collected, it will be free text, not used for analysis.
• Children registered ad hoc will be associated with the school operational area they are registered in.
• Schools will have 1 Drug Distribution task per eligible, depending on the child's age (from the registration attributes).

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 Data Collection Data Dictionary defines the forms and data needed for register child and drug distribution workflow.

Plan: School-level intervention (NTD Point Distribution)

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

  Jira Legacy
  server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-855

• A school should be a point that is tied to an operational area. There will be just one school per operational area. 

Location types: Distribution-point (typetypes=school, health-facility) 

Jira Legacy
server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-471

Distribution will always take place at the school. Task generation will involve generating tasks against entities (children) linked to the distribution-point level.

Activities/Tasks available:

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

Workflow

...

1

...

-

...

1. Create families that students are linked to, based on the GPS coordinates that are collected against them. This breaks key assumption that we do not need to do family creation or link students to families or link across school and community.
   1. Would require all students in one house to have same GPS coordinate to determine who is in which family.
   2. These families would have to be an attribute in the student roster load CSV.
      1. This load would have to do a lookup on enumerated structures based on family GPS coordinate.
      2. Would allow us to evaluate multiple students for the business status. 
2. Import GPS point for each student. This does not follow typical location-person linkages in Reveal. We do not typically have a point location for an individual.
   1. Import GPS locations of students as locations in Reveal 
   2. GPS point would be an attribute in the student roster load CSV.
      1. Link would have to be created here
3. Use Reveal for in field enumeration and family registration

...

Workflow 1 - Plan Creation w. Roster import (Web)

This will take place at a central location ahead of the intervention. Schools will send their rosters to a central administrator who will create a plan for the intervention. The administrator will have to compile these roster rosters into an one import for all schoolscommunities; s/he will have to cross check spellings of schools so that they map correctly to the school list in Reveal. have to map the schools on the roster to operational area names or ids defined in Reveal so that the Reveal names/ids are on the roster import template.

We will follow the regular prioritization planning workflow on the Web UI, similar to IRS planning. The plan definition template can be found here: Web UI reporting and plan template We will add a plan type of NTD School (Point) Distribution that will have a default activity type of Drug Distribution of Mass Medicine Administration and Register Child.

In plan creation we will add a way to upload a CSV roster file. 

Jira Legacy
server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-470

 .This likely should be done in a technical and design way that is compatible/similar/the same as 

Jira Legacy
server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-834

. This case is unique in that we are uploading entities to exist within an OA, rather than importing attributes against OAs. The way we may want to treat and count these entities in the planning interface is similar to the way we want to count and treat structures in OAs. FYI Pierre Dane.

• Components
  • Question name: CSV roster
  • Upload button
  • Download template button
  • Help text - reads "You may upload a CSV with the roster of the children in the school. You must include all required fields in the template."
  • View current roster
• Workflow first roster upload . 
  • Click Download template (template will be laid out per CSV requirements, below) –> CSV file downloads to desktop
  • Complete template and save  
  • Select Upload, select CSV file
  • Validation checks of CSV
    • Required fields
    • Check schools  schools against OAs in system for schools
    • Check classroom attributes against classroom list <how will we manage classrooms
    • Other? <What other validation checks are necessary?>
    • Reveal 
    • Check that fields with dropdown select type, boolean type, numeric type and Yes/No type have valid entries
    • Error message if failed:
      • "Upload failed. Check your CSV to make sure all required fields are filled in".<Other error messages depending on validation checks>
      • "Upload failed. Check field (field name) in your CSV to make sure it is a valid entry type
    • Message if successful: "x out of y individuals were successfully uploaded"
  • View/download current roster hyperlink
    • This appears as a hyperlink "View current roster <file name"name>
    • Can click on this and see the assigned ids of students, student list with attributes
    • There should be a way to download this information as a CSV that looks identical to what was uploaded.
      • Must include the Reveal operational area id and student identifiers (all fields from the Registration dictionary)
• Workflow to replace roster replace roster
  • A roster can only be replaced if they have not started to collect data in that plan (plan!=draft). Once they start to collect data, any changes must be made through the client.
  • Select Upload, select CSV file
  • Confirmation message: "This upload will replace the current roster. You will not be able to recover the previous roster. Are you sure you want to proceed?" 
• Restrictions
  • Once a plan status is not in 'draft' the roster may not be uploaded/replaced. 
  • If a plan has data collected against it, the roster may not be uploaded/replaced. 
  • Cannot edit individuals rows or parts of the roster on web, must edit CSV and replace if changes needed, or can edit on client later 

CSV requirements <Will be defined once the register student form for the client is defined - will have the same requirements>

...

• Region (maps to admin unit and will match Reveal)
• Inkhundla (maps to admin unit and will match Reveal)
• School (maps to operational area and will match Reveal)
• Does not have National id (boolean_
• National ID (integer)
• Reveal ID (integer), not autopopulated, this will be defined and entered by country protocol
• Name of child (string)
• Child's allocated sex at birth ('Male', 'Female')
• Child's date of birth (date YYYY-MM-DD)
• Date of birth estimated (boolean)
• Age category (6-10, 11-15, 16-18, 'Adult')
• Currently enrolled at school ('Yes, 'No'
• Name of school attending, if from another school (string)
• School grade/form (where form 1 is grade 8) ('Form 1', 'Form 2', 'Form 3', 'Form 4', 'Form 5', 'Grade 1', 'Grade 2', 'Grade 3', 'Grade 4', 'Grade 5', 'Grade 6')
• Class number (string)

Workflow 2 - Roster import (Client) -

...

Out of scope for MVP

Workflow 3 - Register child (client) 

Jira Legacy
server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-472

...

Child registration will follow similar UI and workflow in the client as family member registration, however, children will not be attached to families, so the UI for entry into child registration will be different.

Suggested Workflow <Is there already a UI and workflow for this through immunization OpenSRP?>

• Access the list view (current list view) . This will be a school-view of the list. We will have 1 school (point) per operational area.
• Have button somewhere for 'Reg child'
• Selecting that button takes you to the Register child form (See Data collection data dictionary)
• Completing the registration takes you to the child-specific view. Task should have generated and be visible on task view for child.
• Back button from there takes you back to list view.

...

• Child will be marked as coming from the community according to the registration attribute 'Currently enrolled at school' == 'No' . This attribute is needed so that we can disaggregate children in reporting based on whether or not they attend school.

Workflow 4 - Edit child (edit)

...

1. Registration info is incorrect
2. Child has moved classrooms. Classroom will be stored as a free text attribute on the child, we do not need to manage a classroom list or a separate classroom entity. It is understood that this means we will not be able to disaggregate on classroom.
3. Other reason

Suggested Workflow <though this may already have a UI in the immunization OpenSRP workflow>

• Access the list view
• Select a child
• Access child-specific view 
• Access edit view for the registration info
• Selecting that button takes you to the Register child form where you can make edits

...

When drug distribution occurs, teachers will distribute drugs to and collect data against each child. Drug distribution may happen by classroom or not. This will be a drug distribution task; each child will only have one round of drugs and therefore one task generated. See Data collection data dictionary. 

Task generation must happen in two places:

...

• Access list view.
• (as needed) Perform necessary filter/searches/sorts.
• Access child-specific view
• Access child-specific task view
• Complete task
• Child-task view updates color based on business status logic. See Data collection data dictionary
• Go back to full list view - task color for that child also updated here

Reporting

Dashboards to be defined, likely two types. See Web UI reporting and plan template

• Coverage
• Performance

Drill down levels

• DistrictRegion
• Inkhundla (comparable to a district in size)
• School (32 schools)
• Age Group
• Individual List View of Children

Need to disaggregate likely by age, gender, and classroomschool-going (or not)

• We need to define what are the key values we need to build in tables in Superset
• Disaggregation would be by any other items from data dictionary mentioned like gender, classroom, precise age, dose given, drugs taken etc.

On app indicators to be defined. See Data collection data dictionary

Mock-Ups

Views/UI . 

The below are new components we believe to be needed for the UI. 

Jira Legacy
server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-502

(Android) Child registration - there needs to be a place in the client where we can add a new child. I would guess this is from the chid child list view and is an icon somewhere on that screen.

(Android) Child list view (This could be the same as the task list, however, we would want to see all children, regardless of task status. So if there is ever a reason a child would not have a task, then we might need a separate view for all children that is not task based)

• Search requirements (all based on child-level attributes in data dictionary registration details)
  • Classroom
  • National ID
  • Date of birth
  • Name (surname/given)
• Sort requirements
  • Classroom
  • National ID
  • Date of birth
  • Name (surname/given)
• Filter requirements
  
  • School grade/form
  • Age category
  • Sex
  • School-going vs. non-school-doing
• Sort requirements
  • School grade/form 
  • Name
  • Age
• • going

(Android) Child-specific view, accessed from the child list view. Should contain

• There is a task view for the child. I imagine this to look similar to the family task view, but be for an individual.
• There is also an edit view for the registration info that starts from this child-specific view. Could also be similar to editing family member registration.

(Web) Reporting views in line with above.

Justification

Dependencies

Notes

Questions

...

How will we manage and maintain a list of classrooms for each school? 

...

to consider in technical scoping

The roster CSV upload in the plan will need to have validation checks? What others, not defined above are necessary? What level of detail can we have in error messages for these checks?

Will the CSV template define the expected input types? In particular, this will be needed for input types that are select one, boolean, Yes/No etc.

Is there already a UI and workflow for much of this work through  immunization OpenSRP?

...