CHANGES_NEEDED

(DRFO verification status = ‘NOT_VERIFIED’)

OR

(DRACS death acts verification status = ‘NOT_VERIFIED’)

OR

(Manual NHS verification status = ‘NOT_VERIFIED’)

OR

(UNZR verification status = ‘NOT_VERIFIED’)

OR

(MVS Passport verification status = ‘NOT_VERIFIED’)

OR

(DMS Passport verification status = ‘NOT_VERIFIED’)

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

The status doesn’t lead to blocking a person in the system

VERIFIED

(DRFO verification status = ‘VERIFIED’)

AND

(DRACS death acts verification status = ‘VERIFIED’)

AND

(Manual NHS verification status = ‘VERIFIED’)

AND

(UNZR verification status = ‘VERIFIED’)

AND

(MVS Passport verification status = ‘VERIFIED’)

AND

(DMS Passport verification status = ‘VERIFIED’)

Person 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

(Manual NHS verification status <> ‘VERIFIED’ or ‘NOT_VERIFIED’)

OR

(UNZR verification status <> ‘VERIFIED’ or ‘NOT_VERIFIED)’

OR

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

OR

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

At least one of the stream for person is not in final status (‘VERIFIED’ or ‘NOT_VERIFIED’)

NOT_VERIFIED

This cumulative status is temporarily unavailable.

At the moment can be set by manual update in the DB only;

The status leads to blocking a person in the system

VERIFICATION_NEEDED

INITIAL

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

Person 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 person has been invoked.

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

RC_IL.Sign person request (DMS)

RC_(GraphQL) Update Person (DMS) https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/18217041921

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/18213700177

IN_REVIEW

AUTO

Any verification status.

DRFO verification job has started by schedule.

Marks person that are processing by the DRFO verification job at the moment.RC_DRFO data synchronization for Persons (CSI-2823)

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/18038227025

NOT_VERIFIED

AUTO

Person has verification status IN_REVIEW
DRFO verification job successfully processed a person record.

Verification job responded that person's data is invalid/absent in the DRFO registry, and correction from MIS needed. Creation of new medical events, medication requests will be blocked for the person.RC_DRFO data synchronization for Persons (CSI-2823)

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/18038227025

VERIFIED

AUTO

Person has verification status IN_REVIEW
DRFO verification job successfully processed a person record.

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

RC_DRFO data synchronization for Persons (CSI-2823) https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/18038227025

VERIFICATION_NEEDED

INITIAL

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

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

By migration procedure.

VERIFICATION_NEEDED

MANUAL

Any verification status.
Verification status has been reseted via Admin panel

Marks persons as those requiring immediate re-verification (w/o person’s data update)/wiki/spaces/EDDR/pages/18052349994

RC_(GraphQL) Update Person UNZR verification status (DMS)

VERIFICATION_NEEDED

ONLINE_TRIGGERED

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

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

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805061326418213765970/RC_Sign+person+request+v2#UNZR-registry-verificationhttps://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050613264/Sign+person+request+v2#UNZRv2+DMS#UNZR-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDRDOCAIS/pages/1805110477217714380973/TRUSTED+PIS.+Patient+sign-up#Search-or-create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDRDOCAIS/pages/1805139972517714381017/TRUSTED+PIS.+Confidant+patient+sign-up#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805107201617525605723/PIS.+Patient+sign-up+registration#Search-or-create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805133417217525605723/PIS.+Confidant+patientPatient+sign-up+registration#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805090819718213732671/RC_PIS.+Complete+Update+Person+details#UNZRdetails+DMS#UNZR-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805058052417527603264/GraphQL+NHS+Update+Person#UNZR-registry-verification

VERIFICATION_NOT_NEEDED

AUTO

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

Marks persons as not requiring verification, since their data has been changed and they do not have an unzr/passport. So, there is nothing to verify.

VERIFICATION_NOT_NEEDED

INITIAL

Person was added to system before the Verification process has been implemented. Person has no unzr.

Person considered as such who has not to be checked trough implemented verification processes within EIS MVS register. Has no influence on cumulative verification status. The INITIAL reason will be replaced by AUTO over time, during the work of the job.

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050351106 RC_UNZR data synchronization for Person (DMS)

