Table Of Contents
Scoping Details | |
|---|---|
| Responsible Person: | Christina Riley |
| Other parties to review/input: | |
| FYI: | |
| Targeted release date: | date |
| Jira Status: | ticket link |
Link Jira tickets
The responsible person owns this feature from scoping to tracking development by Ona and providing clarifications if needed, to testing and sign off. Status
Status
# | Step | Status |
|---|---|---|
| 1 | Responsible prepares rough business analysis/reqs doc | COMPLETE: Christina Riley |
| 2 | Get CHAI review | IN PROGRESS: Vivek Agrawal Pedro Pagalday Olivares |
| 3 | Get Akros Review | |
| 4 | Get Ona feedback | |
| 5 | Responsible - 1 iteration for feedback | |
| 6 | Ona sign off | |
| 7 | Ona tech spec scoping | |
| 8 | Ona LOE | |
| 9 | Ona scheduling |
Definitions
The active detail view and active map view of the web UI contain progress indicators and goal targets:
Progress indicators are percentages that indicate the in-field coverage/progress of a given activity. T
- The progress indicators have a numerator and denominator and are calculated as follows:
- Numerator: the total number of units of a given task completed, divided by:
- Denominator: the total number of units that are eligible to be completed under the current plan.
- They should always be displayed for each task/intervention associated with the given plan.
- The denominator of the progress indicator is dynamic and can change as structures/points are added and/or marked as ineligible.
Goal targets are percentages or counts and represent a target to be obtained in order for a given activity to be marked as 'sufficiently complete'.
- Goal targets are defined by the program.
- Goal targets should be configurable; they may be a specific percentage measure of total progress or a static count.
- Goal targets should only be available to be listed for intervention tasks that are associated with the given plan.
- Goal targets are optional.
Requirements
Progress indicators and goal targets are documented on the 'Plan definition goals' tab of web ui data dictionary and the Reveal dashboards. The denominators, numerators, and goal targets are defined as follows:
Structure-level indicator
- Denominator (goalDenominator): total number of eligible structures = (# of structures enumerated) + (# of structures added in-field) - (# of structures marked as ineligible for structure-level activity) within the plan:
- This denominator is dynamic and will change as structures are added in the field and as structures are marked as ineligible for the activity
- Q: Do we want to define this as part of the plan, or within the jurisdiction (i.e. focus area)? I have defined as part of plan to allow for structures (& individuals, points) added outside of the focus area to be counted.
- Numerator (goalTargetMeasure): equals the number of eligible structures with activity completed within the plan:
- Family registration: = # of structures with completed family registration module (i.e. head of household has been added)
- ITN distribution: = # of structures with any nets distributed
- Q: Should this be with adequate net coverage based on coverage per sleeping spaces (1 net per 2 people)?
- Q: How should non-adequate coverage / no-net distribution (form completed) be displayed?
- IRS: = # of structures visited and sprayed
- Q: How should partially sprayed or visited & not-sprayed be displayed?
- Goal target (goalTargetValue): this is the targeted number of eligible structures needed for activity completion for the plan:
- Family registration: = percentage = (100%, but configurable) of structures with families registered within the plan
- ITN distribution: = percentage = (90%, but configurable) of structures with nets distributed within the plan
- IRS: = percentage = (90%, but configurable) of structures sprayed within the plan
Individual-level indicator
- Denominator (goalDenominator): total number of eligible individuals = # of individuals registered within the plan:
- This denominator is dynamic and will change as individuals are registered to a household
- Q: Do we want to define this as within the jurisdiction (i.e. focus area), or as part of the plan?
- Numerator (goalTargetMeasure): equals the number of eligible individuals with activity completed within the plan:
- RACD: = # of individuals with completed MBS/RACD form
- Mass Blood Screening: = # of individuals with completed MBS/RACD form
- Goal target (goalTargetValue): this is the targeted number of eligible individuals needed for activity completion for the plan:
- RACD: = discrete count = 50 individuals with completed MBS/RACD form within a 1km radius of the index case (but configurable)
- Mass Blood Screening: = percentage = 100% of individuals with completed MBS/RACD form within the focus area (but configurable)
Point-level indicator
- Denominator (goalDenominator): total number of eligible points = (# of points added in previous campaigns) + (# of points added in-field) - (# of points marked as ineligible)
- This denominator is dynamic and will change as points are added in the field and as points are marked as ineligible for the activity
- This assumes that only point-types that are eligible for the plan generated will have an indicator listed. For example, if no entomological activities are selected as an intervention for the current plan, then all ento points (mosquito collection & larval dipping) will be marked as ineligible (gray) and will not have progress or target goal indicators listed on the web UI for this plan.
- Numerator (goalTargetMeasure): equals the number of eligible points with activity completed:
- Mosquito collection: = # of mosquito collection points completed
- Larval dipping point: = # of larval dipping points completed
- Potential Area of transmission: = # of PAOT points documented
- Goal target (goalTargetValue): this is the target number of eligible points needed for activity completion for the plan:
- Mosquito collection: = target of 3 (but configurable)
- Larval dipping: = target of 3 (but configurable)
PAOT: = target of 1 (but configurable)
Focus-level indicator
- Denominator (goalDenominator): number of activities that must be carried out at the focus level
- Assuming there is only 1 activity as these each currently stand
- ICC: number of eligible index cases to be confirmed
- BCC: number of BCC activities to be carried out
- Numerator (goalTargetMeasure): number of activities completed at the focus level.
- ICC: number of index cases confirmed
- BCC: number of BCC activities completed
- Goal target (goalTargetValue): This is dichotomous as complete vs. incomplete for the given activity (assuming only 1 activity available to be done)
- ICC: = target of 1 (but configurable)
- BCC: = target of 1 (but configurable)
Mock-Ups
Active map view of the web UI contain progress indicators and goal targets:
The active detail view:
Active detail should look the same except without the map.
Views
The active detail view:
Active map view of the web UI contain progress indicators and goal targets:
Justification
Dependencies
Notes
Questions
- Q: Do we want to define counts as part of the plan, or within the jurisdiction (i.e. focus area)?
- I have defined as part of plan to allow for structures (& individuals, points) added outside of the focus area to be counted.
- Q: Do we want to follow/define more complicated display logic for interventions with partially complete status (i.e. IRS/ITNs)? Or keep a more simplified view for FI?
- Q: Should visualization of historic index cases & PAOTs across investigations (potentially hover-over to see historical dates/comments) be included in this scoping doc?
Test Case
# | Step | Pass / Fail | Comment |
|---|---|---|---|
1 | |||
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
Additional tester comments: |