Goals
- The goals of this requirements page is to document the user stories specifically related to the "X" feature.
Background
insert discussions during the workshop which are relevant to note. List participants.
Assumptions
- insert
User Stories
List out the user stories under the activity. Put the "next up" under the Out of Scope section.
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
| 1 | Centralized entry of ISA targets | Enter ISA into OpenLMIS (doses at each SDP)
Notes from Vidya: One issue to be mindful of is mapping spellings of each entity in the upload file to the way that entity is spelt within the OpenLMIS system. We see this problem constantly with the CT integration in SELV - the way CT spells the facility and district names sometimes is one or two characters different from how SELV spells it and the whole thing breaks down. Is there a best practice mitigation strategy for this that OpenLMIS uses in other places? | VIMS, SELV/SIIL | MVP | OLMIS-396 - Getting issue details... STATUS | |
| 2 | Modify allocated quantities | As a DIVO, I want to review (and edit) the quantity allocated to me to ensure it will meet demand in my geographical area of responsibility. From VIMS below – not about editing forecasted quantities but about editing the allocated population target #s for my area since those are used in the estimation for quantities for my area: As A RIVO/National, I would like to be able to upload/update the population data for my districts Acceptance Criteria
| MVP | Needs clarification quantities calculated in vials – note from Vidya – I've actually seen this calculated in doses and then converted to vials depending on which manufacturer's antigen is being used at that time in the country, since each manufacturer has a different dose/vial ratio.
Note: Note Finalize button just prevents editing the estimates by user with data entry role. "Unlock For Editing" needs a special permission to unlock for editing Vidya note – the screen shot from VIMS shows that a user has to manually enter the target population for each type (pregnant women, Children U5, Adolescents, etc). In SELV/SIIL, it's just a % of the catchment population for that HF that's assumed is children/pregnant women, etc so the system auto-calculates it. | ||
| 3 | WHO formula calculator | As a Central EPI, I want to use WHO formula to calculate my vaccine needs estimation for all EPI products (vaccines, diluents, syringes, waste management) so that I can forecast my product needs for the year. Below are the steps for how it is currently done in SELV, along with screen shots in the Notes column: Step 1 - the names of products should be uploaded onto the system Step 2 - once the products names are available to the admin user, the admin user selects one product at a time to configure the product ISA Step 3 - the WHO calculator comes up on the screen and the admin user enters the relevant figures for that particular type of product (wastage factor, target %, etc are different for each antigen). | Next | allow demographic data driven targets and provide coverage data.
| ||
| 4 | Aggregate forecasted product needs for campaigns | Needs clarification | ||||
| 5 | Enter forecasted product needs for campaigns → enter SDP microplan forecast for campaign into OpenLMIS campaign screen | Needs clarification | ||||
| 6 | Display the formula used for calculation to the viewer | As a Program Supervisor, I want to see the formula used for calculation of product needs (regardless of whether it’s WHO or a custom formula for my country) so that I have a visual confirmation that the system is performing the calculation as I understand it and which the EPI program has determined is the one to use. Screen shot from SELV attached | SELV/SIIL |
| ||
| 7 | Provide a calculation demo to viewer to confirm accuracy of calculation | As a DIVO, I want a space where I can input my vaccination coverage target figure for a particular antigen and have the system display what the forecasted need in doses/vials is so that I have a visual confirmation that the system is accurately calculating the need as I understand it and which the EPI program has determined is the one to use. | I think 6 and 7 are the same? | |||
| 8 | Provide all levels an option to correct annual needs forecast (i.e instead of set annual population targets) | As a Central Vaccine Logistics Personnel, I want to address the issue of my target population being wrong due to poor census estimates. Instead, I want to provide all levels a chance to edit the annual need based on census target and use that to drive forecasting for all EPI products (vaccines, diluents, syringes) for the year | Needs clarification with story #2 - I think it's the same – this provides a better explanation/justification for why it's needed | |||
| 9 | Provide upload file option for annual needs forecast (i.e. needs calculated externally) | In Mozambique, we have heard requests from certain provinces that state that the MoH forecast for their specific province is incorrect. They want the ability to override the ministry-forecast for their province by being allowed to edit their forecast (example – override wastage rate for BCG from 50% set by MoH to 20% for their province, or change catchment population locally for few HCs that they think is incorrect, etc). | ? maybe MVP | ISn't this related to Story #1? | ||
| 10 | Provision of extension points to countries to customize needs estimation on their own | For those countries that want to use their own method of calculating need that does not match global standards, OpenLMIS will provide an extension point to the system such that a country can build and install an extension to apply their own custom calculation within OpenLMIS. | ? maybe MVP |
Diagrams
Steps
- Administrator needs a way to upload annual targets to each entity (facility and SDP which are not managing stock in OpenLMIS)
Dependencies
insert
Open Questions
Below is a list of questions to be addressed as a result of the vaccine workshop:
| Question | Outcome | |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 |
Out of Scope
Out of scope for this feature OR potentially saving for future development.