Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Target releaseVaccine Module
EpicStock Management
Document status
DRAFT
Document ownerRachel Powers
Technical Lead

Goals/Scope

This functionality seeks to provide users of the system a way to keep track of product and conduct stock management through an electronic stock card. This should captures movements in and out of stock, as well at reasons for stockout and other relevant information. Successful acceptance of this functionality would involve the following:

Enter vaccine stock data, capture stock movements (amount, history, received stock.) The electronic stock card feature is used to mirror the physical cards that sit in storeroom bins and serve as a log of all past ins and outs for each commodity in the storeroom. Each stock card should contains all transactions for each batch of the commodity.

Background

Effective vaccine management requires accurate stock management information in order to track stock levels and ultimately using the information to predict and avoid stockouts.

Forecasting/Needs estimation can be calculated using:

    • Configure stock card template for UI viewing
    • Conduct a physical stock count on a schedule
    • Track ins/outs of stock
      • Transfer in/out (to/from a facility within OpenLMIS and out)
      • Adjustments
    • View stock cards and stock on hand
    • Historical movements/corrections
    • Notifications on low stock

Assumptions

User Stories

#TitleUser StoryLabelImportanceNotes
1

Configure fields on the electronic stock card

As an OpenLMIS implementer, I want to set-up the stock card to specify which fields to display, the name of each field and the order of the fields so that the stock card is easy to navigate and relevant to OpenLMIS users in my implementation managing their stock at a facility.


OLMIS-706


SIIL


Must Have
  • For each Program-Facility Type combination, the following fields are available to choose from when designing a stock card template:
    (Header Options)

    • Facility Name (required)
    • Product name (required)
    • Packsize (optional)
    • Program (required) -
    • Donor (optional) - text string
    • Unit of issue (required) - dispensing unit
    • Stock on Hand (required) - same as balance and is calculated based on the beginning balance, issued, received, and adjustments. see SOH for requisitions. If needed we may need to make separate sub tasks or tickets to break this out.
    • Max Months of Stock: Source referencedata maxmonthsofstock and rounding rules (optional)  OLMIS-887 DONE
    • Min Months of Stock (optional)  OLMIS-978 TO DO
2Create electronic stock cards for a facility

As a storeroom manager, I want to see electronic stock cards for all my products when my facility is set up so I can begin tracking stock movements at my facility


OLMIS-1431

SIILMust Have

1. When implementer initially configures the master product list and associates products to facility types, a blank electronic stock card is generated for all of the facility approved products.

  • Whatever information - such as product name, program, etc. - is available from the product list should be pre-populated. Everything else should be blank.

2. When a new product is added to a facility's product list, a blank electronic stock card is created for the product

  • Whatever information - such as product name, program, etc. - is available from the product list should be pre-populated. Everything else should be blank.

3. SOH for the product is set as NULL (not 0).

  • Note: Storeroom manager will likely do a physical stock count for all products to update SOH. Till this is done, SOH should be NULL
  • Avoid setting SOH = 0 since this will trigger low stock/stock out notifications (  OLMIS-1430 TO DO ) and skew any reports on SOH












Diagrams

Dependencies

DescriptionLink


Open Questions

Below is a list of questions to be addressed as a result of this requirements document:

#QuestionOutcomeStatus
1

2


3


Out of Scope



  • No labels