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

« Previous Version 7 Next »

  • 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)
  • better mobile support under the admin level
  • costing data- cost of supplies by program
  • 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

 

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
  • master product list

QUESTION ITEMS

  • master product list (NO)
  • usable offline  (YES)
  • No labels