IN_REVIEW

AUTO

Verification status is VERIFIED or VERIFICATION_NEEDED.

Verification job has started by schedule.

Marks persons that are being processed by the verification job at the moment.

NOT_VERIFIED

AUTO

Person has verification status IN_REVIEW.
Verification job has successfully processed a person record.

Verification job responded that person's data is invalid according to the EIS MVS registry, and correction of person’s data required.

NOT_VERIFIED

INITIAL

Person has inappropriate data for synchronization: wrong format of the unzr number.

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

VERIFIED

AUTO

• Person has verification status IN_REVIEW.
  Verification job has successfully processed the person record.

• Person has been received from eMalyatko service

• Verification job responded that person's data is valid according to the EIS MVS registry. Correction is not required.

• Person has been received from trusted service that has verified data by default

VERIFICATION_NEEDED

INITIAL

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

Person considered as such who has to be checked trough implemented verification processes within EIS MVS register. Has no influence on cumulative verification status.

By migration procedure.

VERIFICATION_NEEDED

MANUAL

Any verification status.
Verification status has been reseted via Admin panel

Marks persons as those requiring immediate re-verification (w/o person’s data update)https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18052448299

RC_(GraphQL) Update Person MVS passport verification status (DMS)

VERIFICATION_NEEDED

ONLINE_TRIGGERED

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

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

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050613264/Sign+person+request+v2#MVS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805067880718217041921/RC_IL.Sign+person+request+request#MVSDMS#MVS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDRDOCAIS/pages/1805110477217714380973/TRUSTED+PIS.+Patient+sign-up#Search-or-create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDRDOCAIS/pages/1805139972518213766082/RC_TRUSTED+PIS.+Confidant+patient+sign-up#Createup+DMS#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805107201617525605723/PIS.+Patient+sign-up+registration#Search-or-create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805133417218213766120/RC_PIS.+Confidant+patient+sign-up+registration#Createregistration+DMS#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805090819718213732671/RC_PIS.+Complete+Update+Person+details+details#MVSDMS#MVS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050580524/GraphQL+Update+Person#MVSPerson_EN#MVS-passport-registry-verification

VERIFICATION_NOT_NEEDED

AUTO_DATA_ABSENT

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

Marks persons as not requiring verification, since their data has been changed and they do not have a passport document. So, there is nothing to verify.

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805061326418213765970/RC_Sign+person+request+v2+v2#MVSDMS#MVS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805067880718217041921/RC_IL.Sign+person+request+request#MVSDMS#MVS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDRDOCAIS/pages/1805110477217714380973/TRUSTED+PIS.+Patient+sign-up#Search-or-create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDRDOCAIS/pages/1805139972518213766082/RC_TRUSTED+PIS.+Confidant+patient+sign-up#Createup+DMS#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805107201617525605723/PIS.+Patient+sign-up+registration#Search-or-create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805133417218213766120/RC_PIS.+Confidant+patient+sign-up+registration+registration#CreateDMS#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805090819718213732671/RC_PIS.+Complete+Update+Person+details+details#MVSDMS#MVS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1805058052417527603264/GraphQL+NHS+Update+Person#MVS-passport-registry-verification

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

IN_REVIEW

RC_ MVS passport data synchronization for Persons (DMS)

IN_REVIEW

AUTO

Verification status is VERIFIED or VERIFICATION_NEEDED.

Verification job has started by schedule.

Marks person that are processing by verification job at the moment.

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

NOT_VERIFIED

AUTO_LOST

Person has verification status IN_REVIEW.
Verification job has successfully processed a person record.

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

NOT_VERIFIED

AUTO_INCORRECT_DATA

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

Person considered as such who has no valid data to be checked trough implemented verification processes within EIS MVS register. So, it must be corrected by responsible employee. This state mostly applicable to persons added to the system before the verification process has been implemented.

VERIFIED

AUTO_NOT_LOST

Person has verification status IN_REVIEW.
Verification job has successfully processed a person record.

Verification job responded that person's passport is not considered lost or stolen according to the EIS MVS registry