Page Comparison

...

...

Reference Mobile Application -

...

Requirements

...

Supports collection of routine LMIS data across multiple programs (i.e. 10-20 data points for 100+ commodities) via an intuitive, easy to use interface

...

:

...

...

Additional items on the mobile roadmap include informed push, and delivery/POD (these may be separate apps)

...

Operates offline and online

1. 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)
2. Meta-data alignment
   1. Product Master (Commodity Types, Trade Items, GLN)
   2. Approved Products, Min and Max
   3. Facility list (FHIR Location with GLN)
   4. Stock Adjustment Reasons
   5. Stock origin and destination lists (facilities approved to be)
3. User login
   1. User Auth and RBAC (online to authenticate, RBAC cached.  No network needed until network connection shows credential to be unauthenticated)
4. Direct to digital stock management (Stock on Hand by Program):
   
   1. Physical Inventory (aka Stock Take), with losses and adjustment reasons

...

1. 1. Losses and Adjustments (wastage, consumption, etc)
   2. Issue Stock (stock out)
   3. Receive Stock (stock in)
   4. Receive Stock using a VVM
   5. Receive stock from a shipment (POD)
   6. Receive stock from a shipment (POD) using a SSCC barcode (code 128)
   7. Record losses and adjustments using a UDI barcode (data matrix)
   8. Issue stock (picked with UDI barcodes) and packed into a box where we print a SSCC barcode
2. Requesting new Stock
   1. Stock-based, periodic, Requisition (from Stock on Hand and a calculated stock qty)
   2. Regular periodic Requisition (leverage Stock-based physical inventory, support fields such as:  stock out days, # of new patients)
   3. Receiving ASN/Despatch advice of a shipment being processed.
   4. Requisition Authorize
   5. Requisition Approval
   6. Work with (interop tbd) Program Data capture application to visualize programmatic data capture requirement as part of regular period requisition
3. Fulfilling an Order
   1. Fulfill an Order (Pick, Pack, Ship)
   2. Print a SSCC barcode (code 128) for the shipment
4. For implementations wanting a tailored user experience (i.e. match current country paper forms), can be customized(?) by a software developer
5. Implementation branding/themeing (implementer may brand/theme app without development cycle - ie through app settings)
6. Stock recall
7. 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 

...