openIMIS unreviewed

https://openimis.org

Open-source insurance management information system.

This page shows how openIMIS vocabulary codes map to PublicSchema canonical values. If you work with openIMIS and spot an error, please report it.

10 vocabularios covered: 10 correspondencia de valores. 1 property mapping.

Vocabularios

Vocabulario Nombre en el sistema Relación Cobertura Brechas
delivery-channel PayTypeChoices Correspondencia de valores 3/4 correspondencias 3 sin cobertura
education-level Education Correspondencia de valores 6/7 correspondencias 3 sin cobertura
gender-type Gender Correspondencia de valores 3/3 correspondencias 1 sin cobertura
group-role GroupIndividualRole Correspondencia de valores 14/14 correspondencias 4 sin cobertura
group-type FamilyType Correspondencia de valores 6/6 correspondencias 1 sin cobertura
identifier-type Correspondencia de valores 4/4 correspondencias 16 sin cobertura
payment-status BenefitConsumptionStatus Correspondencia de valores 7/7 correspondencias 4 sin cobertura
relationship-type Correspondencia de valores 13/13 correspondencias 7 sin cobertura
sp/enrollment-status BeneficiaryStatus Correspondencia de valores 4/4 correspondencias 2 sin cobertura
sp/grievance-status Correspondencia de valores 5/5 correspondencias 4 sin cobertura

Propiedades

Vocabulario Nombre en el sistema Cobertura Brechas
administrative_level LocationType 4/4 correspondencias 1 sin cobertura

Brechas documentadas

Elementos de PublicSchema que openIMIS no modela, con la razón documentada.

Elemento PublicSchema Razón
benefit-frequency OpenIMIS does not define a payment frequency vocabulary. Payment cycle cadence is configured per product as numeric date fields (start/end dates and recurring periods), not as a categorical enumeration.
benefit-modality OpenIMIS does not have an explicit benefit modality vocabulary. The social protection module handles cash transfers; in-kind or voucher modalities are not represented as a categorical field.
conditionality-type OpenIMIS does not model conditionality as a categorical attribute on benefit plans. Conditions are managed outside the core schema.
eligibility-status OpenIMIS does not have a dedicated eligibility determination status vocabulary. Eligibility logic is embedded in benefit plan rules and BeneficiaryStatus; there is no separate EligibilityDecision record with its own status field.
hazard-type OpenIMIS does not model hazard or shock events. The system has no shock-registry or emergency-trigger module.
marital-status OpenIMIS does not include a marital status vocabulary in the extracted modules. The insuree model does not have a marital status field in the social protection or insuree modules covered here.
referral-status OpenIMIS does not have a referral module or referral status vocabulary in the extracted codebase. The grievance module handles complaints, not inter-program referrals.
targeting-approach OpenIMIS does not expose a targeting approach vocabulary. The benefit plan configuration does not categorise the method used to identify beneficiaries as a controlled value set.
event-severity v2 event-severity classifies hazard/disaster impact (OASIS CAP v1.2). OpenIMIS's closest scale is grievance TicketPriority (Critical/High/Normal/Low) on the grievance_social_protection module, which measures grievance urgency, not disaster impact. The domains differ, so no semantic mapping is offered. If OpenIMIS deployments record hazard events, they would need a separate severity field aligned with CAP.
event-certainty OpenIMIS does not model event certainty. This vocabulary is used for shock or hazard events, which are outside the scope of the openIMIS modules.
Notificar un problema con estas correspondencias