...

• 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 typecommunity-level polygons that are provided by the Eswatini team.
  • Operational areas will have two types of distributions points within them, school, or health facility (1 or 2 of each per community). The list of students/children will be the same at all of these distribution points within a community. We want users within a community to be able to see the entire register list for that community, regardless of whether the child was registered at a school site or a health facility site. Tasks and entities will not differ based on distribution point type. Tbd, see below, if we handle these distribution points as locations or as attributes of the child.
• We will manage classrooms as an attribute to the school We do not need to the school <Ona: How will we manage this list?> collect the classroom attribute; if any classroom data collected, it will be free text, not used for analysis.
• 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 schoolthe community they are in, and the distribution point of their registration (could be school or community).

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

Location types: Distribution-point (type=school)  Jira LegacyserverSystem JIRAserverId3420e60a-4e6f-3f80-8335-059c22bb40aakeyRVL-471-point (types=school, health-facility) 

There are two different places where distribution may take place within a community - health facility or school. Distribution looks the same (event/task form is identical) at both places. A child may show up at either the school or the health facility, and we need to be able to access that child (and any child registrations done anywhere in the community) at all distribution point locations within the community. This gives us two options for tasking

1. Generate tasks against entities (children) linked to the community level location. School vs. Health Facility becomes child-level attributes to indicate where they were registered rather than the location that entities are linked to.
2. Generate tasks against entities linked to the distribution-point level AND come up with a list view option that can easily switch between or search across the tasks of multiple distribution points (schools, HFs) under a single parent (community aka operational area). 

Activities/Tasks available:

...

This will take place at a central location ahead of the intervention. Schools Communities or 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 communities 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 and Register Child.

...

• 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 fieldsCheck schools against OAs in system for schoolsfields
    • Check classroom attributes against classroom list <how will we manage classroomscommunities against OAs in Reveal
    • Other? <What other validation checks are necessary?>
    • 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>
  • View/download current roster hyperlink
    • This appears as a hyperlink "View current roster <file 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 (name)
• Workflow to replace roster
  • 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
  • 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>

• School Community - this will not be a user-facing attribute that is collected on the client since the client will auto-assign school based on OA. This is required for the web importthe web import.
• School attribute that child is associated with
• Health facility  attribute that child is associated with
• Classroom -
• x
• y
• z

Workflow 2 - Roster import (Client) - proposed not MVP

...

• Coverage
• Performance

Drill down levels

• Region
• District
• SchoolCommunity 
• Age Group
• Individual List View of Chilren

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

...

Dependencies

Notes

Questions

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

...

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?

...