...

• 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)

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 the source of infection as part of the focus investigation

Requirements

1. 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). 
2. 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)
3. LIFECYCLE: The PSOT will persist across subsequent FI, but should be able to be removed (set to inactive) I.e. they do not expire
4. The comment field (task/form) should be editable 
5. The PSOT should be synced to the Reveal WebUI and be available in Superset
   1. Visible in maps (Android and WebUI)
   2. Available as a line listing reports (to be mocked up)
6. The PSOT should be synced to Biophics in the same way that other tasks are (in a future release)
7. 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
   1. 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
8. The PSOT activity will not be part of a plan and no tasks for it will be created
9. The PSOT can be coulored green as soon as it is created, with a status of 'Completed'
10. 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.

Mock-Ups

Views

We anticipate the following views to be impacted on with the creation of this feature:

...

1. Data Dictionary completed
2. 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 the source of infection as part of the focus investigation

Questions

1. This feature has been described as a Potential Source of Infection (POI) and a Potential Source of Transmission- which is correct?
2. Was this requirement mentioned during the initial first visit? To confirm with Pedro

Test Case

...