/
Moldova Vouchers: Architecture and Data Model

Moldova Vouchers: Architecture and Data Model

Integration Architecture

The following integration architecture will be implemented in Moldova.

openIMIS will be integrated with the following eGA systems

System

Objective

System description

More information

System

Objective

System description

More information

MPass

Authenticate employers

 

https://mpass.gov.md/?lang=en

MPay

Manage vouchers payment

 

 

MNotify

Send notification to workers on vouchers assignments

 

https://mnotify.gov.md/#/en/home

MConnect

Mediators

 

https://mconnect.gov.md/#/

MCabinet

Get information about employers and workers

 

 

MLog (optional)

Log actions

 

 

Software Architecture

This is the links between the entities in the worker voucher scheme in Moldova that have to be managed through openIMIS.

The software architecture mapping the above is

The project is covering only the payment for vouchers by the employer, the invoice part. The payment to government accounts, bills, are not in the scope of the project.

Data models

Location

Location setup is not used in this instance but is one of the main configuration which everything depends on. This means the implementation will require to have at least one Village level location. The following configuration will be done and applied to all entities linked to Location:

Region

District

Municipality

Village

Region

District

Municipality

Village

Moldova Regiune

Moldova Raion

Moldova Municipiu

Moldova Oras/Sat

User

Users are created automatically based on the MPass authentication. The first time a user connects to openIMIS through MPass authentication, the user account is created. Roles are created manually in openIMIS and must match the roles assigned in MPass so they can be automatically assigned to the created users. Roles and user information must be checked at every authentication/connection so the user details are updated, especially the roles the user has attached (to prohibit or allow access to features).

Field openIMIS

Mandatory in openIMIS?

Data MD

Mandatory/Optional/Hidden

Default value

Comments

Field openIMIS

Mandatory in openIMIS?

Data MD

Mandatory/Optional/Hidden

Default value

Comments

login_name

YES

NameIdentifier

mandatory

 

  • unique

  • expected to be IDNP

last_name

YES

LastName

optional

 

 

other_names

YES

FirstName

optional

 

 

phone

NO

MobilePhone

optional

 

 

email

YES

EmailAddress

mandatory

 

 

language

YES

Language

mandatory

 

  • one of “ro”, “ru”, “en”

  • language pack required

User Roles

YES

 

mandatory

 

  • different table

  • custom field to be specified in the integration request

User Districts

YES

 

mandatory

Moldova

  • different table

  • not available in the MPass payload so default district level

PolicyHolder (Employer)

The insuree information will be automatically filled from MPass authentication reply. We assume the AdministeredLegalEntity will contain both Legal Entity Name and IDNO. Separate IDNO and CompanyName is assumed not available.

Field openIMIS

Mandatory in openIMIS?

Data MD

Mandatory/Optional/Hidden

Default value

Comments

Field openIMIS

Mandatory in openIMIS?

Data MD

Mandatory/Optional/Hidden

Default value

Comments

code

YES

IDNO (from AdministeredLegalEntity)

mandatory

 

unique

trade_name

YES

Legal Entity Name (from AdministeredLegalEntity)

optional

 

 

location

YES

 

optional

Moldova

not available in the MPass payload so default village level

address

NO

 

hidden

 

 

phone

NO

 

hidden

 

 

fax

NO

 

hidden

 

 

email

NO

 

hidden

 

 

contact_name

NO

 

hidden

 

 

legal_form

NO

 

hidden

 

 

activity_code

NO

 

hidden

 

 

accountancy_account

NO

 

hidden

 

 

bank_account

NO

 

hidden

 

 

payment_reference

NO

 

hidden

 

 

Insuree (Worker)

The insuree information will be automatically filled from MConnect (https://semantic.gov.md/en/assets/details/399a1038-c457-47ef-8a48-531c897d1d1a ). Only Insuree number will be editable field.

Field openIMIS

Mandatory in openIMIS?

Data MD

Mandatory/Optional/Hidden

Default value

Comments

Field openIMIS

Mandatory in openIMIS?

Data MD

Mandatory/Optional/Hidden

Default value

Comments

chf_id

YES

IDNP

mandatory

 

unique with validation on the length

last_name

YES

FamilyName

mandatory

 

 

other_names

YES

GivenName

mandatory

 

gender

YES

Sex

???

 

Sex code (contains values from the sex classifier CF 37603221.0037.01)

dob

YES

DateOfBirth

???

 

 

marital

NO

 

hidden

 

marital status

passport

NO

 

hidden

 

not useful because chf_id is national ID

type_of_id

NO

 

hidden

 

 

phone

NO

 

mandatory

 

to send QR code by MMS

email

NO

 

optional

 

to send QR code by email

current_address

NO

 

hidden

 

 

geolocation

NO

 

hidden

 

 

current_village

NO

 

hidden

 

village level

photo

NO

 

hidden

 

 

photo_date

NO

 

hidden

 

 

card_issued

NO

 

hidden

 

 

relationship

NO

 

hidden

 

 

profession

NO

 

hidden

 

 

education

NO

 

hidden

 

 

 

 

 

 

 

 

Voucher

This consists in a new module that will handle the creation, payment and assignment of vouchers. It’s inherit the HistoryModel

Field openIMIS

Mandatory

Type

Default value

Comments

Field openIMIS

Mandatory

Type

Default value

Comments

code

YES

string

 

unique and autogenerated

issue_date

YES

date

today

 

expiry_date

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk


This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/