Table Of Contents
| Table of Contents |
|---|
...
| # | Step | Status |
|---|---|---|
| 1 | Responsible prepares rough business analysis/reqs doc | COMPLETE Pierre Dane |
| 2 | Get CHAI review | COMPLETE Vivek Agrawal |
| 3 | Get Akros Review | COMPLETE Christina Riley |
| 4 | Get Ona feedback | COMPLETE Craig Appl |
| 5 | Responsible - 1 iteration for feedback | Pierre Dane, please perform the following:
|
| 6 | Ona sign off | |
| 7 | Ona tech spec scoping | |
| 8 | Ona LOE | |
| 9 | Ona scheduling |
...
- 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 Craig Appl - can you verify that each time this data is saved that a new form is submitted to the server (same data workflow as mosq collection point & larval dipping).
- This is the date that the PAOT was recorded - this field is mandatory. Each time a PAOT is identified during an FI this data should be recorded.
- We should be able to see a historical view of the comments & dates recorded as a PAOT in the web UI & supersets.
- 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 PAOT 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 activity
- TASK STATUS: The PAOT can be coulored green as soon as yellow when it is created, with a status :
- Once selected and the data field is filled out, the color will turn to green for 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
...