Content
Table of Contents | ||
---|---|---|
|
Summary
Excerpt |
---|
OpenIMIS should be able to communicate with different registries. The medium-term goal would be for OpenIMIS to connect to different (standalone)registries. This space is specifically to discuss the linkage between openIMIS and Beneficiary Registries, and what effect that will have on openIMIS entities and relationships between entities. |
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
Involved Entities
Beneficiaries
Family
Process Description
Note |
---|
This section is a work in progress. |
There are different types of registries that might hold beneficiary data. Below are some examples of these registries and related information, with the aim to aid discussions to come up with a generic function requirement in openIMIS for linkages with beneficiary registries.
Registry | Linkage details | Reference Tools/Standards | Notes | Complexity | |
---|---|---|---|---|---|
1 | Health Client Registry | Registry <--> openIMIS
|
| Different from ‘beneficiary registry’ which might be a social register as the health specific one might have more specific information on health that might be useful in openIMIS - eg. for referral tracking etc. In some contexts this is seperate registry intended to keep track of individuals when they have an interaction with the health are system. Medium - High | |
2 | General Beneficiary Registry | Registry <--> openIMIS
|
| Overview of linkage between SoSYS (beneficiary mgmt system) in Nepal with openIMIS : SOSYS Nepal: openIMIS linkages with beneficiary management systems Any standard beneficiary registries out there? I don’t know if MOSIP fits, but thats the best I could come up with right now | Medium - High |
3 | CRVS (Civil Registration and Vital Statistics) Systems | Registry <--> openIMIS Registry → openIMIS: a) Get information on beneficiary (& family?) for enrollment. b) Link with unique beneficiary identifier openIMIS → Registry? | CRVS might be very country specific and difficult to come up with a generic way of interoperability - unless we just say we interoperate with OpenCRVS (which unfortunately doesn’t have a lot of implementations currently)High) | ||
4 | Paper based beneficiary registry | Document Management System (DMS) → openIMIS
|
Additional points to consider
Data ownership
Authenticated exchange between registry and openIMIS
Data Protection/Privacy Guidelines (eg. GDPR) and how and who gives consent
Page Properties | ||
---|---|---|
| ||
.. all content moved to the visible part of the page. |
Child Pages
Child pages (Children Display) | ||
---|---|---|
|
Related Reading
Example from Employment Injury Insurance in Nepal: SOSYS Nepal: openIMIS linkages with beneficiary management systems
Work done under Notice D1 for Formal Sector APIs: Healthix Sosys - High Level FHIR Process Flows Healthix Sosys - Low-level FHlR Process Flows