Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
styledefault
typelist
printablefalse

...

  1. Compare Confidant persons documents_relationship data with each birth act data using comparison process:

    1. get documents_relationship.number (with type = BIRTH_CERTIFICATE) from confidant person

    2. get certificates.cert_serial + certificates.cert_number with certificates.cert_status = 1 from birth act

    3. perform normalization of found numbers (remove special symbols, bring to lower register)

    4. compare found numbers:

      1. if at least one act is equal – proceed with all valid acts data to next comparison step

      2. if all acts are not equal – skip this confidant person, if Person does not have other confidant persons – proceed to Step 5

  2. Compare Confidant persons personal data with each birth act data (compared from previous comparison step) using comparison process:

    1. get last_name, first_name, second_name, tax_id and birth_date from confidant person

    2. get father_surname, father_name, father_patronymic, father_numident, father_date_birth, mother_surname, mother_name, mother_patronymic, mother_numident, mother_date_birth from birth act

    3. perform normalization of found fields (remove special symbols, bring to lower register)

    4. compare confidant person with parents by following steps:

      1. compare last_name, first_name, second_name, birth_date with father_surname, father_name, father_patronymic, father_date_birth or mother_surname, mother_name, mother_patronymic, mother_date_birth

        1. if at least one act is equal – compare tax id on the next step

        2. if all acts are not equal – skip this confidant person, if Person does not have other confidant persons – proceed to Step 5.

      2. compare tax_id (if exists) with corresponding father_numident or mother_numident (if exists)

        1. if does not exist or exists and at least one act is equal – proceed with all valid acts data to next comparison step

        2. if not equal – skip this confidant person, if Person does not have other confidant persons – proceed to Step 5

  3. Check compared Confidant persons parent rights from birth acts (compared from previous comparison step):

    1. get father_parent_rights and mother_parent_rights from birth act

    2. check that father_parent_rights <> 183 or mother_parent_rights <> 185 for corresponding confidant person

      1. if father_parent_rights <> 183 or mother_parent_rights <> 185 for Confidant person – proceed to next step

      2. if father_parent_rights = 183 or mother_parent_rights = 185 for any Confidant person – skip this confidant person, if Person does not have other confidant persons – proceed to Step 5

  4. Search for active person using Active person search algorithm with successfully compared confidant person last_name, first_name, second_name and tax_id (if exists)

    1. if tax_id does not exists or search returns ‘No active person found’ or ‘Impossible to clearly identify an active person’ messages – skip this confidant person, if Person does not have other confidant persons – proceed to Step 5

    2. if one active person is found – check that it can be used as confidant person using following validations https://e-health-ua.atlassian.net/wiki/spaces/CSIEH/pages/17612832814/18000249948/RC_+CSI-1323+_Create+Confidant+Person+relationship+request#Validate-confidant-person

      1. if no validation fails – create Confidant person relationship as described https://e-health-ua.atlassian.net/wiki/spaces/CSIEH/pages/17613422651/18000249998/RC_+CSI-1323+_Approve+Confidant+Person+relationship+request#Create-confidant-person-relationship-(action-%3D-INSERT) here, only set:

        1. verification_status = ‘VERIFIED’

        2. verification_reason = ‘AUTO’

        3. dracs_birth_synced_at = now()

      2. remove confidant person data from persons.confidant_person field

...