This document defines the software requirements for the distribution point features for Reveal. A distribution point is a centralized location where individuals meet to receive care. The primary workflows are funded under a grant for Neglected Tropical Diseases (NTDs) which focuses on distributing medication among children who are attending schools in Eswatini. The functional requirements are outlined on NTD School Workflow and the data dictionary. This document applies those functional requirements into the Reveal technical architecture.

...

1. How do we roll back these items in the event someone messes up?

2. We need to define the logic behind generating

3. We need to define the error handling.

4. (Business question) Users don’t have a view into all of the entities that are registered to a distribution point. Therefore, they have no idea if their list was uploaded correctly. How should we mitigate this?

   1. In other words, how will we handle mistakes when a user uploads information that they don’t want to be there. What’s the life cycle we should create to remove the likelihood of duplicates?

      1. We need to come up with unique id generation so that we can

5. We are building a bulk event generator in this CSV upload process. It would be valuable to support JSON format as well as CSV.

6. We need to determine if we should have different variations of the template and optional fields so that we don’t need different templates here.

7. Consider removing the upload after the plan is generated.

8. How will we provide a list of children to the user.

OpenSRP Web UI

We need to develop the following features in the OpenSRP Web UI in order to deliver the features above.

...

• [Craig needs to complete this section]

• Outstanding questions on this section:

  • Should the plan account for adverse event reporting in some way? How will we do counts of adverse events in the reports by creating a complete task when there’s an adverse event reported?

Outstanding Items on the Plan Definition and Task Changes

...

• Users should not have the capability to download large lists that contain personally identifiable information about the clients.

  • Access to download rosters will, at maximum, provide identifiers that can be linked to people registered in the system.

• All uploads need to be validated to include the following:

  • Valid CSV architecture with UTF-8 encoding

  • Individual fields are parsed and validated to remove exposure to SQL injection threats

  • Individual fields are parsed and validated to remove exposure to cross-site scripting threats

  • (We probably need to add more here)

Things to be discussed from scoping so far

...