Table Of Contents
Scoping Details | |
---|---|
Responsible Person: | |
Other parties to review/input: | |
FYI: | |
Targeted release date: | 31st July 2019 |
Jira Status: |
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 Pierre Dane |
2 | Get CHAI review | COMPLETE Vivek Agrawal |
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
A Potential Area of Transmission (PAOT) can be a variety of things:
- It can be in close proximity to a mosquito collection point, larval dipping site or a structure
- It can be within or outside of an operational area
- It can be a distinct thing next to a residential structure
- Identifying PSOTs is part of the Thai protocol and is currently done on hand-drawn maps
- Dropping a point for or editing a potential Source of Transmission should not be restricted by GPS proximity (unlike interaction with other structures)
Requirements
- OVERVIEW: A user should be able to add an icon (possibly similar to the image of Plasmodium Gametocyte below) to the Reveal Android map showing a Potential Area of Transmission (PAOT).
- FORM FIELDS: The user should be able to add a comment to the PAOT form (not mandatory) - maximum string size tbc (2000 chars? this should be the same as other comment fields in Reveal)
specify the type of PAOT from a drop-down (list to be provided - 'Pond, Cave, Forest) (Pedro Pagalday Olivares to confirm this please) - FORM FIELDS: The comment field (task/form) should be editable
- REQUIREDNESS: It is not mandatory to add a PAOT to a focus
- LIFECYCLE: The PAOT will persist across subsequent FI, but should be able to be removed (set to inactive) I.e. they do not expire
- USAGE: The PAOT data should be synced to the Reveal WebUI and be visible in the Web UI maps (high priority)
- USAGE: The PSOT data should be as a line listing reports (to be mocked up) (low priority)
- USAGE: The PAOT should be synced to Biophics in the same way that other tasks are (high priority) - this is where the BVBD will analyse the data
- PLANNING: The PAOT activity will not be part of a plan and no tasks for it will be created, all PSOT will be created ad hoc in the field
- TASK STATUS: The PAOT can be coulored green as soon as it is created, with a status of 'Completed'
- LINKAGE: One focus area can have multiple PAOTs
- LINKAGE: The PAOT is associated to a focus area and not explicitly to an Index Case. This linkage can be assumed through the 1:1 mapping of focus area and index case per plan. However the PAOT is not necessarily related to the index or secondary cases in the focus i.e. it is A a potential area of transmission, not THE potential area of transmission for the cases in the focus at that time.
- EDGE CASE: A PAOT is NEVER another type of structure, and if a structure is identified as a potential source then a PAOT should be added alongside the existing structure
- A potential issue raised is what happens with very large structures (Markets, football fields) as PAOT cannot be dropped on top of this - Vivek confirmed that this was discussed with BVBD and placing a pit next to the structure with a comment is sufficient
Mock-Ups
Adding a PAOT PAOT Form
Views
We anticipate the following views to be impacted on with the creation of this feature:
- Android - Add structure form
- Android - Maps
- Android - New form
- Web - Maps
Justification
- The Thailand BVBD has requested this feature:
- They need to be able to list the PAOT so that they can monitor them and potentially intervene (in active foci).
- It is important to be able to measure the most common PAOT in order to decide on intervention types to implement (inputs into epi research, SOPs and policy)
Dependencies
- Data Dictionary completed
- Icon produced
Notes
- Vivek - purpose: for targeted interventions, could visually see if there is a correlation of infection for more than one focus. they do this on paper at the moment. It is a critical piece of protocol for the Thai team.
- Was this mentioned in the initial first visit? To confirm with Pedro
- Data should be surfaced in web UI and pushed through to Biophics (not for this version though)
- You need to be able to define an area of transmission as part of the focus investigation
Questions
- This feature has been described as a Potential Source of Infection (POI) and a Potential Source of Transmission- which is correct?
- Confirmed by Vivek Agrawal as Potential Area of Transmission (PAOT)
- Was this requirement mentioned during the initial first visit? To confirm with Pedro
Test Case
# | Step | Pass / Fail | Comment |
---|---|---|---|
1 | |||
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
Additional tester comments: |