Purpose

This job is designed for initial and further regular synchronization of Parties with the EIS MVS registry in order to check if their passport documents are invalid or not.

Configuration

Data flow

Scheduller starts according to DMS_PARTY_SYNCHRONIZATION_SCHEDULE cron parameter. It creates oban job that selects DMS_PASSPORT_PARTIES_SYNCHRONIZATION_BATCH_SIZE Parties that match to some filter parameters. For each the job receives Party’s passport data on input and returns the result of reconciliation with the EIS MVS registry to output (details in “Step description” section below):

...

Step description

Step 1. Get list of Parties

Get list of Parties that meets the following criteria (using logical AND):

...

• dms_passport_verification_status = IN_REVIEW

• dms_passport_verification_reason = AUTO

Step 1.1 Update Party

Invoke the Step If party_verifications.dms_passport_verification_status still IN_REVIEW

...

• dms_passport_data_id = null

• dms_passport_data_status = null

• dms_passport_synced_at = null

• dms_passport_verification_status = NOT_VERIFIED

• dms_passport_verification_reason = AUTO_INCORRECT_DATA

• dms_passport_unverified_at = current datetime

Step 2. Call CheckPassportDMSStatus

Call CheckPassportDMSStatus with third-party service https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18052513879/MVS+Trembita+methods#CheckPassportDMSStatus using the following request params:

...

• pass_type = 0101

• pas_number = prm.party.documents.number (number as last six symbols)

• pas_serial = prm.party.documents.number (serial as first two symbols)

Step 3. Create or update dms_passport_data

If Step 2 was successful and PasStatus = 1 returned. Get a record from mimir.dms_passport_data table by pass_type, pas_serial, pas_number :

...

Step 4. Update Party

Invoke the Step If party_verifications.dms_passport_verification_status still IN_REVIEW (because if changed to VERIFICATION_NEEDED+ONLINE_TRIGGERED, then it means that party record has been changed while current sync with EIS MVS performed)

...

• dms_passport_data_id = mimir.dms_passport_data.id

• dms_passport_data_status = 1

• dms_passport_synced_at = date and time when synchronization has been performed (current datetime)

• dms_passport_verification_status = NOT_VERIFIED

• dms_passport_verification_reason = AUTO_NOT_VALID

• dms_passport_unverified_at = current datetime

Step 4.1. Update another Parties

Invoke the Step If party_verifications.dms_passport_verification_status is not IN_REVIEW

...

• dms_passport_data_id = mimir.dms_passport_data.id

• dms_passport_data_status = 1

• dms_passport_synced_at = date and time when synchronization has been performed (current datetime)

• dms_passport_verification_status = NOT_VERIFIED

• dms_passport_verification_reason = AUTO_NOT_VALID

• dms_passport_unverified_at = current datetime

Step 4.2. Update Persons

Invoke the Step if person_verifications.dms_passport_verification_status is not IN_REVIEW

...

• dms_passport_data_id = mimir.dms_passport_data.id

• dms_passport_data_status = 1

• dms_passport_synced_at = date and time when synchronization has been performed (current datetime)

• dms_passport_verification_status = NOT_VERIFIED

• dms_passport_verification_reason = AUTO_NOT_VALID

• dms_passport_unverified_at = current datetime

Step 5. Update Party

Invoke the Step If party_verifications.dms_passport_verification_status still IN_REVIEW

...

• dms_passport_data_id = null

• dms_passport_data_status = 0

• dms_passport_synced_at = date and time when synchronization has been performed (current datetime)

• dms_passport_verification_status = VERIFIED

• dms_passport_verification_reason = AUTO_VALID

• dms_passport_unverified_at = null

Step 6. Technical error returned

If technical error: PasStatus = -2, -1, timeout, etc. returned in Step 2 - the Party is considered unprocessed.

...