Table Of Contents

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

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.

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

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. 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 does need to review/approve plans for a visit to a focus. 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 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.

Pedro Pagalday Olivares - can you review the above user-types and make sure they align with how you envision the team structure & permission levels documented in the Team Structure and User Assignment document.

Requirements

• 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