Followup meeting with Francesca Garrett- the CHT Community Manager. Attended by Christine Lenihan and Rebecca Alban (Unlicensed)
Medic are technical stewards, but there are other organizations that input into it. Their aim is to make it easier to launch digital health initiatives in their community.
toolkit includes- community health application framework- helps you to not have to start from scratch. provide a codebase that can be customized, also provide a suite of reference applications. They can be deployed as is, or be modified. Each one addresses a specific use case, or geography. They also include apps from other organisations. Open access design images
Just formalized a partnership with special olympics- screen for CHWs with disabilities
Have a Slack channel for developers
Creating an online community–in Discourse, meant to represent the CHT (not medic mobile). have categories or tags to track conversations about tools or apps. **opportunity fro our involvement. We could host a conversation, follow conversations that
What does it mean to be a partner? Formal partners have made commitment to community principles- to make resources to open access. (something to contribute). Governance structure reviews groups who are interested in partnerships. Trying to be very intentional with their initial partners.
They will provide tech support on this- platform will create a place for implementers to help eachother. And medic will facilitate and steer them to the right organization. Community of implementers who can give their own best practices
These tools are what have been used in all of their field implementations- they are being provided as reference applications. They have all been field tested and have a demonstrative impact
the first tool was medic mobiles tool- they were first to contribute (obviously)
Current no standalone apps related to supply chain-- opportunity to explore interoperability
Potential for scope to use the app is infinite - code can be modified in any way that people want to adjust their workflows. can be used in an endless implementations- maternal health, HIV AIDS, iCCM, many areas.
Partners are 'technical contributing partners'- org that might do a build on their framework. Reference application library will be robust
standards or reviews of applications to include them in the toolkit? they are creating standards for creating standards, other than just open source code. Will be some expectations around documentation and ese of implementation. Ideally want something that could be deployed 'as is'. Still deciding whether it needs to have been field tested. The online forum- we may find ways to host or promote them.
What are there most relevant use cases- not externally calling for, involves work where
Could create a 'tag' for OpenLMIS sot hat if there are conversations that organically occur , and pull those into a Slack channel. in early stages happy to be building community. Want to make sure we are easily able to plug into conversations
Next Steps:
Toolkit is not even formally launched yet. They still need to finalize list of tools that they will include in the toolkit (initially, as it will continue to grow). They will rehaul the website with this info.
They are keeping us on a list of inteersted parties and will keep us looped in to the launch of the toolkit and online community . Once that is published we can review the tools and consider how VR/OpenLMIS can utilize them or (possibly contribute to toolkit)
Present: Michael Kohn and Marc Abbyad, Medic Mobile/CHT; Brandon Bowersox-Johnson, VillageReach and Josh Zamor, OpenLMIS
...