Page Comparison

...

B. Field Trip Experiences

Group 1: 

• Members' enrolment: central them, a lot of data entry done and similar data is entered in different systems
• Members' enrolment: concern about keeping data on phone and the security issues related to this (theft etc)
• Client Identification: no patient verification without internet is a challenge
• Client Identification: Definitions of household is loose (up to 6 people).
• Cards don’t have photos which makes it difficult for illiterate people to know which card is there’s
• Capitation: reimbursement system calculated on number of cases but provider still needs to add diagnosis in OpenIMIS. Should we be putting this level of effort on the provider when this data is not required for capitation payment 

...

• In Chad, how can this request for change (for co-payment) at the global level can be accommodated or we have it to develop it via local projects? We'll talk about the channels being used later in the afternoon. This shall be discussed among the implementers - it's something we need to find out based on your priorities. Local implementation structure and teams are needed for local development and features. Prioritization of requests is being assessed based on discussions with the technical advisory group. 
• How can we be registered to openIMIS (as a local company)? 
• How can we be capacitated? (Communication between local and global) Self-learning via wiki platform for architecture.. also via github
• For interoperability initiatives, how can we coordinate (so we don't end up doing the same thing)? Communicate with our developers.
• How high is the risk if I cannot fund local developers into the redesigned and modular system? Roadmap for communication among developers to be released by the end of the month.
• is there a timeline for redesign? 2 modules by end of 2019 but size of module not clear. There is a will. Will have roadmap and timeline at end of Feb 2019. Until then we will be sticking with the MS based system for implementation? Yes. It should also allow for seamless transition to modular approach
• Would you know about the licensing agreement (when it will be offered for free)? At the end of feb, they would most probably know about the new architectures
• Can this whole work be done offline? Enquiry part is still online. 
• Recommendation: Big opportunity to involve developers from pioneer countries like Tanzania (re-architecure phases, etc) . Response: Academic outreach with universities
• Recommendation: Need to involve local institutions like academia as early as now. Include in their curricula activities
• Comment: Local private software firms may be willing to participate in the developers' committee. Response: Universities can be entry points for capacity-building. 
• How can we benefit from the global initiative when the complete package is complete? We want to add open source development languages that are not dependent on Microsoft. Ideal scenarios is that the database layer exchangeable that can be run on a Microsoft server and Linode server.
• Comment: Potential for openIMIS to interoperate with other systems or existing systems that are up and running (GOTOHOMIS, etc)? 
• Will there be a claims management demo? Rejection reports

COUNTRY GROUP WORK

Q: Is there a sustainability plan for CBHI?

A: 

Q: In Cameroon and Rwanda, no enrolment features. Recommendation: Cameroon might want to customize it in their country as we are developing a master version. 

A: Government want to use the aspect of this program for the future. We want to check if we can adopt openIMIS. Our problem is we have many bills and we want to extend this program in Cameroon. It's a strategic decision to make.  We want to get ready on the rollout of openIMIS. To get the offline version installed and understand the functions so we can manage it on our level. 

Country System and Requirements: Tanzania

• Unclear policy direction 
• Governance: Sector-wide approach, health financing technical working group, CHF Implementers group, technical committee established on CHF IMIS, installment of payments (a question right now)
• Harmonization: Current rollout, harmonize strategy for enrolment officers, lot of issue on mismatch of money, 
• Feature Requests: Payments have arrived, policies are active, app that runs on any hardware, integration with facility system, client registry might have overlapped with insurance system - integration needs to be aligned re data capture, standardization on NHIF and CHF
• Challenges: SMS cost, hardware needs, lack of phones, capacity building (large number of people), administrative costs, unclear policyQ&A:

Q: Microsoft training - we have done video tutorials, we can create training in each region via video

Q (Rwanda): Standards for claim management or wait for the openIMIS software to be ready?

Comment: There should be closer linkages between working groups on health client registry and openIMIS. 

Technical

• Front (Material-ui, React & Redux, Javascript) in MS active source pages
• Back (Django/Python <> Java)
  • University students come with Java and Python
• Database (SQL server)
• HL7-FHIR as data exchange standard (issue: question on database set-up or use an external one?)
• Airflow for monitoring of batch processes
• Migrating mobile application

Academia

• Assets
  • Social protection and insurance (with courses on health financing)
  • IT programming
  • Research component
• Gaps
  • Limited tools for practical learning
  • Limited real-life scenarios
  • Curriculum outdated
• Action Items
  • Revisit curriculum to include openIMIS
  • Research topics on digital health trends using openIMIS
  • Ad hoc projects on openIMIS for collab between IT and social protection
  • Short courses on health financing (with openIMIS as a tool)
  • IT specialist to support the local openIMIS developers team

COMMUNICATIONS CHANNEL

-Data Confidentiality Onion

• Confidentiality Access
  • Public Communication (website) - representative deign
  • Team Communication (wiki) - transparent discussions
  • Internal Team (forum) - restricted 
  • Peer to peer (eMail) - confidential 
  • GIZ Internal - GIZ internal systems
• Communication Platforms
  • Issue Queue (Jira)
  • Wiki (Confluence)
  • Source Code Repository (Git)
  • Documentation Repository (Git)
  • Etc (Refer to Uwe's list)

-Public Communication

• Corporate Identity
  • Brand Guidelines
  • Templates (Powerpoint, Banner, Icons)
  • Merchandise 
  • Technical Writing
• Website
• Newsletter and Social Media
• Demo Server
• Documentation

-Team Communications

• Wiki for IC
• Wiki for DC
• Events
• Calendars
• Google Groups
• Google Folders

Reflections:

• 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: