|
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.
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 | Definition | Label | Importance | Notes |
---|---|---|---|---|---|---|
1 | Forecast Accuracy/ Forecast Demand Ratio | As (multiple users), I want to see the Forecast Demand Ratio in my district/province/country so that I can better understand amount used versus forcasted for the same time period to inform future needs estimates | Ratio of actual usage by product during a particular period compared to the forecasted usage for the same period. Usage includes vials opened or administered and closed vial wastage but not quantities ordered to keep the buffer stock. | DISC | Must Have |
Summary: Of all the doses that you forecasted for a particular vaccine in a time period, what was consumed and what was wasted? Info on wastage is based on whatever consumption reporting is in place. To make it more accurate and not base consumption just on "doses used," (= doses given + wastage) doses actually given out can be captured from HMIS (DHIS2) |
KPI | Calculation | Data Needed | Data Sources |
---|---|---|---|
Forecast Demand Ratio | Forecasted demand ratio = (doses consumed and wasted per product) / (doses forecasted per product) | Forecasted demand/usage or vaccination targets by product. Actual consumption or administration by product. Actual wastage (vials opened and closed vials discarded) by product. | Monthly immunization reports. Micro plans and/or MOH policies for targets. Stock ledgers/stock cards. |
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.
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 |
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 | How do we handle consumption? Issues from the fridge or distinguish between wastage and shots in the arm? | Does this KPI need to be viewed within OpenLMIS or within DHIS2? |