Content
| Table of Contents | ||
|---|---|---|
|
Summary
| Excerpt |
|---|
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. |
| Page Properties | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Overview
|
| Page Properties | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
IC Prioritisation
|
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
| Child pages (Children Display) | ||
|---|---|---|
|
Source
This was the idea mentioned during interviews with various stakeholders in February 2021.