OpenLMIS documents its major features and functional requirements with user stories and use cases. The user stories are grouped based on functionality to create an epic. Each epic has a defined scope and is slotted for a release. Once development begins, new stories and related technical tasks may be generated as needed to support the functional stories. Visit the Living Product Roadmap for a high-level roadmap of upcoming work.
Overview of Functionality
Currently Available in OpenLMIS
The following is a high-level list of current features available in OpenLMIS version 3. Review the releases schedule to know which releases are past and upcoming (release notes for 2.0.0 - 3.1.2 and post 3.1.2.)
Last updated: after the 3.3 release.
Upcoming Features
The following features are in-progress and potential features for future development.
The list is derived from the product committee, Gap Analysis work (comparing version 3 with eLMIS in Tanzania and Zambia) and requests from implementers. The list is by no means complete and many requested features are detailed in JIRA on the Roadmap Board.
The stock management features (also known as inventory management/control) for a facility/store/location is the on-going accounting of the stock on hand of medical commodities and inventory-able items. Users can record transactions like issues (debit), receipts (credit), stock counts (+/-), and a variety of adjustments (+/-). These features support the Storage Business Process outlined in the CRDM.
The requisition features support users in requesting new stock (based on consumption or estimated need) and approvals to generate an order for fulfillment (see Fulfillment for details). Users can either manually report on the past periods' stock levels or leverage the electronic stock cards from Stock Management to inform the requisition process. When a requisition is approved, it is converted to an order (i.e. a purchase order). These features support the Requisition Business Process outlined in the CRDM.
The initial set of features support the Requisition Business Process and sub activities. The following features support the requesting of new stock by reporting on the period's past stocking information and requesting new stock. As a storeroom manager, I want to submit a requisition and report on my stock levels so that my supervisor(s) can approve and create an order for fulfillment and subsequent delivery. This service specifically contains the features and business logic for the workflow of requisitioning new stock. For a detailed view of the workflow, you can watch a brief recorded demo.
Forecasting and Estimation (3.2.1)
The definition of stock based means that a facility or location is using stock management or managing its inventory with OpenLMIS and the re-order amounts (or requested quantities) are based off the stock movements of the past period (i.e. the electronic stock cards). The first release focuses on a limited scope for vaccines and using Ideal Stock Amounts to calculate the order quantity.
The purpose of this requirement is to improve the following process for Emergency Requisitions by removing the requirement to report on the last period's stocking information, allowing the user to specify what products they want to order.
Supports the ability to view a facilities budget within the requisition workflow and approval process.
The following features support the processes involved in creating, viewing, fulfilling (both internally within OpenLMIS and externally with integrations to an outside ERP) and lastly receiving an order via the proof of delivery. Fulfilling encompasses the identification and preparation of accurate quantities of items packed correctly from store needed for transport by lower level. These features support both the Dispatch and Receive Business Process outlined in the CRDM.
Ability to view orders and export those orders to external systems for fulfillment. Features supporting the external fulfillment process, by which requisitions are fulfilled by an external warehouse outside of OpenLMIS, include:
Accept stock into inventory via an electronic Proof of Delivery (based on the Order but no shipment information)
Orders are created within OpenLMIS from approved requisitions in specific programs. Each order contains a list of products and corresponding Order Quantities. The user reviews the list of orders, selects an order to fulfill, and sets the fill quantities. Once an order is fulfilled a proof of delivery document is printed and sent as part of the shipment.
Improves the Proof of Delivery to connect to stock management.
Aggregate order fulfillment (sometimes called distribution): Grouping and fulfilling orders together to make decisions on fulfillment quantities based on all the orders.
The reporting and analytics vision is to support OpenLMIS users with both routine reporting and ad-hoc analysis.
A small number of routine reports to support with monitoring the requisition reporting rate and key indicators.
Single Sign-on for new reporting stack (3.5)
Some of the following elements can only be configured through csv.
User Management
See Administration Screens to see the outstanding screens and functionality to be built to manage all reference data through the user interface.