Data Privacy is a key concern for the openIMIS initiative. Health financing mechanisms (such as insurance systems) capture a wealth of data on individuals, their families, their treatment, their health care costs as well as financial data on income and expenditure of an insurer. While data is generated and transferred by many different hands on the insurer side, the facility side or the client side it also transfers across different IT systems of different stakeholders in context of interoperability. Concerns of data privacy hence come from different angles. With openIMIS we would like to explore such concerns and see how openIMIS could address these.

We encourage you to contribute to this discussion by providing us your ideas and inputs. You can do so by directly stating requirements you would have from an insurance system. You can also share (by uploading on this page below the table) relevant documentation on this topic like publications, consultation summaries, presentations, etc. and adding a summary of your documentation by indicating key reflections and requirements from openIMIS derived from the shared document. You are free to also use workshop concepts developed and shared here by the initiative in your contexts to get us inputs from your contexts on this topic.

Consultation rounds

openIMIS has undertaken consultation rounds on Data Privacy at

re:publica in Accra, Ghana

republica 2018 - Data Confidentiality vs. Shared Data

Key impressions:


Day one consultation rounds in Basel

Day One Consultation event on Data Privacy

Key impressions:


OpenIMIS data privacy

The data is saved on the file system of the web server (photo of the insured persons) and in the database, which makes it accessible to users only via openIMIS solutions:

Server administrators have access to the data through direct access to the computer system (necessary for problem resolution)
System administrators can export data in order to reload them in an offline instance of openIMIS, these exports are protected by a password chosen when exporting.