Global - October 15 2019

Call Information

  • 08:00 PDT - Seattle
  • 11:00 EDT - New York, DC
  • 17:00 CAT - Zambia/Malawi (UTC+2)
  • 18:00 EAT - Tanzania/Kenya (UTC+3)

Last Meeting NotesGlobal - Sept 17 2019



Lead (Time)

Notes and Updates

Software Development Update

RoadmapLiving Product Roadmap 

Current sprintBacklog Grooming Sprint 135

Upcoming sprintBacklog Grooming Sprint 136

Version 3.7: 

Team stats


3.7 Release Update

  • Phase 1 of the release process testing is completed
  • Phase 2 is underway, should be completed in the next day or two

Implementer Meeting FeedbackWesley Brown (5 min)

Meeting Notes: Implementers - October 1 2019


  • Feedback on feature requests
OpenLMIS Private Health (Proposed Sustainability Prototype)Wesley Brown (10 min)

Google Presentation:


  • Simon - Work similar to this is already ongoing in Angola (Primavera, AppySaude). Need to expand the operations-side of thing; things like real-time support. May need to find local partners to help actually provide this. Applications that currently exist tend to be "square peg in round hole." A dashboard on the landing page could be helpful
  • Sebastian - Dashboard: Different roles would want to see very different data on a dashboard.
  • Dercio - Adding a role-based dashboard could be a good new feature for core OpenLMIS

Version 3.8

Wesley Brown (10 min)

Feature Backlog: Feature Backlog

Proposed Features:

  1. Configuration Assistant
  2. Stock Management - UI Caching

If we could have only one feature, which one?

  • Simon - Configuration assistant; most headaches from products (facility-approved products) and supply lines.
    • Products can now be managed directly in OLMIS (as of v3.7)
  • Sebastian - Concerned that we wouldn't be able to improve the configuration much in just 3 Sprints. Perhaps just focus on a single page/configuration element. Perhaps improved visualization of user roles/access.
  • Sachin - Better support for non-linear facility configuration (ie, not strictly following the level-based facility structure).
    • Certain category of products might come from a hub whereas others might come from another facility. The flow of products should be able to vary.
    • Sebastian - This might be supported already, it would depend on exactly what this configuration entails. We added support for multiple suppliers in a previous version (v3.6, I think).
    • Christine - We do have flexibility in the approval configuration, but complicated to setup and validate. Would be nice to improve this area, however this doesn't change once set up.

Next PC meeting: Topic ideas??

Additional Requests and Information:




OpenLMIS: the global initiative for powerful LMIS software