Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...



Responsible Person:
Other parties to review/input:
FYI:
Targeted release date:
Jira Legacy
serverSystem JIRA
columnsfixversions
serverId3420e60a-4e6f-3f80-8335-059c22bb40aa
keyRVL-104
Jira Status:
Jira Legacy
serverSystem JIRA
columnsstatus
serverId3420e60a-4e6f-3f80-8335-059c22bb40aa
keyRVL-104

Process

  1. Prepare rough business analysis/reqs doc (Pierre Dane: IN PROGRESS)
  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

The responsible person then owns this feature from scoping, to tracking development by Ona and providing clarifications if needed, to testing and sign off.  

Definitions

A Potential Source of Transmission can be a variety of things:

...

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

Generic Scoping Steps

  1. Prepare rough business analysis/reqs doc (Pierre Dane: IN PROGRESS)
  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

...

Requirements

  1. A user should be able to add an icon (possibly similar to image 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 specify the type of PSOT from a drop-down (list to be provided - 'Pond, Cave, Forest) (Pedro Pagalday Olivares to confirm this please)
  3. 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 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. 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

...