Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Method is used for approve or reject employee request.

...

Then party will be verified online with DRFO registry via separate process: https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17250320467/DRFO + data + synchronization +for+Parties#Data-flowfor Parties_EN

DRACS death acts registry verification

...

Then party will be verified online with DRACS death acts registry via separate process: https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249239231 Online verification of Parties with DRACS death acts registry_EN

DRACS name change acts registry verification

If party is created, set values in party_verifications table:

  • dracs_name_change_verification_status = VERIFICATION_NOT_NEEDED

  • dracs_name_change_verification_reason = INITIAL

If party is updated and persons dracs_name_change_verification_status = ‘VERIFICATION_NEEDED’:

Calculate cumulative verification status

Calculate parties cumulative verification status based on parties verification status in each stream: DRFO registry verification, DRACS death acts registry verification, DRACS name change acts registry verification according to logic described at https://e-health-ua.atlassian.net/wiki/spaces/DRACS2EH/pages/1786196877417820254221/UPD+Party+verification+status+model#Cumulative-verification-status

  • Set calculated status to parties.verification_status field

  • Create StatusChangeEvent for each active employee related to a party in event manager with new verification status if it was changed