Versions Compared

Old Version 7

changes.mady.by.user Siddharth Srivastava

Saved on

compared with

New Version 8

changes.mady.by.user Saurav Bhattarai

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Content

Table of Contents
excludeContent

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

Process Group

The JLN Process Matrix

Function

Linkage to various registries

Source

Interview with stakeholders

Related

https://openimis.atlassian.net/wiki/spaces/OP/pages/2385740062/Idea%3A+Integration+with+a+health+facility+register?focusedCommentId=2819948545#comment-2819948545

Page Properties

IC Prioritisation

Overall Score

Current Relevance

Future Relevance

Global Good

Local Funding

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

  • Registry → openIMIS:

    • Get information on ‘client’ for enrollment.

    • Link with unique client identifier

  • openIMIS → Registry ??

  • Registry <-> openIMIS:

    • Get identity and eligibility related info on patient

    • Provide details of diagnosis and treatment provided to an individual to insurer for payment processing.

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
(Social Protection Programmes)

Registry <--> openIMIS

  • Registry → openIMIS:

    • Get information on beneficiary for enrollment.

    • Link with unique beneficiary identifier

  • openIMIS → Registry:

    • Update registry of beneficiary details

    • New beneficiary?

  • openIMIS → Alternate Insurance system(s):

    • Update registry of beneficiary details

    • Transfer of individuals from one to another programme/insurer

    • Transfer claims history across with individuals when transferred to another programme

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 nowMedium - 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

Page Properties
hiddentrue
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.

.. all content moved to the visible part of the page.

Child Pages

Child pages (Children Display)
alltrue

Related Reading