Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Title & presenter/sSession Objective/sSession MaterialsKey outputs and or/decisions made by the community
Day 1

OpenLMIS Sustainability Project Overview


Facilitator: Kim Couri (Resonance)

-Review where we are today re: sustainability research

-Review results of OpenLMIS Partner Engagement Survey

-overview of Future State options for consideration; including review prototype for private health 


-Reactions/Q&A

OLMIS Community Meeting_Slides Day 1 Final.pptx

OpenLMIS for Private Health-concept pitch

Reviewed research to date and 3 options on the table:

Results of OpenLMIS Partner Engagement Survey show most positive reactions for Option 2Partnership to Handover

Day 1

Presentations by IQVIA

Steven Harsono, head of public health for IQVIA

Introduce concept of OpenLMIS/IQVIA partnership-how would each party benefit? what are some considerations for how we would shape the partnership?

Reactions/Q&A

IQVIA-OpenLMIS Concept 6 Nov 2019.pdf

Summary of Feedback about IQVIA from Meeting Participants: 

-How would a commercial and core version of OpenLMIS relate to eachother? Would one feed the other? Commercial version fund core?-Strong

-IQVIA sees the idea of maintaining 2 products risky- one could 'cannibalize' the other; so they are open to maintaining one open source product

-We agree on a desire to continue supporting implementations; IQVIA seems open to this

-''It is up to us to guide the approach and determine what is important to us''

-Need ''We need to find a way to manage data concerns re: privacy & data ownership''

-''They have relatively high market penetration, geographic presence & resources to mobilize''

Summary of participant feedback- re IQVIA.pptx

Day 2Presentation by Mezzanine, Dale Sandberg

Introduce Mezzanine as a company, their model of work, and how OpenLMIS & Mezzanine could potentially work together

Reactions/Q&A

NA

Summary of Feedback about Mezzanine from Meeting Participants:

(to insert)-Common concerns about their narrow model of working as well as size/resourcing to take on OpenLMIS; unclear what their implementer role would be as not open to on prem support

-''This sounded mere like a hosting partnership with much stewardship of the product; the singular focus on SaaS does not seem to reflect the market realities

-''I am not sure Mezzanine’s SaaS only model is good fit for OpenLMIS current user base & implementers''

-'' They felt a bit warmer & like their mission aligns more closely with ours than IQVIA does but still unsure''

Summary of participant feedback- re Mezzanine.pptx

Day 2

Identification of Community Priorities

Facilitator: Rebecca

No matter what future path is chosen, we recognize that there will be a need to change from the status quo.

This small group exercise was designed to create consensus around what the community thinks is most important to retain, versus aspects that are negotiable. Clarification on these points this will be important when we engage in negotiations with any future partner



Process for this session: 4 small groups listed priority topics that they felt were important to retain. Then the large group went around to the different flipcharts and placed colored votes to indicate which points they agree or disagree with. Green votes indicate agree, yellow is tentative, and red indicated disagree

Feedback from this session is divided into 4 topical groups. The main takeaway points with community consensus (indicated by number of green votes) are listed below:

  1. OpenLMIS Product:
  • “Free” version of OpenLMIS as a global good continues to exist; implementations can contribute to the global good
  • The “free” version of OpenLMIS is a subset of the paid version and benefits from the paid version
  • There is one product roadmap that is publicly available

2. Partner & Community:

  • Community should be open to change and evolution; there is value in community but need to redefine
  • Current and future community members need to have opportunity to engage in implementations and won’t be required to upsell any commercial product
  • Need commitment between partner and community which at a minimum includes  :
    1. Mechanism to contribute code back to core version and cannot be removed
    2. A product roadmap (ideally with input on roadmap
    3. Clear roles around implementation (see #2)
    4. Commitment to community as important part of product
  • Need to leave with clear messaging on how we talk about future state

3. Current & Future Implementations:

  • Have options for local ownership and implementation
  • Product should maintain upgrade paths
  • OpenLMIS+ is built on core
  • Sensitise the value of data towards data sharing
  • Development of fair data use/sharing agreements
  • Implementers must have a choice of a global good version (OSS) & plus version ($$)
    • (Only tentative consensus around the following ideas)
      •  Implementers can contribute to core
      • Releases “premium” futures into openLMIS OpenLMIS after set time period (moving window)
      • Options for technical support packages that can be bought

4. Explanatory phase for future state:

  • Future out how to define success
  • Address concerns about partner fit and fears around 'selling data'
Day 3Messaging for our next stepsAlign on how we will speak about the OpenLMIS Sustainability work with stakeholders; our current process; and how we will move forwardNA

Agreed messaging around our next steps for the exploratory phase in 2020:

  • ''OpenLMIS is exploring public private partnership models that will enable us to continue supporting our open source product and public health mission''
    • Terms of any new partnership will stay true to our community goals and principles, as well as ensure that current and future implementations receive continued support
    • Our community has now aligned on what elements of OpenLMIS we prioritize and wish to retain in the future state; these will be used to guide conversations/negotiations with any future partners
    • We are exploring multiple private sector partners (we do not need to be name specific at this stage)
    • We should consider starting to sensitize stakeholders and country implementations around the value of (and possible future need to) contribute financially to for core maintenance/stewardship (for example adding USAID budget line annually)
Day 3

Definition of priorities for 2020 'Exploratory Phase'

Facilitator: Brandon Bowersox Johnson

This exercise allowed us to prioritize what type of activities for the steward team and wider community to  focus on in 2020.

We voted using Green (agreement), yellow (tentative), and red stickers (disagree). Therefore, items with the most green are where the community consensus lies

Topics were divided into 5 buckets for this exercise. Overall, there was agreement to focus on creating the right partnership, continuing community & capacity building activities, our public health mission, exploring data sharing and the value of our data. There were very mixed feelings about continuing to explore applications for the private health markets. Details below:

Image AddedImage Added

Image AddedImage Added

Image Added

Overview of Learning Sessions and materials

...