...
Scoping Details | |
|---|---|
| Responsible Person: | Christina Riley |
| Other parties to review/input: | |
| FYI: | |
| Targeted release date: | date |
| Jira Status: | ticket link |
Link Jira tickets
...
# | Step | Status |
|---|---|---|
| 1 | Responsible prepares rough business analysis/reqs doc | COMPLETE: Christina Riley |
| 2 | Get CHAI review | IN PROGRESSCOMPLETE: Vivek Agrawal Pedro Pagalday Olivares |
| 3 | Get Akros Review | COMPLETE: Christina Riley |
| 4 | Get Ona feedback | PENDING: Craig Appl |
| 5 | Responsible - 1 iteration for feedback | |
| 6 | Ona sign off | |
| 7 | Ona tech spec scoping | |
| 8 | Ona LOE | |
| 9 | Ona scheduling |
...
User types describe the admin level, type of tool usage, and objectives of tool usage of a given user:
- Subdistrict-level data collector and in-field decision maker: this user primarily uses the mobile client to carry out intervention activities in the field and monitor field progress through the web UI dashboards. This user will review the progress indicators and goal targets regularly to make decisions for the current focus investigation plan. These decisions will be based on achieving optimum field coverage for each intervention. Decisions that this user may need to make include:
- Should the entire focus be completed for the given intervention?
- Should houses be revisited for RACD/MBS if an individual was not present?
- Should houses be revisited if not enough bednets were distributed?
- District-level data collector and in-field decision maker: this user primarily uses the mobile client to carry out intervention activities in the field and monitor field progress through the web UI dashboards. This user will review the progress indicators and goal targets regularly to make decisions for the current focus investigation plan. These decisions will be based on achieving optimum field coverage for each intervention. Decisions that this user may need to make include:
- Should the entire focus be completed for the given intervention?
- Should houses be revisited for RACD/MBS if an individual was not present?
- Should houses be revisited if not enough bednets were distributed?
- District-level planning and strategic decision-maker: this user primarily uses the planning module and web dashboard to review historical data, create and plan routine interventions, and modify as necessary plans for case-triggered investigations, and is also responsible for team assignment. This user will also review plans that are in progress in the field and monitor the progress indicators and goal targets in the web dashboards. It seems this kind of user may not exist for Thailand FI as all district users are type 1, however, this will be the type of district user we see with IRS.This type of user needs to be combined with the previous 2 for Thailand. Typical IRS users.
- Provincial-level data collector and in-field decision maker: this user primarily uses the mobile client to carry out entomological interventions, mark the GPS points of breeding sides and mosquito collection points.
- Provincial-level planning and strategic decision maker: this user will access the web UI for plan review and active-plan monitoring across their province. They will also use the information to understand where active foci are, where there are active focus investigations, and strategically plan for routine interventions based on this information. Some provincial-level users will also create plans (& collect data), particularly in provinces where there is no district-level team.
QUESTION: Will any of these users create routine intervention plans? Or will this only happen at the district level? → sounds like a maybe given district users don't speak English- QUESTION: In December we leaned that the provincial staff do does need to review/approve plans for a visit to a focifocus. Would they need to see draft plans? Would they need to edit draft plans? → They need to create and edit plans
- Regional-level planning and strategic decision-maker: This user will access the web UI for plan review, edit and add across the provinces, they will also use the information to understand where active foci are, where interventions are being carried out, and strategically monitor and plan for interventions based on this information.
- Central-level planning and strategic decision maker: this user will access the web UI for plan review and active-plan monitoring across the country. They will primarily use the information to understand where active foci are, where there are active focus investigations, and strategically plan for routine interventions at a high level based on this information.the revision of national guidelines, monitor interventions are carrying out correctly, and enforce new guidelines as needed. This user will have the ability to edit plans but not create new ones.
- QUESTION: Will any of these users create routine intervention plans? Or will this only happen at the district level? → sounds like a maybe given district users don't speak English
- Central-level system administrator and community manager: this user understands the back-end of the Reveal tool, as well as integration with the BIOPHICS system, and is responsible for maintenance, trouble-shooting, the addition of users through OpenMRS, and coordinates, responds, and escalates issues to Reveal partners as necessary. This type of user may also collate Thailand-user-experience feedback. This user type will also review mobile client and web UI activity.
- At least one of these users needs full editing permissions.
...
Progress indicators and goal targets are documented on the 'Plan definition goals' tab of web ui data dictionary and the Reveal dashboards, including variable-specific calculations highlighted in light green. 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 completedtested on MBS/RACD form - Mass Blood Screening: = # of individuals
with completedtested on MBS/RACD form
- RACD: = # of individuals
- 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)
...