Page Comparison

Table Of Contents

...

...

1. OVERVIEW: A user should be able to add an icon (TBD) to the Reveal Android map showing a Potential Area of Transmission (PAOT). 
2. 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)
3. FORM FIELDS:
   1. 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).
   2. The date that the PAOT was recorded should be recorded and displayed on the card view
   3. We should be able to see a historical view of the comments & dates recorded as a PAOT in the web UI & supersets.(low priority)
4. REQUIREDNESS: It is not mandatory to add a PAOT to a focus
5. LIFECYCLE: The PAOT will persist across subsequent FI, but should be able to be removed (set to inactive) I.e. they do not expire
6. LIFECYCLE: The addition of a  PAOT to a focus area will, in general, be a .once off task performed during the first visit
7. USAGE: The PAOT data should be synced to the Reveal WebUI and be visible in the Web UI maps (high priority)
8. USAGE: The PAOT data should be as a line listing reports (to be mocked up) (low priority) - the comment should display when clicking the PAOT icon in the WebUI
9. 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
10. PLANNING: The PAOT activity will not be part of a plan activity ←Changed this on 18 July | We will generate plan actions and goals to visit any existing PAOT and update the information in the system.
11. TASK STATUS: The PAOT can be coulored yellow when it is created:
    1. Once selected and the comment field is filled out, the color will turn to green for status of 'Completed'.
12. LINKAGE: One focus area can have multiple PAOTs
13. 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.
14. 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
    1. 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

...