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 recap of discussions in Washington DC
-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
Empower School of Health's presentation to express interest to joining as a Trusted Partner:
(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
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 firstname.lastname@example.org as the contact, so inquiries come to the Community Manager. If we have email@example.com 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.
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
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.
(Did not get to cover this on Feb 12, 2019 meeting – skipped this topic because of low time.)
Country implementation opportunities:
This Trello tableis 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.
Machine Learning assets with Google- utility of AI for predicting facility consumption. Licensing questions being investigated with help of DIAL