| Table of Contents |
|---|
...
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 (Point) Distribution that will have a default activity type of Drug Distribution 1 of Mass Medicine Administration and Register Child.
In plan creation we will add a way to upload a CSV roster file.
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-470
. 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.Jira Legacy server System JIRA serverId 3420e60a-4e6f-3f80-8335-059c22bb40aa key RVL-834
...
- 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)
- National ID (integer)
- Does not have National id (boolean_
- National ID (integer)
- Reveal ID (integer) . MB: Is this an ID that will be provided or one the system needs to generate? AM: System gen = OpenSRP id. National ID is provided. SB: Not the OpenSRP IP, they want the ID to follow a specific pattern
- Name of child (string)
- Child's allocated sex at birth ('Male', 'Female')
- Child's date of birth (date YYYY-MM-DD)
- Date of birth estimate 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)
...
- Access the list view (current list view) . MB: Is this linked to a specific school or operational area? Please clarify. AM: School view! Schools will be points in OA and may be 1:1 school:OA or many:1 school to OA, but we only need a view at school level.
- 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' . MB: Does this just meant they weren't on the imported list? I see limited value in this designation. AM: No. There may be school-going children who were missed on import. Value is to be able to disaggregate reporting between school-going and not. I.e. to know how many not school going we reach in school workflows, does that meet what our estimates are, etc.
<How do we want to treat community children? Can we add "From community" as their classroom attribute? Otherwise we have to make that attribute non-required.>
Workflow 4 - Edit child (edit)
We may need to make edits to a child if:
SB: I think that was anwered in the previous line, but we will have a Yes/No for Enrolled at School, so we can compare the number of children reached that are school-going vs. not
Workflow 4 - Edit child (edit)
We may need to make edits to a child if:
- Registration info is incorrect
- Child has moved classrooms . MB: Editing classrooms. Will classroom list be free text or some kind of pulldown. Will the classrooms be predined or given some name. if a unique name, then pulldowns will be harder to do. AM: In this use case, free text is fine, so we do not need to manage a classroom list - it will be a free text attribute for the child entity.
- Other reason
...
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. See Data collection data dictionary
MB: do kids get a single dose one time or is there follow-up. Eg. Will they come back to the school at a later date for another round. AM: I'm adding details on task gen shortly but publishing to save work (we may need two tasks). SB: It has been decided that they will only be receiving one round
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
- Region
DistrictInkhundlaCommunitySchool- Age Group
- Individual List View of ChilrenChildren
Need to disaggregate likely by age, gender, and school-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 | ||||||
|---|---|---|---|---|---|---|
|
...
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.
...
- Search requirements (all based on child-level attributes in data dictionary registration details)
- Classroom
- National ID
- Date of birth
- Name
- Sort requirements
- Classroom
- National ID
- Date of birth
- Name
- Filter requirements
- School grade/form
- Age category
- Sex
- School-going vs. non-school-doing
- School grade/form
- Name
- Agegoing
Child-specific view, accessed from the child list view. Should contain
...