...
- Encouraged to talk more about openIMIS and adopt it in the country
- Appreciate the clarification of governance structure
- Importance of communications
- Broaden our systems with openIMIS
- Difference between IMIS and openIMIS and the potential of timing in terms of starting implementation
- Sustainability via academia
- Strengthening the local capacity
DAY 2
Reflections:
-How do we approach the next steps (work plan-oriented)
-Requirements from different countries and find out how we can continue the conversation in Rwanda
-How we can collaborate from the requirements to the development (how the process can be easily managed)
-Communication channels are easily completed
-Some are skeptical about openIMIS
-Participants gained confidence on openIMIS
-Interaction between implementers and developers (communication channels)
-Harmonize and streamline processes
-Interaction, timelines, guidelines
-Connect the global, regional, and national levels
-Knowledge exchange and knowledge production
-Regional hubs roles (what are expected from them)
-Use of tools for knowledge sharing among different country contexts
-How do we make countries contribute to the global good
Implementing
*Private Sector
*Dr Mashaushi and Dr Faraja (Academe they dont have health - IFM), similar gaps with Asia
*Good branding
*KPIs - what are expected from CoPs and timelines
-Template for presentations, etc and documentation of country context stories
JEMBI HEALTH SYSTEMS
-African non-profit company
Jembi's core competencies include:
*needs assessment and requirements gathering
*system design and solution architecture
*software design and solution architecture
*software development
*implementation and capacity-building
Jembi's approach to health information systems
-acknowledging the interconnection between policy, practice, and technology
-focusing on building local capacity to use, manage and maintain the health information systems
-honest brokers of technology
-focus on interoperability
-Project Canvas
Country Engagement
AIM: Viable solution for health financing in low-resource setting
*Country Engagement
-represented in relevant African health information systems communities
*Products and Requirements
-country driven requirements are available to support openIMIS feature refinement and the ongoing development of the system
*Technical Product Requirements and Interoperability
-openimis interoperab
*Implementers
*Capitation
*Technical Architecture
Q&A:
Q: How do you conduct projects in countries?
A: TA, work with local capacity in the country and build that, work with ministries of health, work with openMRS in Cameroon, also do some of the dev work, build capacity with local moh to manage systems,
Q: Interesting to look deeper into, how do you reach out to people, how do you transfer and write messages and communicate to people?
A: System we designed we look at individual country requirements and make it universal and develop that functionality and follow standards from the blood transfusion society. We looked at how we do that product management or project management. A lot of engagement on the user side.
Q: It's important to have the translation part outlined at the beginning. That kind of highlights sustainability in the country.
Q: Interested in process steps. Based on the country assessment, how you went about it? In terms of prioritization and creating the global good? How do you list and select them and prioritize?
A: Slide deck later in the afternoon to check the processes
Q: Besides the blood project, we also have the CRVS project.
Q: What do you need to be onboard? So we can support you in the process?
A: We don't have the health financing knowledge but the more we know about the area. People don't state the point or tell a story that illustrates the point and is able to repeat the point and reiterate. A lot of discussion on how you go about gathering your requirements kind of capacitating in that way. We want to look at health financing and this is how you go about for these requirements. Health financing knowledge so we shape all those discussions. W have a lot of people we can start these discussions with.
Q: Use your networks. Interesting to know your network (later at lunch)
Q: Local capacity-building it may be where the networking part comes in (which may include private sector).
A: Anything for us to read. It's a bit complicated.
Q: Have a presentation on how Jembi is operating in Africa and how we leverage this collaboration. We face a lot of questions on success factors. Our colleagues will be interested in about it. If a possible joint session?
A: We can set up a webinar.
EPOS
-Group of companies in Germany (1985)
-Mainly active in Africa but also involved in hospital planning and supply
-Michael as a freelance consultant (hospital sector)
-Workflows in hospitals (focus on IT system implementation) and see how they can fit in the workflow
-openIMIS (open source approach is a good thing) and might go in the same direction with DHIS2 (university-based)
-To serve whole countries instead of having siloed pilot solutions
-From cap bldg perspective, we should focus on the political decision-makers, play with it, see the benefits
-Easier to have a menu on issues (as multiple choices) - small things that would make it easier to use
SWISS TPH
-Research and tropical diseases, training and cap bldg, health systems programs (education), insurance medicine courses, research activities happening within the institute,
-Department is on the implementation side, siddhart based on the technology side
-Implementation side - doing different health sector sides
-Dragos - health technology and telemedicine
WORK PLAN
Promotion
-Webinars
-Marketing
-Resources (demos, videos)
-Social Media
-Donor side
-Government side
Implementation
-Implementation Starter Kit (ongoing)
-Capacity-building (modules, content)
-Support to the implementation side (resources)
-Usability requirements (Flow of issue queue)
-Focus on rearchitecturing within the development teams
Infrastructure
-
-