December 19, 2017

Monthly OpenLMIS Governance Committee Call. This meeting includes members of the governance committee, as well as anyone else interested in participating. 


7:00 - 8:00AM PST - Seattle

10AM to 11AM  EST - New York, DC

4:00PM CEST - Geneva, Copenhagen*

5:00PM EAT - Dar*

*Please note the updated meeting time in CEST and EAT timezones and the update call-in info below

Call Details

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap (US Toll): +16465588656,,214188477# or +14086380968,,214188477#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 214 188 477
International numbers available:

Action Items





Chat Captures

Introductions and call opening

  • Ashraf to facilitate introduction to Ethiopia team 
  • Carl Leitner to provide update on conversation with Satmed

Gap Analysis Kickoff Readout

Mary Jo Kochendorfer (Deactivated)
Matt Berg (Unlicensed)

  • Mary Jo Kochendorfer (Deactivated) presented a PPT on the Gap Analysis project kickoff
  • Expressed excitement to work with JSI and Ona, and also recognizes that there will be challenges. We're all excited to demonstrate that we can collaboratively build features in an efficient way. 
  • Reason for the work: Harmonize versions and provide a potential upgrade path for Tanzania and Zambia
    • Diversification of the OpenLMIS developer base 
    • Moving the developer center of gravity to Africa
  • Reviewed phases, deliverables, and timelines
  • Showed global distribution of development and management teams
  • Reviewed draft team composition 
    • Can't have fully staffed teams at each organization, understanding how shared services will work between the teams 
  • Opportunities:
    • More organizations contributing to core development
    • Investment in building expertise across organizations 
    • Opportunity for other organizations to implement/support v3
    • Conversations around additional funding (Data Use Partnership and USAID TZ) 
  • Challenges
    • Had hoped for fully staffed teams - not enough funding 
    • Coordination - Across multiple teams, similar expertise
    • Feature definition - Can be challenging process, not all existing features will be the best way to solve user needs. May need new features. 
    • Prioritization - Aligning stakeholders, achieving priorities 
    • Balance - Balancing goals of competing features and supporting community processes 
  • Question: Would other organizations be involved in OpenLMIS implementation projects or just core development?
    • Yes, a mix of both. May be involved in both
  • Kyle: When we say "focused on OpenLMIS" are we referring to core development or to implementations?
  • MJ: What Carl was asking - this refers to all organizations and a mix of activities. The other teams may have other projects unrrelated to OpenLMIS. The core team that VR has historically supported are not fully funded on this project. With additional funding we'll still have those four dedicated members, but outside of that we can't speak to everyone (Ona, JSI, etc.) 
  • Jake: It is our hope though that getting people spun up on v3 architecture that they could go after those. By growing the number of software devs that are "fluent" in this architecture there would be a larger implementer pool to draw from. Definitely a by-product that we want. We want JSI and Ona to be able to go after implementations using version 3. Just as VR used SolDevelo to backstop the Malawi implementation, then JSI or Ona could take the lead. 
  • Ashraf: JSI provides support tangentially to OpenLMIS through eLMIS. 
  • Carl: From my perspective I think this is a good thing to have a mixture of core and impleemntation work. Helps "ground" that core work and specific country requests. There could be positive effects. Can talk more about how to balance this. 
  • Kyle: Wants to talk more about this, specifically about implementations and linking lessons learned back to the global community. 
    • It's Kyle's prefernce from past experience, provides great insight for programmers to learn specific challenges during implementation. Should really look at that model.
      • 1 - implementation expereience, challenges 
      • 2 - implementation perspective: important to understand and limit the forking of country instances. Devs need to have experience in both places
      • 3 - country perspective: responsiveness to challenges, bugs, etc. 
  • Edward: Wanted to thank MJ and Jake for making this process very consultative and collaborative 

Digital Square Announcement B0

Tenly Snow (Deactivated)

Original proposal, had some language that Digital Square is mandated to find additional resources to cover activities that weren't covered in the original proposal. May be some things that are covered in the original proposal. 

Carl: What we want to do is continue to simplify the proposal process. More of a task order shortened process and add annual activities on top of that. Just because you have the initial approval for the gap analysis funding, want to make sure that these additional task orders are easy for you to manage. 

