B. Enter Stock Data

"DONE" means this functionality is already built into OpenLMIS 3.1. All other items not marked are still needed for the Vaccines modules.

Enter Stock Data MVP
DONE: Record a physical stock count by product (source: ES1)
Record VVM status with physical stock count (recording VVM status should be optional, not required) (source: RE1)
DONE: Record a stock adjustment (source: ES2)
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)
Record VVM status with ad-hoc receipt/issue (optional, not required)
DONE: Record lots (source: ES6)
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)
DONE: Initiate and submit a requisition (source: ES7)
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 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 As a IHW/ILL, I want the ability to set a date in the past for my inventory or stock movement so that I can capture historical/past events into the electronic record (including capturing events that happened during an internet or electrical outage). (We want to do this without complex configuration, EG there is no need to allow/deny for different user groups or for different date cut-offs such as 1-month or 6-month limits.)
Next
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!
Not needed
Facility-within-a-Facility (If we don't build this, the work-arounds are acceptable.)

Sources:

Priorities came from the final MVP whiteboard at the Vaccines Workshop: /wiki/spaces/OP/pages/113054114
Most of these user stories sourced and numbered above came from pre-workshop research here: Stock Management Domain Parent Page