February 12, 2019

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

Time

  • 7:00 - 8:00 AM PST - Seattle
  • 10:00 AM to 12:00 PM EST - New York, DC
  • 3:00 PM CET - Geneva, Copenhagen (4PM during daylight saving time of the year)
  • 5:00 PM EAT - Dar (6PM during daylight saving time of the year)


Call Details


Join Zoom Meeting https://zoom.us/j/377281719

One tap mobile +16699006833,,377281719# US (San Jose) or +19294362866,,377281719# US

Dial by your location: +1 669 900 6833 US (San Jose) or +1 929 436 2866 US
Meeting ID: 377 281 719
Find your local number: https://zoom.us/u/byw2qkHOU

Action items for next call   

  • Conduct a vote regarding Empower joining the OpenLMIS Community as a Trusted Partner

Action Items from January Governance

  • Rebecca and others to finalize Trusted Partner Declaration of community principles
  • Finalize BAO vote

Notes


Topic

Who

Notes

Chat Captures

Introductions and Call opening

  • Notes from January Governance call

January Notes

  

Carl is out sick so Rebecca will facilitate today



Trusted Partner UpdateRebecca Alban

Results of BAO vote for Trusted Partner and welcome to BAO

Excited that our community is growing with strong, experienced partners!

TP profiles on the wiki here: Meet our Trusted Partners

  • Resource for the community, putting Trusted Partners forward as the face of OpenLMIS
  • Will use this info for website content and pdf to be shared with stakeholders/potential implementers

Update and Reflections from Sustainability Meeting in Jan

Resonance Team 




Resonance team recap of discussions in Washington DC

Main points:

-Established 7 core attributes that are key to the OpenLMIS future state

-Reviewed 8 frameworks/theoretical constructs for OpenLMIS sustainability

-Underlying theme of workshop was that OpenLMIS should become an entity on its own (NGO, company or other)

-Honed in on the business models that had highest scores from the group, and left us with 4 constructs

-Taking a customer-centric view: 2 options (Option A and Option B) with different target audiences (some within health, and some outside). Both options will allow OpenLMIS to keep an Open Source core, and continue servicing the public health purpose

-Timeline: May 14-15 will be next workshop, June 28th final project briefing 

Questions (Brandon VR)-

  • Which idea incorporates private pharmacies? It would be in Option A, which incorporates health-only audiences
  • Are we going to also address the funding model in addition to customer that we fill focus on? The next phase of the work will focus mainly on the funding model over the next 4.5 months
  • (Emily VR): Why just 2 options? Was it pretty clear to the team whether other options should be excluded? The Option A & B are aggregations of many of the models that we reviewed. SAS and other funding options are baked into the current options. It seemed that a lot of the key decision points flowed from the customer base. Tiered pricing model is still in the mix and we want to consider it for both Option A and B


Here are the slides that were presented by Resonance:

Next Step: Rebecca Alban to conduct a vote over email and circle back to Empower


Empower School of Health- Trusted Partner Presentation

Sachin Jagtap

Radhika Singh

Empower School of Health's presentation to express interest to joining as a Trusted Partner:

Questions:

(Parambir)- Given that you are non partial consultants, is there a conflict of interest?- they will provide general information and feedback, their aim is to serve their customers. 

Brandon- appreciated the slide about how they want to be involved in the community- that is exactly what we want to see in terms of trusted partner involvement help folks to use this tool and use it better

Parambir-Do they have any in country presence in Africa? They have 4 global offices in India, Thailand, Geneva, and New York. They have representatives in various countries in Africa, but not an office (yet). But they are starting to do more work there so might get an office soon. They work a lot with local consultants



OpenLMIS Representation in the Digital Health Atlas

Rebecca Alban

(Did not get to cover this on Feb 12, 2019 meeting – skipped this topic because of low time.)

https://digitalhealthatlas.org/en/-/   There is a map that stakeholders can scan to see what digital health technologies are being used in each country.

Linkages to the Global Good Guide Book (Carl Leitner to describe)

Consensus needed on who the contact/focal person for each implementation should be. 

