Governance Committee Meeting Notes - December 15, 2015

How to increase country-base participation in OpenLMIS

Follow-on topic from last meeting. Come prepared with feedback from country teams.

20

All

• Gaurav (CHAI): No feedback from country teams - need sensitazation to support country teams and MoH to bring them up to speed. Learning curve. Need to open up involvement in all committees.

• Marasi (JSI Tanzania): Establishing formal governance committee (2-3 people) - Pharmaceutical service + ICT committee - governance and change control board for eLMIS. Responsible for reporting back to other technical committees and funding coordination. Head of ICT (Mr. Sotter), and PSU Head of IT (To be hired - responsible for ILS Gateway and eLMIS), and MSD Head of IT (Paschal Pastory), and Alpha (JSI).

• Mozambique: Language challenge, are phone calls a good mechanism for engagement?

• Karl - How much involvement does the country want over the product (vs. their specific implementation)? Interest in Tanzania. Is product roadmap a good place to engage?

• Lindabeth - What are the benefits for the countries of participation? Coordinated funding opportunities; Receive information on plans for the product; Influence on long-term vision of the product.

• Possible next steps:

  • Share the product roadmap with countries - solicit written feedback (translate).

  • Webinar on OpenLMIS Community - start of a user group community?

  • Start with existing deployments

  • Teams to begin socialization with country representatives

OpenLMIS Re-Architecture Plan Overview

15

Rich

• First Step: 2.0 Stabilization (January 2016)

  • Stable point to start future implementations 

  • Toggling-off country-specific features (can be switched back on)

  • Jenkins CI

  • Master branch, with agreed to coding standard and contribution guide

• Re-architecture Goals (3.0)

  • Extensibility - adjust behavior of the system to support country needs

  • Contribution Model - Country additions can be made available to others without breaking other's code. Increase ease of contribution and code manageability.

  • Separate "Core" from Modules - Services and functionality that are inherent to OpenLMIS and apply globally to any system - it's own separate code project. Changes infrequently. Highly reliable/tested. Can add functionality with modules without effecting the rest of the application

• Re-architecture Project Approach

  • "Core" Project

  • Reference Application Project - "Vanilla" Install - Core, UI, Authentication, Standard Modules, packaged for easy deployment

• Current Activities

  • Detailed design in progress

  • Impacts:

    • 3.0 Core will be smaller than what is in 2.0 today (to remove non-global features)

Questions:

What level of backwards compatibility will be available? What level of support will be available for updating code to new version?

Why would countries upgrade to the new version when it has less features than previous version?

•  

  • Schema will carry forward

    • User interface will carry forward

    • Core business logic will be revised - degree of change TBD

    • Worst case: Country specific extension would need to be re-implemented on new version

    • Steps to migration:

      • Data migration

      • Recoding country-specific (non-core) code as a module

Committee Updates:

• OpenLMIS Impact Collateral - Need Logo Approval

• In-Person?

• Current Projects List

10

Sarah

Not Discussed

OpenLMIS Implementation Opportunities Review Roundtable - Updates

• New?

• Malawi

• USAID BAA: Liberia, Sierra Leone, Guinea

• Vaccine Functionality

• Uganda

10

All

Not Discussed