Edward: Quick question, what is the appetite for additional funding for OpenLMIS. Are Digital Square folks open to that? Will enlarge the pool?

Carl: Digital square management team doesn't make the decision. The governing board does. The board doesn't have a prioritization framework yet. We will present a framework to them in February board meeting. Will then use that as input for the end of April board meeting. Have an early draft of what that might look like. He doesn't know if they'll look for depth or breadth. But the language that was in the announcement was encouraging breadth. Not sure what the ultimate decision 

Ashraf: The way you described it Carl (depth and breadth), before a critical mass has been obtained for the depth, the breadth will make more sense. Depth (# of global goods) 

Opportunities sharing platformTenly Snow (Deactivated)

Jake: Would be helpful to frame the problem first 

Edward: A variety of organizations here, what is the role of the community and new business development. How do opportunities get sent out? Obviously if you're the person receiving the inquiries and then bidding on them, how do we keep this as transparent as possible? Open question. How do we triage opportunities? Is there a group that is part of the community to figure out on our own what makes the most sense? What should the new business process look like? 

Jake: What you're alluding to is that there is an inherant tension or appearance in the fact that Community Manager has been doing business development, but ultimately is a VillageReach employee. How to mitigate that, how to move OpenLMIS out of VR? Most immediately, how do we ensure that there is no conflict of interest. More implementatino work will be coming forward. How do we ensure that everyone can respond to these queries. Does anyone want to add onto that problem statement. 

Carl: Two issues:

  • Transparency for inquiries process
  • What is the responsibility if the opportunity doesn't come into the regular channels to share that with the community? Responsibility to share? 

Jake: Would also like to determine amongst Community members how we're going to review opportunities and respond, or not? Received feedback on Cambodia RFP, why didn't we respond? 

Edward: May find out about opportunities later once the timeline has expired. 

Matt Berg: Similar situation with the OpenSRP community. About who is actively involved. More important than how communication arrives. Has been a balancing act. We let people know if we're planning on bidding on a project. Opportunities for collaboration? Sometimes even bid against each other. 

Carl: Can skip to next agenda item (wrapped up in the same agenda item) 

Potential solution

All inquiries via or the website forms on are auto-forwarded to a Google Forum or Slack channel. 

Opportunities visualization 

Governance Charter, Community Structure, Approval Processes 

Carl Leitner
  • Update charter to reflect actual participation
  • Revisit scope and approval processes 
  • Set timeline for revisiting, publishing, and agreeing 
  • Ambassador model

Carl: Designee from the active organizations in terms of responding to inquiries. Who will be "on point" for responding to queries? Ambassador model is being used in OpenHIE. Can continue this conversation and find something that is comfortable for everybody. Part of the larger process of looking at the existing charter for the Governance committee → relationship to Product Committee. Take a look at revising the Charter to address issues that are coming up and formalize the Product/Governance relationship. With Digital Square we expect to have some funding that isn't tied to specific deliverables. If Governance and Product are well-structured, can delegate more responsibility to those committee. What are new functional requirements that aren't well funded? Want to ensure that the funding is there. Anyone interested in looking at that can propose a revised charter at the next Governance committee call. 

Jake: In working group, will discuss issue of lead sharing and come up with mechanisms to promote greater transparency as well as address the voting and approval processes. 

Community Updates
ZEIR (OpenSRP) and TimR demos

ZEIR (Overview):
ZEIR (Full):

TImR (Overview):
TImR (Full):

Matt Berg can provide demos 

GHSC-PSM article on Malawi rollout

Kyle to connect Tenly with Knowledge Management 

Open Source Sustainability Blog

OpenLMIS Webinar Series

  • Vaccine module update
  • Tupaia demo upcoming on  

Vaccine Module Update YouTube Video

Tupaia demo YouTube video

Global Digital Health Forum

Trip report to be published this week. 

Additions from the community? 


Kyle Duarte

Lindabeth Doby

Edward Wilson
Ashraf Islam

Jake Watson
Tenly Snow
Mary Jo Kochendorfer
Christine Lenihan

Carl Leitner
Lauren Wall 

Matt Berg 



OpenLMIS: the global initiative for powerful LMIS software