Content

1 Summary
2 Overview
3 IC Prioritisation
4 Requirement
- 4.1 1.1 Goals/Scope
- 4.2 1.2 Background
- 4.3 1.3 Assumptions
- 4.4 1.4 User stories
- 4.5 1.5 Implementation Cases
5 Technical Specification
- 5.1 2.1 Impact on the general architecture
- 5.2 2.2 Impact on the database structure
6 Child Pages
7 Source

Summary

OpeinIMIS should be given a function that enables it to provide services to stigmatized groups without the OpenIMIS operator (e.g. service agent) being able to determine the exact identity of the beneficiary.
Note Michael Stahl: Examples are the allocation of vouchers to HIV patients or sex workers whose identity is to be protected.

Overview

Process Group	https://openimis.atlassian.net/wiki/spaces/OP/pages/1079607554
Function	Anonymization Function
Source	https://openimis.atlassian.net/browse/OSD-51
Related	https://openimis.atlassian.net/wiki/spaces/OP/pages/1191706637
Impact on costs (man hours, man days)
Impact on schedule
Category of change	Minor Major Principal

IC Prioritisation

Score	10
Current Relevance	10
Future Relevance	10
Global Good	10
Local Funding	Potential for funding in scale up of HIV free care scheme (through Catalytic Implementation Fund)

Requirement

1.1 Goals/Scope

The goal of this work is to create an anonymized function in openIMIS, where a claim admin can enter a claim for an anonymized person. More specifically, upon enrollment, the name, phone number and address of the beneficiary are recorded and a unique identification number (insuree number) is generated. Once saved, the personal information is only visible by an administrator (although it might be necessary that a responsible person at the HF be nominated to have access in case changes need to be made or a person looses his number and needs to be identified) . All other users only have access of the identification number. During the claims entry, the administrator enters only the unique number and all given services and items.

1.2 Background

In certain healthcare settings, anonymization in any database is required due to sensitivities in protection the identity of patients. This is the case for example with HIV patients, as the disease is highly stigmatized in certain communities and therefore the identity of these patients should be protected as much as possible.

1.3 Assumptions

1.4 User stories

#	User Story	Importance	Notes
1	As a claim admin, I want to create a claim for an anonymized person	3
2	As an enrollment officer, I want to generate an anonymized number	2

1.5 Implementation Cases

HIV User fees in Cameroon: currently, the anonymization function is done by another software DAMA that generates the number, but this is not deployed in all health facilities. If openIMIS could do this, only one software would be required for the entire enrollment and claims process.

Technical Specification

2.1 Impact on the general architecture

2.2 Impact on the database structure

Child Pages

Source

This was the idea mentioned during interviews with various stakeholders in February 2021.

Github: https://github.com/openimis/client-fe_js

openIMIS

Idea: Anonymization function