RC_Offline comparison of divorce acts with Persons (DRACS 2.0)

Purpose

This process fetches divorce acts data from mimir service and uses it for comparison with persons data.

Key points

1. This process uses cron parameter to configure its start time.

2. This process is performed in mpi scheduler pod.

3. Each divorce act is compared by husband data and by wife data separately.

Configuration

Service logic

Offline comparison job starts according to PERSONS_DRACS_DIVORCE_ACTS_COMPARE_SCHEDULE cron parameter.

Step 1. Divorce acts list for comparison

1. Get list of divorce acts from that are ready to be compared to persons - perform RPC call to mimir service, dracs_divorce_acts table, with following parameters:

   1. ar_op_name = ‘1' or '4’

   2. persons_compare_status = ‘READY’

2. Sort obtained list in ascending order by dracs_divorce_acts.updated_at field

3. Limit obtained list with PERSONS_DRACS_DIVORCE_ACTS_COMPARE_BATCH_SIZE value

4. In case no divorce acts were fetched - end process.

Step 2. Data preparation and potential candidates select

1. Get divorce act from obtained list, update its status in dracs_divorce_acts table:

   1. set persons_compare_status = ‘IN_PROCESS’

2. Get husband data for comparison process if mn_old_surname <> mn_surname and these fields are not empty

3. Get wife data for comparison process if wmn_old_surname <> wmn_surname and these fields are not empty

4. Prepare divorce act data for comparison process

   1. perform regexp for each of the fields:

      1. for mn_name, wmn_name, mn_old_surname, wmn_old_surname, mn_patronymic and wmn_patronymic change:

         1. [ --'] to ''

         2. 'є' to 'е'

         3. 'и' to 'і'

      2. for mn_series_numb and wmn_series_numb change:

         1. [ /%#№ _-]  to ''

   2. for mn_date_birth and wmn_date_birth change mask from dd.mm.yyyy to yyyy-mm-dd

   3. for mn_numident and wmn_numident normalize value - check that it is 10 symbols, if not true - set null

5. Get active persons (is_active=true, status=active) as candidates for comparison with husband or wife data from divorce act from MPI db using following predicate blocks:

   1. tax_id

   2. documents.number

   3. birth_date + last_name

   4. settlement_id + last_name

6. In case no candidates were found for husband and/or wife, update divorce acts persons compare status:

   1. set persons_compare_status = ‘PROCESSED’

7. Go to next divorce act in obtained list (return to p.1 of Step 2)

Step 3. Divorce act comparison process

1. Get person from obtained candidates list

2. Prepare persons data for comparison process according to Deduplication process NEW | Data cleaning and preparation

3. Define person’s document for Deduplication process:

   1. If passport document type is present in the act (DocType=1), then choose person’s PASSPORT or NATIONAL_ID depending of the passport number in the act by regex.

   2. If other document type is present in the act, then submit a list of documents to deduplication process: BIRTH_CERTIFICATE, COMPLEMENTARY_PROTECTION_CERTIFICATE PERMANENT_RESIDENCE_PERMIT, REFUGEE_CERTIFICATE, TEMPORARY_CERTIFICATE, TEMPORARY_PASSPORT

4. Compare divorce act data with person data using logistic regression method, as implemented in Deduplication process:

   1. For each variable field use separate calculation process based on the table below.

   2. Calculate final comparison score between divorce act and person.

Step 4. Verification candidates

Before performing this step, check that divorce act record is still in persons_compare_status = 'IN_PROCESS'.
In case status is changed - skip this step, go to next divorce act in obtained list (return to p.1 of Step 2).

Based on divorce act and person comparison score, there are two flows that can be performed:

• white zone or grey zone (comparison score is greater than PERSON_DRACS_DIVORCE_ACT_PARTIAL_MATCH_SCORE value)

• black zone (comparison score is less than PERSON_DRACS_DIVORCE_ACT_PARTIAL_MATCH_SCORE value)

Step 4.1. White or grey zone

White or grey zone indicates that divorce act possibly relates to person, therefore it can be stated that person changed its surname after divorce and it can be used by doctor as supporting information for update person process.

1. Create verification candidate between divorce act and person in MPI db, person_verification_candidates table, set values:

   1. id = autogenerate uuid

   2. person_id = id of a person from mpi.persons

   3. entity_id = id of divorce act from mimir.dracs_divorce_acts

   4. entity_type = ‘dracs_divorce_act’

   5. status = ‘NEW’

   6. config = variables that were used in comparison process (p.3 of Step 3)

   7. details = additional details of comparison process

   8. score = logistic regression comparison score

   9. inserted_at = now()

   10. updated_at = now()

       1. if active verification candidate between person_id and dracs_divorce_act_id already exists in person_verification_candidates table in status = ‘NEW’ - skip this pair

2. Update persons verification status in person_verifications table based on current dracs name change verification status of person:

   1. in case dracs_name_change_verification_status = ‘VERIFICATION_NOT_NEEDED’ or ‘VERIFIED’ - update persons dracs name change verification status:

      1. set dracs_name_change_verification_status = ‘VERIFICATION_NEEDED’

      2. set dracs_name_change_verification_reason = ‘AUTO_OFFLINE’

      3. set updated_at = now()

      4. set updated_by = system_user()

Step 4.2. Black zone

Black zone indicates that divorce act does not relate to person, therefore it can be stated that person highly likely did not change its last name.
No further actions should be taken with person or verification candidates.

Step 5. Processed divorce act

1. When divorce act is fully compares with all candidates from list, change its status in mimir.dracs_divorce_acts table

   1. set persons_compare_status = ‘PROCESSED’

2. Go to next divorce act in obtained list (return to Step 2)