Content
Table of Contents | ||
---|---|---|
|
Summary
Excerpt |
---|
OpeinIMIS should be given a function that enables it to provide services to stigmatised 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
|
Source
This was the idea mentioned during interviews with various stakeholders in February 2021.
Github: https://github.com/openimis/client-fe_js
hidden | true |
---|
Info |
---|
You can add optional sections in this hidden box. The people working on this idea can then move the section into the visible part of the page. |
Involved Entities
Process Description
Additional ReadingRequirement
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.
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) | ||
---|---|---|
|