...
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 Responsible prepares rough business analysis/reqs doc | IN PROGRESS - Pierre Dane |
2 | Get CHAI review | |
3 | Get Akros Review | |
4 | Get Ona feedback | |
5 | One Responsible - 1 iteration for feedback | |
6 | Ona sign off | |
7 | Ona tech spec scoping | |
8 | Ona LOE | |
9 | Ona scheduling |
...
- 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 Source of Transmission (PSOT).
- FORM FIELDS: The user should be able to add a comment to the 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) - FORM FIELDS: The comment field (task/form) should be editable
- 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 USAGE: 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)
- USAGE: 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
- 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
- PLANNING: The PSOT 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 PSOT can be coulored green as soon as it is created, with a status of 'Completed'
- LINKAGE: The PSOT 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 PSOT is not necessarily related to the index or secondary cases in the focus i.e. it is A a potential source of infection, not THE potential source of infection for the cases in the focus at that time.
- EDGE CASE: 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
- 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
Mock-Ups
.
Views
We anticipate the following views to be impacted on with the creation of this feature:
...