Custom openIMIS Functionalities
This page is under construction. The structure and layout might change.
The following table is listing different functionalities and under which implementations have been / will be developed and used. The objective of this table is to identify requested functionalities that might have already been developed and can be reused or will be developed under a specific implementation / project, before starting to redevelop them.
Functionality | Description | Developed by | Used in | Jira ticket.s / Wiki |
---|---|---|---|---|
Insuree number generator | During enrolment, the insuree number is automatically generated based on a set of rules and set to each insuree. | Mauritania implementation | Mauritania implementation | |
Insuree attachments | Attachments can be added to insurees for additional validation and treatment before enrolment. | Mauritania implementation | Mauritania implementation | |
Insuree multiple name management | Insuree can have 2 lastname / firstname (depending on alphabet used, in this implementation we needed to manage arabic and latin name) | Mauritania implementation | Mauritania implementation | OMI-47: Caractères arabe sur la carte d'adhésionUAT Deployment |
Multi-Program Management | Management of multiple “program” in the same instance. Manage multiple scheme in the same openIMIS with different rules. Each claims are linked to a specific scheme and can be see only for user with this scheme configured. | Cameroon UHC implementation | Cameroon UHC implementation |
|
Complex Services | Management of subservice and subitems in a service. Implement Service bundle with different calculation rules. |
|
Did you encounter a problem or do you have a suggestion?
Please contact our Service Desk
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/