openIMIS product:
the principle of insurance product is to enroll Beneficiaries via a contribution hat the pay themself, this means that the main insuree is entering in a contractual relation with the scheme, to do so they accept to comply with the conditions, this include, but not limited to a serie mandatory information on the insurance taker (Head of family) and other beneficiaries.
coreMIS program:
unlike openIMIS product, coreMIS program aim to the target people proactively based on politic impulse, this mean that the program need to have a base of potential beneficiaries (high probability of errors in the data) used to target the final recipent for the relief based on the relief target
How to merge those fundamental difference ?
I do believe that once a person is enrol, some confidence in the data collected must be correct there for the “beneficiary“ must use the same table as “insuree” (Beneficiary being more generic)
Also the relationship entity that reflect the enrolment should be similar, in openIMIS product, we use a policy but it is too limited for coreMIS, something more generic is required: “Benefit”, openIMIS product should move to the benefit entity in the future.: Benefit consumption module / Enquire
Before being a beneficiary, for targeting reasons, a person will be an individual/person, this model will require up to no mandatory data.