Versions Compared

Key

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

...

  • NOT_VERIFIED - if any streams has got NOT_VERIFIED status

  • VERIFIED - if all streams has got VERIFIED status

  • VERIFICATION_NEEDED - if any streams has not got a final status as VERIFIED or NOT_VERIFIED

Note

Verification status of a stream that has value VERIFICATION_NOT_NEEDED does not affect the value of cumulative verification status.

Verification status

Conditions

Description

NOT_VERIFIED

(DRFO verification status = 'NOT_VERIFIED')

OR

(DRACS death acts verification status = 'NOT_VERIFIED')

OR

(MVS Passport verification status = ‘NOT_VERIFIED’)

OR

(DMS Passport verification status = ‘NOT_VERIFIED’)

Party is not verified (has status NOT_VERIFIED) in at least one stream

VERIFIED

(DRFO verification status = 'VERIFIED')

AND

(DRACS death acts verification status = 'VERIFIED')

AND

(MVS Passport verification status = ‘VERIFIED’)

AND

(DMS Passport verification status = ‘VERIFIED’)

Party is verified in all streams

VERIFICATION_NEEDED

(DRFO verification status <> 'VERIFIED' or 'NOT_VERIFIED)'

OR

(DRACS death acts verification status <> 'VERIFIED' or 'NOT_VERIFIED')

OR

(MVS Passport verification status <> ‘VERIFIED' or 'NOT_VERIFIED')

OR

(MVS Passport DMS verification status <> ‘VERIFIED' or 'NOT_VERIFIED')

At least one of the stream for Party is not in final status ('VERIFIED' or 'NOT_VERIFIED')

...

Status

Reason

Conditions

Description of target verification status

Method to turn the status

VERIFICATION_NEEDED

INITIAL

Party was added to system before the Verification process has been implemented.

Party considered as such who has to be checked trough implemented verification process with DRFO register.

By migration procedure

VERIFICATION_NEEDED

ONLINE_TRIGGERED

Any verification status.
Create/Update employee has been invoked.

Marks parties as those requiring immediate verification because their data has been changed.

https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249403019

https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249206457 Approve or Reject employee Request

RC_(GraphQL) Create Employee request (DMS)

IN_REVIEW

AUTO

Any verification status.

DRFO verification job has started by schedule.

Marks party that are processing by the DRFO verification job at the moment.https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271128770

DRFO data synchronization for Parties_EN

NOT_VERIFIED

AUTO

Party has verification status IN_REVIEW
DRFO verification job successfully processed a party record.

Verification job responded that party’s data is invalid/absent in the DRFO registry, and correction from MIS needed. Some APIs will be blocked with time for employees related to the party.https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271128770

DRFO data synchronization for Parties_EN

VERIFIED

AUTO

Party has verification status IN_REVIEW
DRFO verification job successfully processed a party record.

Verification job responded that party’s data is valid and present in the DRFO registry. Correction from MIS is not required.

https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271128770

MVS passport verification

...

MVS passport verification

This status model is valid for mvs passport stream that performs a synchronization with EIS MVS register to check whether the passport document is among stolen or lost ones.

...

Source:

View file
nameMVS Passport status model for Parties v2.drawio

Status in the stream

Reason in the stream

Conditions

Description of target verification status

Method to turn the status

VERIFICATION_NEEDED

INITIAL

Party was added to the system before the Verification process has been implemented.

Party is considered as such who has to be checked trough implemented verification processes within EIS MVS register.

By migration procedure.

VERIFICATION_NEEDED

ONLINE_TRIGGERED

Any verification status.
Create/Update employee has been invoked.

Marks a Party as those requiring immediate verification because its data has been changed.

/wiki/spaces/EDDR/pages/18051006540 Approve or Reject employee Request

VERIFICATION_NOT_NEEDED

AUTO_DATA_ABSENT

Any verification status.
Create/Update employee has been invoked, data pre-estimation by the job

Marks Parties as not verified, since their data has been changed and they do not have a passport, but must have.

/wiki/spaces/EDDR/pages/18051006540

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18051334145

IN_REVIEW

Approve or Reject employee Request

RC_MVS passport data synchronization for Parties (DMS)

IN_REVIEW

AUTO

Verification status is VERIFIED or VERIFICATION_NEEDED.

Verification job has started by schedule.

Marks a Party who is being processed by verification job at the moment.

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18051334145 RC_MVS passport data synchronization for Parties (DMS)

NOT_VERIFIED

AUTO_LOST

Party has verification status IN_REVIEW.
Verification job has successfully processed a party record.

Verification job responded that Party's passport is considered lost or stolen according to the EIS MVS registry, and correction of its data required.

NOT_VERIFIED

AUTO_INCORRECT_DATA

Party has inappropriate data for synchronization: invalid passport number or more than one passport document.

Party is considered as those who has no valid passport data to be checked trough implemented verification processes within EIS MVS register. So, it must be corrected by responsible employee.

VERIFIED

AUTO_NOT_LOST

Party has verification status IN_REVIEW.
Verification job has successfully processed a party record.

Verification job responded that party's passport is not considered lost or stolen according to the EIS MVS registry. Correction is not required.

DMS passport verification

This status model is valid for dms passport stream that performs a synchronization with EIS MVS register to check whether the passport document is among the invalid ones.

...

Source:

View file
nameDMS Passport status model for Parties v2.drawio

Status in the stream

Reason in the stream

Conditions

Description of target verification status

Method to turn the status

VERIFICATION_NEEDED

INITIAL

Party was added to the system before the Verification process has been implemented.

Party is considered as such who has to be checked trough implemented verification processes within EIS MVS register.

By migration procedure.

VERIFICATION_NEEDED

ONLINE_TRIGGERED

Any verification status.
Create/Update employee has been invoked.

Marks a Party as those requiring immediate verification because its data has been changed.

/wiki/spaces/EDDR/pages/18051006540 Approve or Reject employee Request

VERIFICATION_NOT_NEEDED

AUTO_DATA_ABSENT

Any verification status.
Create/Update employee has been invoked, data pre-estimation by the job

Marks Parties as not verified, since their data has been changed and they do not have a passport, but must have.

/wiki/spaces/EDDR/pages/18051006540

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050449429

Approve or Reject employee Request

RC_DMS passport data synchronization for Parties (DMS)

IN_REVIEW

AUTO

Verification status is VERIFIED or VERIFICATION_NEEDED.

Verification job has started by schedule.

Marks a Party who is being processed by verification job at the moment.

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050449429 RC_DMS passport data synchronization for Parties (DMS)

NOT_VERIFIED

AUTO_NOT_VALID

Party has verification status IN_REVIEW.
Verification job has successfully processed a party record.

Verification job responded that Party's passport is considered not valid according to the EIS MVS registry, and correction of its data required.

NOT_VERIFIED

AUTO_INCORRECT_DATA

Party has inappropriate data for synchronization: invalid passport number or more than one passport document.

Party is considered as those who has no valid passport data to be checked trough implemented verification processes within EIS MVS register. So, it must be corrected by responsible employee.

VERIFIED

AUTO_VALID

Party has verification status IN_REVIEW.
Verification job has successfully processed a party record.

Verification job responded that party's passport is considered valid according to the EIS MVS registry. Correction is not required.

DRACS verification

...

Source:

...

Status

Reason

Conditions

Description of target verification status

Method to turn the status

VERIFICATION_NEEDED

INITIAL

Party was added to system before the Verification process has been implemented.

Party considered as such who has to be checked with DRACS register.

By migration procedure

VERIFICATION_NEEDED

ONLINE_TRIGGERED

Any verification status.
Create/Update employee has been invoked.

Marks parties as those requiring immediate verification because their data has been changed.

https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249403019

https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249206457 Approve or Reject employee Request

RC_(GraphQL) Create Employee request (DMS)

VERIFIED

AUTO_ONLINE

AUTO_OFFLINE

Party has verification status VERIFICATION_NEEDED, NOT_VERIFIED, VERIFIED

Marks Party as VERIFIED in case found related death act, or in case Job 1 has not got any related act.

Comment will be set to NULL in DB.

Two jobs conducts verification of a parties:

NOT_VERIFIED

AUTO_ONLINE

AUTO_OFFLINE

Party has verification status VERIFICATION_NEEDED, NOT_VERIFIED, VERIFIED

Marks Party as NOT_VERIFIED in case Job 1 and/or Job 2 found possible related death act(s) (grey zone)

Comment will be set to NULL in DB.

Two jobs conducts verification of a parties:

VERIFIED

MANUAL_NOT_CONFIRMED
MANUAL_CONFIRMED

Party has verification status NOT_VERIFIED

MIS user conducts verification.

Party marked as verified with appropriate reason by a MIS user

https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249599655

/wiki/spaces/DRACS/pages/17570431333 Update Party verification status

RC_(GraphQL) Update Party DRACS death verification status (DMS)

VERIFIED

OFFLINE_VERIFIED

Prerequisites

  • All death acts for 2014-2022 period were downloaded from DRACS register and processed by eHealth system's Offline verification process and

  • parties are still in status VERIFICATION_NEEDED with reason INITIAL after processed 2014-2022 death acts

One time migration for such parties to VERIFIED status with OFFLINE_VERIFIED reason)

Comment will be set to NULL in DB.

To be conducted within system support process

IN_REVIEW

MANUAL

  • party was not verified by medical employee during parametrized period (for example 30 days)

/wiki/spaces/DRACS/pages/17570431333 RC_(GraphQL) Update Party DRACS death verification status (DMS)