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
- Features will be rolled out in phases.
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 | To do before deeming user story "done" | JIRA Tickets |
|---|---|---|---|---|---|---|---|
| 1 | Provide upload file option for annual needs forecast (i.e. needs calculated externally, ISA targets) | Upload ISA or targets into OpenLMIS (the target number of doses at each SDP or location)
| VIMS, SELV/SIIL | MVP | 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? -- Say 100 HF exist in the system and the first upload has ISA for all; next time, you want to update only for 10 HF – do you still upload all or upload only 10? Depends on "template" that is provided to uploader to use. Vidya to Discuss with Brandon Bowersox-Johnson What about viewing all the facilities after uploading? if view option is needed, that's another ticket/story; also discuss with Brandon. Discussion with BBJ on Jul 25: BBJ: does each column need to be a unique ID – for eg instead of saying Balaka Hospital, it would have to be a unique code. So part of the feature should be that the software lets you download a CSV that's a template – so if you go to screen "configure ISA" – one of the things will be CSV template and another is upload a new set of ISAs via upload file function. Template would be a spreadsheet with all the codes and facilities associated with it, product codes, and just the one column for ISA that needs to be filled out. maybe could have previous ISAs and update the new ones.BBJ: we should allow people to do either — upload all 100 but only 10 have changed or only upload 10. The facilities + IDS will be looked at as part of system config so don't need another ticket for that. OPEN QUESTION ON time period and on doses to vials (because of rounding issue) BBJ agrees that there should be a view feature – won't take it too long from programming stand point. So should be "download," "upload," and "view"- so view can be used right away or months later. View can have filter options if you only want to see a product or a particular HF – and can have a total figure at the bottom that updates each time you apply filter. Include a wishlist for how many filters/search options you want. Also said it keep it all in one ticket. | OLMIS-396 - Getting issue details... STATUS OLMIS-2892 - Getting issue details... STATUS OLMIS-2972 - 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. | 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. 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). Discussion with BBJ week of July 25: BBJ says Sam first input, and if she finds any of this tricky then she gets Nick's buy-in. BBJ – they can do it either in the screen or do another download/upload — VS push for download/upload and works the same as the central level. Audit logging – should be part of this work so make this another ticket. (Audit logging for ISA quantity modifications) | Needs a UI experience/mockup Vidya Sampath to reach out to Brandon Bowersox-Johnson to ask who in ISG should be involved in the brainstorm to create this ticket including UI experience Must complete ticket before August 5 | OLMIS-2966 - Getting issue details... STATUS | |
| 3 | Create rights | MVP | Need to discuss how to determine the rights for this. by Program, facility, supervisory node? follow language in other tickets (CCE rights) to create this ticket. One of the rights is edit ISA for own entity/geog area, and the other is right to upload for all HF in country (central level). The former is likely by program, and supervisory node. (list RIVO and DIVO as examples in the ticket for edits and central level has for whole country). | Must complete ticket before August 5 | OLMIS-2890 - Getting issue details... STATUS OLMIS-2891 - Getting issue details... STATUS | ||
| 4 | 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 |
| |||
| 5 | 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
| Next |
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. 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 | ||||
| 6 | Aggregate forecasted product needs for campaigns | Needs clarification | |||||
| 7 | Enter forecasted product needs for campaigns → enter SDP microplan forecast for campaign into OpenLMIS campaign screen | Needs clarification | |||||
| 8 | 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 |  | |||
| 9 | 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. |
| ||||
| 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 | Status | |
|---|---|---|---|
| 1 | There are multiple ways countries look at the frequency for the ISA amoungs. Either we need to match these numbers to the resupply schedule or we can allow annual numbers which we divide by 12 or allow for annual numbers we divide by 24. We need to come up with a way to determine what or how we define time period for the ISA targets. | ||
| 2 | Open Question: Is the ISA number, which is uploaded, in doses or vials? We can calculate either way but need to make a call. | Doses (because the way in which the ISA is calculated gives you an output which is dosage | Closed |
| 3 | Vidya – look into how the re-supply works in VIMS across multiple levels (if multiple resupply periods exist) | ||
| 4 | Talk to SME about need for story #1 and story #2 and if it does make sense to have both (talk to them once the mock-ups are done to walk them through both stories via UI examples) |
Out of Scope
Out of scope for this feature OR potentially saving for future development.