Mozambique (VR implementer, Brandon)- VR are finishing a short engagement with Chemonics/PSM; looking at gaps to update SIGLUS
Angola (VR implementer, Brandon)- VR are currently doing an assessment to lay groundwork for OpenLMIS deployment to update their system from paper-based. → Brandon to follow up over email with Carl and Parambir over email
Cameroon (CHAI implementer, Satish)- Concept note, developed with Christine, submitted to GAVI 1 month ago. Haven't heard back officially- trying to coordinate to see what additional information they need
Malawi (VR)- Current task order ends in December. VR is talking to PSM folks about what capacity building efforts are needed to move our current implementation
Zambia they wanted additional analytics dashboard; Facility Edition- has been upgraded from desktop version to a web version; a facility would have one central installation of the FE (instead of many installations).
FOLLOW UP Request for Ashraf to provide a link; he will provide it to Mary Jo or Rebecca
Guinea (JSI)- provided reports on backfixes;
Tanzania VIMS (JSI) - CDI (JSI)- haven't received many requests and dont have ongoing contract
Should all Trusted Partners be required to sign a letter to comply with principles of TPs? For transparency and clear expectations it could be a good idea to have all TPs sign up to adhere principles outlined in the Trusted Partner doc FOLLOW UPRebecca Alban to draft this document
Trusted Partner logo created- draft guidance on logo usage and the logo files have been added to Trusted Partner document. Rebecca Alban circulated draft language and logos via our googlegroup- thanks for your comments FOLLOW UPRebecca Alban to finalize this language
We decided not to worry about trademarking at this time; intellectual property should be lumped in with other sustainability work
Here is the new TP logo:
Upcoming Trusted Partner Debrief Meeting-Oct 25 will outline our approach as our community to identifying and perusing implementation opportunities. Will clarify roles, responsibilities, and expectations of the core OpenLMIS team and Trusted Partners in this process. Will be time for discussion and feedback as well.
Comparison Matrix of Different OpenLMIS versions/products
We are constantly constrained by our inability to obtain large data sets from our current implementations. Challenge is that we don't have access to robust set of actual data. We have tried to obtain VIMS (obtained approval) but couldn't get the data. How do we address this risk?
This is challenging for us to do development work; and a risk. We did try to get data from Tanzania; approval was given but we were not able to get the data.
Any updates? Ashraf: regarding VIMS data; we have been asked to write a formal letter to be signed by the Permanent Secretary in order to get approval for them to share the data. Henry has a good relationship with their PS.
Abstracts submitted; still waiting on acceptance notices
Some of the GAP funding that was requested might not be approved; the team should re-submit the request with additional details about GAP activities to be conducted in Zambia, such as associated site visits to see FE and CE
Global Digital Health Forum
Washington, DC December 10th
Abstract to participate in panel accepted ''Facilitating collaboration to accelerate, scale and improve digital health global goods ''
Digital Square Global Goods Implementers Meeting-
Likely to be Dec 13th (date TBC)
2 members of OpenLMIS core steward team to attend
Linking facility data (Connect-A-Thon)
Tanzania Health Supply Chain
October 10-11, 2018
Matt Berg to Geneva in November to visit Global Fund
Should have follow up discuss how to position OpenLMIS
World Health Summit (Carl) for digital health principles?
Global Good Guidebook will be presented (OpenLMIS is featured in here)
OpenLMIS Community Lunch Meeting: being planned to dovetail with GHSCS conference
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 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.
Cite examples from recent Cote d'Ivoire opportunity:
What do we do when a Trusted Partner decides not to support the OpenLMIS v3? Or how does OpenLMIS decide When to not propose OpenLMIS when there is a system in country or a local entity is proposing a custom solution?