Table of Contents |
---|
Scoping Details | |
---|---|
Responsible Person: | |
Other parties to review/input: |
FYI: |
Targeted release date: |
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
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 | Prepare rough business analysis/reqs doc |
...
IN PROGRESS - Pierre Dane |
...
2 | Get CHAI review | |
3 | Get Akros Review | |
4 | Get Ona feedback | |
5 | One iteration | |
6 | Ona sign off | |
7 | Ona tech spec scoping | |
8 | Ona LOE | |
9 | Ona scheduling |
...
Definitions
A Potential Source of Transmission can be a variety of things:
- It can be associated with in close proximity to a mosquito collection point or , 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
- This 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)
...
- 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 webUI web UI and pushed through to Biophics (not for this version though)
- You need to be able to define the source of infection as part of the focus investigation
...
- 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 Source of Transmission (PSOT).
- The user should be able to add a comment to the PSOT PSOT form
specify the type of PSOT from a drop-down (list to be provided - 'Pond, Cave, Forest) (Pedro Pagalday Olivares to confirm this please) - LIFECYCLE: The PSOT will persist across subsequent FI, but should be able to be removed (set to inactive) I.e. they do not expire
- The comment field (task/form) should be editable
- The PSOT should be synced to the Reveal WebUI and be available in Superset
- Visible in maps (Android and WebUI)
- Available as a line listing reports (to be mocked up)
- The PSOT should be synced to Biophics in the same way that other tasks are (in a future release)
- A PSOT is NEVER another type of structure, and if a structure is identified as a potential source then a PSOT should be added alongside the existing structure
- Potential A potential issue raised is what happens with very large structures (Markets, football fields) as PSOT 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
- The PSOT activity will not be part of a plan and no tasks for it will be created
- The PSOT can be coulored green as soon as it is created, with a status of 'Completed'
Mock-Ups
Views
We anticipate the following views to be impacted on with the creation of this feature:
...
- The Thailand BVBD has requested this feature:
- They need to be able to list the PSOT so that they can monitor them and potentially intervene (in active foci).
- It is important to be able to measure the most common PSOT in order to decide on intervention types to implement (inputs into epi research, SOPs and policy)
...
Dependencies
- Data Dictionary completed
- Icon produced
Questions
- This feature has been described as a Potential Source of Infection (POI) and a Potential Source of Transmission- which is correct?
Test Case
# | Step | Pass / Fail | Comment |
---|---|---|---|
1 | |||
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
Additional tester comments: |
...