Introductions and Call opening - Notes from August Governance call
| |
Intro from Stew, joining the call today
|
|
Engaging SolDevelo to participate in Governance(3ish minutes)
| Mary Jo Kochendorfer (Deactivated) | - SolDevelo have been functioning as trusted partners for some time but have never officially been invited to governance
- Proposal to be grandfathered in as a TP and member of the governance committee: all feedback is positive, no dissent
- JSI: approve
- VR: approve
- PATH: approve
- Ona: approve
- Kaleb: approve
- PSM: approve
- Continued Discussion: Should SolDevelo sign a letter to comply with principles of TPs? We could do that for every organization; make everyone officially sign up to adhere principles
Next Step: Rebecca Alban (Unlicensed) to officially invite Jakub from SolDevelo |
|
Partner coordination (5 min)
| Parambir S Gill (Unlicensed) | - Discussion/suggestions on how to increase partner coordination for upcoming opportunities; more joint proposals
- JSI: we need better information about actual opportunities, and enough lead time to put together a solid proposal
- The more we know in advance, the better prepared we can be
- Suggestion from JSI: could solicit input from the community during the design phase, scope of projects. This could produce realistic scopes of work
- Suggestion from VR: promote partnerships within the community to put together better teams; want to evangelize this idea
- If partnerships are created in early phases, from the outset, they will be more well-received
- Was Angola work a public RFP? Yes, but work will be done to increase visibility of future opportunities and publicize it within the community
|
|
Software development Update (2 minutes for questions)
|
| Context: Includes all four teams. Started testing in Sprint 105, released 3.4 in Sprint 106. Current sprint stats: https://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504
Only 15 bugs ranked as major (a huge reduction for the team). Overview of bugs here. Living Product Roadmap for what is to be delivered in 3.5. We are thinking to push back the 3.5 release to the end of November/early Dec. | Proposal to IHE QRPH for ADX on FHIR |
New Trusted Partner Update (4 min)
| |
Feedback: lettering looks a little fuzzy but may be a resolution thing. Rebecca will check. |
Sustainability update (4 min)
| Brandon Bowersox-JohnsonKaleb Brownlow (Deactivated) | Vendor Selection Next steps: pursue phase 1 contracting with Resonance; still some concerns re; their short timeline. Could build in a milestone into the contract, post phase 1, which would require a review. - mid-late Q2 would be desired timeline.
- Brittney at BMGF will reach out to Resonance to get the contracting process started. Goal is to have something in place by end of September, for an October start date.
|
|
Grant Spend and Proposal Update (5 min)
| Mary Jo Kochendorfer (Deactivated) | - The below presentation provides a high-level funding overview of current and upcoming grants, spending, and risks/challenges
- We should highlight these funding-related risks and challenges to Resonance and Lenati as we move forward in our conversations with them
Widget Connector |
---|
url | https://docs.google.com/presentation/d/1GxQ4hv8kLGGLfYcd7or7zkoRYVdYXeHGaB2CH4BPwa4/edit?usp=sharing |
---|
|
Source: https://docs.google.com/presentation/d/1GxQ4hv8kLGGLfYcd7or7zkoRYVdYXeHGaB2CH4BPwa4/edit?usp=sharing |
|
Interface Workstream Update (5 min)
| Rebecca Alban (Unlicensed) & Mary Jo Kochendorfer (Deactivated) | - Voting outcome for prioritizing DHIS2 (Vision for Integration)-majority vote achieved
- How to proceed for remaining priorities (do we really need this level of detail on Governance or should we move to product?)
|
|
Using actual data for demo, performance, and reporting We are constantly constrained by our inability to obtain large data sets from our current implementations. We would like to update the governance of this challenge and risk to current work. | Mary Jo Kochendorfer (Deactivated) & Brandon Bowersox-Johnson | 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? |
|
Current implementations-updates on what stage they are at/activities (5 min) | | - Mozambique (VR implementer, Brandon)
- Angola (VR implementer, Brandon)
- Cameroon (CHAI implementer, Satish)- the country team in Cameroon presented the CHAI-VR OpenLMIS concept note to GAVI late last week. We are yet to hear back from them. I will keep you posted as soon as I have any updates from the country team. As of now, the concept note only has a high level approach and solution sans the budget. Once GAVI responds positively, we will work on building a more comprehensive proposal.
- Malawi
Implementation Opportunities for more details. |
|
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 - OpenHIE Community Meeting
- Global Health Supply Chain Summit (GHSCS)
- 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 ''
- Angola
- Postponed to late October
- Tanzania Health Supply Chain
Meetings - OpenLMIS Community Lunch Meeting: being planned to dovetail with GHSCS conference
|
|
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 (Unlicensed) | Community 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.
|
|
Moving Forum Discussion from Google Groups to Discourse | Wesley Brown | Discussion and Decision Update: after weighing the potential costs and benefits of shifting community conversations to Discourse, the community stewards decided that this is a 'value-add' and want to move forward with it Any questions or reservations from the group on this? Highlighting the current gaps: - Google Groups:
- Does not fill the gap between real time communication (Slack) and email.
- Ends up being another funnel into our inboxes
- Lacks advanced forum features like categories, user/community management, user individualization/progression, etc
Proposal for Discourse (based on feedback from Craig): - Discourse would be the main entry point into the OpenLMIS community for new members
- The system should require an account but one that can be freely made by the user. User categorization can be used to denote users with more experience within the community (see OpenMRS Developer Stages)
- I think that Discourse would incorporate:
- Google Groups discussions
- Public project-related email
- Some of what currently goes into Slack
- Some the discussions currently occurring within the wiki
|
|
Conflict of Interest (September agenda is packed, so we will cover this in our October meeting) | Mary Jo | 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? |
|
AOB |
|
|
|
Community and Product Updates |
---|
Product Updates |
|
Community Updates | Community Meeting |