Shared Vision for OpenLMIS Software (Plenary)

Owned by Kevin Cussen (Deactivated)
Last updated: Oct 06, 2015
  • Description: What are the boundaries of OpenLMIS? What is the domain scope in which OpenLMIS will operate? What belongs in OpenLMIS and what doesn't?

Leads: Dykki, Kevin

To Join Remotely: 

Join the call: https://www.uberconference.com/info3285

Optional dial-in number: 716-293-6106

PIN: 63498

Rapporteur/Notetaker:Sandy Hawley

Notes from Session:

What IS part of OpenLMIS?

  • basic cold chain equipment support, but not beyond "It is working"
  • suggestions for best practice processes in supply chain reports (core)
  • costing data- cost of supplies by program
  • batch management
  • different ways to install- configurable vs. specific
  • stock management (district, region, int. warehouse)
  • open source
  • one (1) product or platform
  • a common roof for programs (essential meds and vaccines)
  • requisitions
  • source for analytics/data source- R&R
  • commodities transaction data
  • modular
  • facilities "light" or interface
  • dispensing "light" or interface
  • key processes supported offline: (intermittent access) * - determine which one (some need support and some don't)
  • reference mobile application
    • responsive: not pillar/core; but sufficient interface and APIs to allow for construction of apps that enable mobile access
    • trying to create a one size fits all isn't feasible (mobile use is different for each country/facility) 
  • upgrade path 

 

What it is NOT part of OpenLMIS (doesn't mean we won't interface with this, it's just not our focus/core, or another system that does it better)

  • medical records
  • ERP system (warehouse data)
  • procurement at national level (no budgeting and buying)
  • asset management
  • full stack analytics tool, full business intelligence tool
  • bar coding, but support call for separate modules
  • budgeting
  • warehouse management
  • EMR
  • distribution management/rout planning, transport
  • master product list
  • master data
  • CHW
  • M&E
  • disaster relief/response
  • disease or initiative specific
  • Full VAN tool
  • country-specific system

 

QUESTION ITEMS

  • beyond health
  • master product list 
  • mobile and offline are separate issues but
    • usable offline - many countries need offline capability, especially where mobile challenges exist (screen size for forms, data not feasible in some places)- interface issues may be country specific 
  • SaaS
  • annual forecasting
  • facility stock management, or clients without online capability - does the mobile/offline become part of OpenLMIS?
    • offline capability is a need (this is feedback we are hearing)
    • in current state- its not possible to make whole OpenLMIS offline-but for example, the requisition process could be made offline 

 

 

Artifacts:

Is the domain of OpenLMIS:

Is NOT the domain of OpenLMIS:

Questionable / Contested:

 

OpenLMIS: the global initiative for powerful LMIS software