How is it being used? Donors want to know a foot print of a solution (how scaled is it).  Additionally if anyone wants to learn more about the solution, they will want a contact which can provide that information.

Option 1) Each implementing organization is listed as the contact. If we have each implementing organization serve as the point person, we want a way to say they are all OpenLMIS.

Option 2) We list info@openlmis.org as the contact, so inquiries come to the Community Manager. If we have info@openlmis.org be the point for each implementation, we will need a way to keep it updated (right now we don’t know all the information about the scale of the solution in each country.

VOTE


Recap of updated Steward roles 


Rebecca Alban

Steward team is taking a slightly downsized form in 2019, transitioning Mary Jo's previous role.

Quick review of the updated OpenLMIS stewards roles and responsibilities:

  • Brian Taliesin (OpenLMIS Director): PATH (50% LOE)- direction, vision, strategy, partnerships/relationships
  • Wes Brown (Technical Product Manager): taking over responsibility of product-related activities such as managing the Roadmap, product committee meetings, collecting feedback for the product. Will continue supporting current implementations and encouraging implementer engagement
  • Rebecca Alban (Community Manager): no changes in role, just 80% LOE. Continue with comms/advocacy, manage/track implementation opportunities, partner coordination, governance committee, study tours, respond to general inquiries
  • Josh Zamor (Architect)OpenLMIS software architecture, OpenHIE subcommittee, Software interoperability, integrations and standards, facilitate Technical Committee

A new wiki page created with this info, to guide community re: who to reach out to for various types of inquiries.


Conferences and Meetings

Conferences provide the community the opportunity for OpenLMIS members to speak or represent the OpenLMIS software and community in public forum.



All

Conferences 

  • Reproductive Health Supplies Coalition- General Meeting

  • ICT4D

    • April 30 – May 3 2019 in Kampala, Uganda
    • Maguette Thioro Ndong from Digital Square is presenting: Adapting Global Standards to improve Supply Chain in Health domain
  • Health & Humanitarian Logistics Conference 
    • July 10-11, 2019 in Kigali, Rwanda



Opportunities Roundtable

Definitions to use shared terminology:

  • Implementation opportunity: an opportunity for an implementation or deployment of the OpenLMIS software.  Usually this is done at a national or sub-national level within a ministry of health. This can also include feature work which would be done within the implementation and contributed back to the global codebase.
  • Community opportunity: a funding opportunity to support an organization or individual to work directly on the global codebase and/or administrate the community processes. This may include funding specific features on the community roadmap.
Rebecca Alban

(Did not get to cover this on Feb 12, 2019 meeting – skipped this topic because of low time.)

Country implementation opportunities:

  • This Trello table is being updated on an ongoing basis; to help the core team to track and manage implementation opportunities, but also provides a detailed snapshot of the scope and status of current implementation opportunities for stakeholders.


Community Opportunities:







For March Update: GAP Software features update
this presentation to be updated 
DIAL and Software Freedom ConservancyMichael D / Carl Leitner

1) the potential need to trademark the OpenLMIS Trusted Partner logo.   What types of services SFC can provide in this regard and how can DIAL can help facilitate?  

2)  pros and cons about moving the copyright from Village Reach to a third party such as SFC.


InteroperabilityCarl Leitner Josh Zamor

What is our strategy for interoperability?

List some interoperability use cases on a wiki page

strategy for fostering connections with other orgs: for example: TransIT

link to documentation in 3.5 about interoperability


AOB


Community and Product Updates
Product Updates
Community Updates




ATTENDANCE: Chris Opit (Unlicensed)Craig Appl (Unlicensed)Edward WilsonJosh ZamorMattias Wiklund (Unlicensed), Kim Courei (Resonance), Emily Clayton (Resonance), James Bernard (Resonance), Parambir S Gill (Unlicensed)Emily BancroftBrandon Bowersox-JohnsonJakub Sławiński, Sachin Jagtap (Empower School of Health)





RECORDING AND CHAT TRANSCRIPT   

Feb 12 Meeting Recording:
https://zoom.us/recording/share/2kvS_HWzIBYOOGDgVAot6PWU0Gc781rWlyyBptvNdyOwIumekTziMw 






ADDITIONAL READING