...
| Page Properties | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals
- Add on features features to stockmanagement-1.0.0-beta (ref-distro-3.1.0) that are needed for vaccines.
Background
OpenLMIS version 3.1 will deliver the following features within .0 previously delivered an initial beta of stock management. See Stock Management for the detailed list of features.
Assumptions
- insert
User Stories
...
- With the addition of the features below, the stock management module will become "vaccines capable". It can still be used for non-vaccine medical commodities simultaneously as well.
User Stories
| # | Title | User Story | LabelImportance | Notes | JIRA Tickets | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Record VVM with physical inventory | Record VVM status with physical stock count (recording VVM status should be optional, not required) (source: RE1) | MVP | |||||||
| 2 | Record VVM with adjustment | Record VVM status with any adjustment (optional, not required) As an Immunization Health Worker/Intermediate Level Logistician, I want the optional ability to capture a VVM status when I record an adjustment, so that my I have the visibility to prioritize product with a worsening VVM status. | MVP | |||||||
| 3 | Record VVM with ad-hoc receipt/issue | Record VVM status with ad-hoc receipt/issue (optional, not required) | MVP | |||||||
| 4 | Program specific adjustment reasons for adjustments | As a DIVO, I would like to indicate vaccine specific wastage reasons when making adjustments to my stock levels so that I can accurately track/record wastage to inform my ordering and resupplying. For example, vaccines would like specific wastage reasons. Record wastage quantities and reasons (source: ES3) (VIMS) | MVP | Open Question: How do we quantify open vial wastage (because you cannot count how many doses were wasted)? In VIMS we capture the count of open vials. | ||||||
| 4 | Record VVM status with ad-hoc receipt/issue | Record VVM status with ad-hoc receipt/issue (optional, not required) | MVP | 5 | 5 | |||||
| 6 | Receive Re-supply | As an Immunization Health Worker/Intermediate Level Logistician, I want to receive and record a delivery with an optional VVM status, so that my stock record is accurate. (Connects to Re-supply domain) Details: Connect the POD to stock management. | MVP | |||||||
| 67 | BIN Bin cards for CCE equipment | Track CCE equipment location with my stock inventories and movements — expand the definition of stock card identities to act as a Bin card based on CCE equipment location. As a IHW/ILL, I want my stock cards to be differentiated by CCE equipment location—in other words I want to do a physical inventory count or record any adjustment or movement for a specific CCE fridge/cooler locationequipment, so that I can link the when a CCE equipment failure event data happens I can connect that to the specific quantities of stock impacted. | MVP | Relates to CCE capacity. (Connects to CCE domain) | ||||||
| 78 | Correct stock movements | Correct stock movements See Correcting stock movements for the approved proposal (using Reversal approach) | Next | ?Up for discussion. | 8(Note: This was not raised for discussion at the Copenhagen 2017 workshop, but we have identified that it is important for an accurate stock record.) | |||||
| 9 | Add lots at any facility (not centrally managed) | Users need the ability to record a Lot Code and Expiration Date during any stock event (inventory, adjustment, ad-hoc receipt/issue)—even if that Lot is not yet known in the centrally managed Lot list. (modified from ES5) | Next | Brandon Bowersox-Johnson, this is a substantial amount of work. Let's discuss if this a MUST for the MVP. | 9(Note: This was originally in the MVP at the Copenhagen 2017 workshop.) | |||||
| 10 | Generate issue voucher | As an Issuer of Stock, I would like the system to automatically generate Issue voucher number to my Issue voucher so that I can keep track of the issues I have made to my recipients (and so that they can receive based on an issue voucher instead of manually entering quantities). And so that I have an audit trail to and to save time and reduce errors. (source: RE4—includes lots of details and links to info) | Next | Got 5 votes! | ||||||
| 1011 | Supporting GLNs / Facility-within-a-Facility | Facility-within-a-Facility | Next | (If we don't build this, the work-arounds are acceptable.) | GLNs may be a separate thing, not facility-within-a-facility. We could easily add a GLN field without addressing facility-within-a-facility needs. | |||||
| 12 | Schedule for physical stock count | Set a schedule to force/prompt a physical inventory | Next | (got zero dot votes) | ||||||
| 13 | Kits, diluents, syringes | Kits, diluents, syringes (The group discussed how you might think it would be nice if these were automatically ordered, but really that is not practical and not important for vaccines. Sometimes they are ordered on a different schedule. The syringes and other items should have their own min and max quantities and they should be forecast and ordered so they do not run out of stock. Overall, it would be hard for software to automate this for all country situations, and it should be handled by SOPs outside the software.) | Not needed |
Sources:
- Priorities came from the final MVP whiteboard at the Vaccines Workshop: /wiki/spaces/OP/pages/113054114. Note that the Dependencies & Configuration stories have been moved here into the Enter Stock Data step.
- Most of these user stories sourced and numbered above came from pre-workshop research here: Stock Management Domain Parent Page
Diagrams
none
Dependencies
insertMany dependencies on Reference Data (existing) and CCE (new/coming soon). Originally, dependencies had its own page in this domain, see the history of A. Dependencies & Configuration.
Open Questions
Below is a list of questions to be addressed as a result of the vaccine workshop:
| Question | Outcome | |
|---|---|---|
| 1 | Open Question:Is using Stock Management required for some or all facilities who order and receive vaccines? Will Forecasting & Estimation or Re-Supply domains require that certain facilities (intermediate nodes or SDPs?) use stock management? Mary Jo Kochendorfer (Deactivated) I think we need to discuss. | |
| 2 | How much data entry burden is story #6? We suggest making it optional so country SOPs can choose. | |
| 23 | Story #10 Terminology issue to try to bet a global agreement on; an "ad-hoc issue" is called a transfer many places. A transfer is lateral (to peers at the same level). An issue is down the supply chain. But these terms may not be universal. | |
| 34 |
Out of Scope
Out of scope for this feature OR potentially saving for future development.
Initial documentation by Brandon Bowersox-Johnson below. Once reviewed, I suggest removing it.
"DONE" means this functionality is already built into OpenLMIS 3.1. All other items not marked are still needed for the Vaccines modules.
...
Record VVM status with any adjustment (optional, not required)
As an Immunization Health Worker/Intermediate Level Logistician, I want the optional ability to capture a VVM status when I record an adjustment, so that my I have the visibility to prioritize product with a worsening VVM status.
...
Record wastage quantities and reasons
(source: ES3)
Open Question: How do we quantify open vial wastage (because you cannot count how many doses were wasted)? In VIMS we capture the count of open vials.
...
DONE: Record ad-hoc receipt/issue
(source: ES4)
...
Add lots locally
Users need the ability to record a Lot Code and Expiration Date during any stock event (inventory, adjustment, ad-hoc receipt/issue)—even if that Lot is not yet known in the centrally managed Lot list.
(modified from ES5)
...
Receive Re-supply
As an Immunization Health Worker/Intermediate Level Logistician, I want to receive and record a delivery with an optional VVM status, so that my stock record is accurate.
(Connects to Re-supply domain)
...
Track CCE equipment location with my stock inventories and movements — expand the definition of stock card identities
DONE- As a IHW/ILL, I want my stock cards to be differentiated by CCE equipment location—in other words I want to do a physical inventory count or record any adjustment or movement for a specific CCE fridge/cooler location, so that I can link the CCE equipment failure event data to the specific quantities of stock impacted.
(Connects to CCE domain)
Open Question: How much data entry burden is this? We suggest making it optional so country SOPs can choose.
Enter historical stock activities
...
.
...
Generate issue voucher
As an Issuer of Stock, I would like the system to automatically generate Issue voucher number to my Issue voucher so that I can keep track of the issues I have made to my recipients (and so that they can receive based on an issue voucher instead of manually entering quantities). And so that I have an audit trail to and to save time and reduce errors.
(source: RE4—includes lots of details and links to info)
Open Question: Terminology issue to try to bet a global agreement on; an "ad-hoc issue" is called a transfer many places. A transfer is lateral (to peers at the same level). An issue is down the supply chain. But these terms may not be universal.
Got 5 votes!
...
Facility-within-a-Facility
...