Vision
- The OpenLMIS vision is to support a core set of LMIS business processes to be accessible via a web or mobile/tablet interface
- OpenLMIS offers a robust set of APIs which enable a variety of mobile tools (CommCare Supply, ODK, OpenSRP, Medic Mobile, etc.) to interface with OpenLMIS. Countries/implementors can select the mobile application of their choice.
- OpenLMIS supports supply chain management processes down to the facility level.
- Can be quickly deployed "as is" without software development, including ability to be configured to match the business requirements of a country (how achievable is this? need exploration)
- Meta-data alignment
- Product Master (Commodity Types, Trade Items, )
- Approved Products, Min and Max
- Facility list (FHIR Location with GLN)
- Stock Adjustment Reasons
- Stock origin and destination lists (facilities approved to be)
- User login
- User Auth and RBAC (online to authenticate, RBAC cached. No network needed until network connection shows credential to be unauthenticated)
- Direct to digital stock management (Stock on Hand by Program):
- Physical Inventory (aka Stock Take), with losses and adjustment reasons
- Losses and Adjustments (wastage, consumption, etc)
- Issue Stock (stock out)
- Receive Stock (stock in)
- Receive Stock using a VVM
- Receive stock from a shipment (POD)
- Receive stock from a shipment (POD) using a SSCC barcode (code 128)
- Record losses and adjustments using a UDI barcode (data matrix)
- Issue stock (picked with UDI barcodes) and packed into a box where we print a SSCC barcode
- Requesting new Stock
- Stock-based, periodic, Requisition (from Stock on Hand and a calculated stock qty)
- Regular periodic Requisition (leverage Stock-based physical inventory, support fields such as: stock out days, # of new patients)
- Receiving ASN/Despatch advice of a shipment being processed.
- Requisition Authorize
- Requisition Approval
- Work with (interop tbd) Program Data capture application to visualize programmatic data capture requirement as part of regular period requisition
- Fulfilling an Order
- Fulfill an Order (Pick, Pack, Ship)
- Print a SSCC barcode (code 128) for the shipment
- For implementations wanting a tailored user experience (i.e. match current country paper forms), can be customized(?) by a software developer
- Implementation branding/themeing (implementer may brand/theme app without development cycle - ie through app settings)
- Stock recall
- Stock instance fraud detection (through interop with service providers - Optel?)
MVP and Rough bucketing of epics:
Deliverable / epic | Requirements | Value description |
---|
MVP | 1 through 4a. Exclude 2d. Include 5a. | Mobile app supporting last-mile physical inventory incl recording data on KPIs for wastage and consumption. Replenishment process supported by stock-based requisitioning using configured re-supply calculations. |
Daily stock transactions | 4b through f | Better mobile use of daily stock movements and better upstream visibility - better data for decision making. (presumes internet infrastructure for the timeliness of that data for decision making) |
Fulfill and Receive Orders using SSCC barcodes | 6 and 4g | Fullfill orders, print SSCC barcode label, receive shipment into inventory quickly by scanning SSCC barcode label. |
WIP |
|
|
|
|
|
Key Points for Consideration
Current Plans for Integration
Evaluating Options
| Evaluation Criteria | Option 1 | Option 2 | Option 3 |
---|
1 | Performance |
|
|
|
2 | OpenLMIS community Maintainability |
|
|
|
3 | Implementer Maintainability |
|
|
|
4 | Reusability |
|
|
|