Page Comparison

...

• These children are people not constrained to families
• We will define operational areas as schools based on community-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 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 will be associated with the school operational area community they are registered in, and the distribution point of their registration (could be school or community).
• Schools will have either 1 or 2 Drug Distribution taskstask per eligible, depending on the child's age (from the registration attributes) whether that school requires one or two rounds of dosing (will be pre-defined and based on endemicity)

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.

...

• Register Child - does not autogenerate
• Drug Distribution Round 1 - 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

• Drug Distribution Round 2 - autogenerates against any eligible, registered child in a school that is targeted for 2 rounds of distribution
  • This targeting is determined by an endemicity attribute that is associated with the child based on the school they attend.

Workflow 0 - Enumeration data links child to location (No longer need to support this workflow 1/29)

...

• 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

...