Will be good to get a link / copy of the presentation.

Background

A Beneficiary registration system is already in place (SOSYS) run by the Social Security Fund (SSF).

SSF wants to keep SOSYS for beneficiary management and payment.

Classes

• Employer

• Contributer (Employee)

• Contribution

Processes

• Contributor Registration – probable link to openIMIS

• Contribution collectionLink between SOSYS & openIMIS

Current Status

3 APIs developed:

Batch Registration

Eligibility status - balance & other details are collected from openIMIS

Valuated claims report

Question:

Did you look at the FHIR resources as to how well they mapped?

• no not really

What do you plan to keep in SOSYS and what to remove?

Healthix

Recommendation:

this is more of a proof of concept / prototype approach

Please plan a more systemic API and interface suit that make it easier for systems like SOSYS to interface to openIMIS.

openIMIS is to be the claims adjudication aspect. Healthix to build interfaces to allow systems like SOSYS to leverage openIMIS’ claims adjudication functionality aspects.

possibility to leverage “eligibility” from within openIMIS by external systems (like SOSYS)

provide guidance to allow Healthix understands what is expecting and what need to be done

• the 3 APIs are prior activities

There is a regime with 31% (20/11) contribution but what information is wished to be available in openIMIS 31 %, the 20/11% or juste the contribution value

Possible deliverables

• Formal description of the formal sector API scope (roadmap) (Design and documentation)

• software deliverable / product

  • V1 - minimum of the SOSYS functional interfaces

  • V2 - a scoped set of additional interfaces as agreed by developers and community

• QA and testing code - functionality