[SELV/SIIL] Distribution/Re-Supply Domain: Record Data on Amount Distributed

Target release	Vaccine Module
Epic	Distribution/Re-Supply Domain
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

#

Title

User Story

Label

Importance

Notes

1

Record product inventory inside the CCE during my distribution visit

As a FC/logistician/distributor, I arrive at the facility and I want to record details about products in the CCE as my part of my visit so that I can capture the amount on hand in the CCE and the amount I see is discarded in the discard bin and the amount I dropped off into the CCE so that there is a clear inventory of products on day of visit.

SELV/SIIL

Must Have

Open – Vidya Sampath check back with Moz team with stock summary form (EPI Use) usage outside of SELV and if any stock decisions are made by the DPS or PAV MISAU using this data. Have their response inform open question to the group

2

Record reason for spoiled products during my distribution visit

As a FC/logistician/distributor, I want to record the reason for spoilage of the products I found in the discard bin on day of visit so that I can capture reasons for wastage. For this, I need a drop down menu providing me reason options such as:

Heat Exposure (VVM Indicator)
Freeze Exposure (Shake Test)
Broken/damaged vial
Expired

Must have

Open question for group:

Is it enough to give # of vials of a product that expired, or list expiry date on each vial discarded? (VS - think this is nice to have, most folks ask for this data but do not actually do anything with it).
What level of detail is needed for wastage? Just closed vial wastage pertaining to VVM and freezing?
Note – this is only wastage found on day of visit; we also need to record wastage as part of SM domain.

3

View forecasted amount in a column alongside where distribution amounts are recorded

As a FC/logistician/distributor, I want the forecasted amount for that facility and time period, displayed in a column so that I have a visual reminder of how much was forecasted as the need for that facility.

SELV, SIIL

Must have

There are two options here:

Simple – just display the amount as currently exists in SELV and SIIL

Nice to have - the screen displays how much you over or under supplied based on the total (SOH - spoiled + delivered)

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