Target release	Vaccine Module
Epic	Distribution/Re-Supply
Document status	DRAFT
Document owner	Vidya Sampath
Technical Lead	Technical Lead who reviews or supports document

Goals/Scope

- - - In push (allocation) based supply chains, vaccines are directly delivered to the level below instead of the level going to pick up the vaccines from the level above. This page captured the functionality requests for the personas responsible for distributing and for those receiving the distribution.
    - In push based SCs, users will input data using this functionality when they are in the middle of their distribution workflow at the storage point receiving this distribution.

Background

Are there any country specific features that should be noted? Who are the personas? Who are the users that will be interacting with this functionality? What are their challenges, responsibilities, and level of connectivity? These personas are intended to be representative archetypes of the key stakeholders who will participate in theses workflows/scenarios.

Personas involved:

Intermediate Level Logistician/Distributor/Field Coordinator ( responsible for actual distribution of products and for inputing the data that this feature functionality will serve)

Assumptions

What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this features from a tablet).

User Stories

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

#

Title

User Story

Label

Importance

Notes

1

Distribution Visit Observations

As a FC/distributor/logistician, I want to record information ("observations") from my visit to a drop-off facility/district depot so that a record exists with my distribution visit details. I want to record the following:

Facility I am visiting
Date of visit
If I did not visit, the reason for doing so in the form of multiple choice options (pre-determined with EPI program in my country i.e. CONFIGURABLE BY ADMIN)
My name and title
The receiver at the drop-off location's name and title confirming my visit

SELV/SIIL

Must Have

2

Diagrams

Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.

Dependencies

Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.

Description	Link
Name of story or release	Link to JIRA

Open Questions

Initial communication between stakeholders and the development team to help understand scope and estimates.

Below is a list of questions to be addressed as a result of this requirements document:

#	Question	Outcome	Status
1	(e.g. How we make users more aware of this feature?)	Communicate the decision reached	Open, In Progress, Closed, and date of closure

Out of Scope

- List the features discussed which are out of scope or might be revisited in a later release.

Save