...
- basic cold chain equipment support, but not beyond "It is working"
- suggestions for best practice processes in supply chain reports (core)
- mobile support under the admin level/ mobile for offline users
- 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/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)
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)
...
- Beyond health
- master product list (NO)
- 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 olmis offline-but for example, the requisition process could be made offline
...