Nov 12th, 2019

Introductions and Call opening (5 min)

• Notes from October Governance call

October Notes

Welcome

Framing and objectives for this call; 

Presentation of Future Path Options (20 min) 

Resonance Team-Kim Couri 

**Insert IQVIA Slide deck here **

Healthcare data science company- potential partnership option

want to be able to focus on stewardship and sustainability

What can IQVIA bring? Worlds largest healthcare dataset

Product: OpenLMIS continue to be open source, additional features to bring for future vision 

potential offerings for analytics that could be useful for govts

Support future expansion into other sectors

We know data is fragmented and want to build platforms that can inform product availability and broader market dynamics; this data could help them understand the whole market and access/availability

3 main pieces that would/could change in partnership scenario:

-OpenLMIS would integrate to be under the IQVIA umbrella; integrate into their global organizational backbone

-Digital strategy and design, future management

-Future business model; beyond government; potential private sector players that would benefit; they are in many countries globally already that we could leverage

-Can add master data management capabilities; can bring their salesforce into target markets, they work with other technologies in a complementary way; leverage other platform building-pieces 

Questions (Carl L): Have you thought through where OpenLMIS core and 'plus' boundaries lie? Continuing to develop and enhancing it may work against the goal of working for the OpenLMIS 'plus' which you are trying to commercialize. Need to be business minded about what we want OpenLMIS 'plus' to achieve. There are ways we can do this that can benefit both sides. If we get it right the existing community still gets to provide input and future customers can pay for it; want to retain community engagement to get inputs and keep it responsive to real needs within a country

(Carl L): Have you looked through current open source license to know if there would be required changes or other implications re: licensing? Questions would be for how long the license needs to be retained

(Edward): Role of an implementing partner would go away because IQVIA would become the implementing partner? right? They are open on this–question is around how much we want OpenLMIS 'plus' to be self sustained. Partners could still continue to do implementations which are better positioned than IQVIA; If we dont believe implementation is a revenue stream for maintaining the core product then it doesn't matter. What kind of risk re: not having enough revenue to sustain the core product? 

(Wes) Has IQVIA migrated any other open source products? No, this is unique for them, but they do a lot of technology integration. From change mgmt perspective they are very comfortable with it; its not a complex change or a risky change for them. 

(Gaurav): What sort of revenue projections do you have that makes this an attractive opportunity for IQVIA and what part of it do you anticipate reinvesting in OpenLMIS product and services? They are not ready for a revenue question yet...many of their partners that they work with do not make revenue. They know that OpenLMIS is part of a discussion of what they are in re: 'last mile pharma e-commerce' they need to be able to talk to distributors and understand markets for the countries it is used in. The synergy makes sense logically and then can figure out how to make money from it

Community Questions/Comments (internal)

(Edward): Seems similar to option 3 where you release OpenLMIS into the wild. Their plan to enhance the open source was not clear. Maybe the potential to grow the product into the private sector could be wonderful, but open source maintenance is not clear.

(Ashraf): More to digest and understand to conclude in 8 minutes...agree with Edward that progressing the private sector version should not be at expense of open source version

(Carl L): They could do this without our consent of the community (Technically). That they are taking this approach is a positive sign. We need a line between open source version and 'plus' version. Doesn't see any down sides to this...

(Emily B): We should dig into in Joburg: reality in any of these scenarios is that the future looks different. We are moving away for donor support so independent entity will also be focused on revenue generating streams. This tension will exist in any scenario; such as needing to bring in impact investors

Temperature Check:

Conferences and Meetings

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

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.

• 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:

• New Trello table! Similar to the above table, this tool is being used by the stewards to track our exploring of new product opportunities and partnerships

Study Tours:

• Study Tours wiki page tracks applications received, study tours completed, and other key milestones related to OpenLMIS Study Tours