Versions Compared

Key

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

...

  1. CHANGES_NEEDED - if any of streams has got NOT_VERIFIED status

  2. VERIFIED - if all registers/streams have got VERIFIED status

  3. VERIFICATION_NEEDED - if any verification stream has not got a final status as VERIFIED or NOT_VERIFIED

  4. NOT_VERIFIED - if manually has been set into DB

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

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

...

Status

Reason

Conditions

Description of target verification status

Method to turn the status

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 rules or verified with registers.

By migration procedure.

VERIFICATION_NEEDED

RULES_TRIGGERED

Person has verification status VERIFICATION_NEEDED,IN_REVIEW, NOT_VERIFIED, VERIFIED

Create/Update person has been invoked and at least one of corresponding rules triggered.

Marks person for NHS as those requiring manual verification.

It is switched to by:

Creation of IL.Person_request

Creation of IL.authentication_method_request

VERIFIED

RULES_PASSED

Person has verification status VERIFICATION_NEEDED,IN_REVIEW, NOT_VERIFIED, VERIFIED

Create/Update person has been invoked and no rules to send for manual verification process were triggered.

Marks person for NHS as those who has passed controls automatically.

Comment will be set to NULL in DB.

It is switched to by:

Creation of IL.Person_request

Creation of IL.authentication_method_request

IN_REVIEW

MANUAL

Person with verification status VERIFICATION_NEEDED with reason RULES_TRIGGERED

Manual change of verification status is invoked.

Means that person is being verified by NHS employee

https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271129848/RC_(GraphQL) + Update + Person + manual + rules + verification +status_EN?search_id=a86819ab-64e4-4865-b5f3-aa2290e729e6status (DMS)

NOT_VERIFIED

MANUAL

Person has verification status IN_REVIEW

Describes that person's info is incomplete and correction from MIS needed.

Comment is required.

https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271129848/RC_(GraphQL) + Update + Person + manual + rules +verification+status_EN?search_id=a86819ab-64e4-4865-b5f3-aa2290e729e6verification status (DMS)

VERIFIED

MANUAL

Person has verification status IN_REVIEW

Describes that person is verified manually and no clarifications needed.

Comment will be set to NULL in DB.

https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271129848/RC_(GraphQL) + Update + Person + manual + rules + verification +status_EN?search_id=a86819ab-64e4-4865-b5f3-aa2290e729e6status (DMS)

DRFO verification

DRFO status model v2.png

Source:

View file
nameDRFO status model.drawio.xml

Status

Reason

Conditions

Description of target verification status

Method to turn the status

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.

https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249206422
https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249599639 /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)

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.

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

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.https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271128739

RC_DRFO data synchronization for Persons (CSI-2823)

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.https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271128739

RC_DRFO data synchronization for Persons (CSI-2823)

UNZR verification

This status model is valid for UNZR synchronization with EIS MVS register to check whether it is valid or not.

...

Source:

View file
nameUNZR status model for Persons.drawio

Status in the stream

Reason in the stream

Conditions

Description of target verification status

Method to turn the status

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)[NEW] (GraphQL) Update Person UNZR verification status

/wiki/spaces/EDDR/pages/18052349994

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#UNZR-registry-verification

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

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

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

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

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18051334172/PIS.+Confidant+patient+sign-up+registration#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050908197/PIS.+Complete+Update+Person+details#UNZR-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050580524/GraphQL+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

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

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 Persons v2.drawio

Status in the stream

Reason in the stream

Conditions

Description of target verification status

Method to turn the status

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

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/EDDR/pages/18050678807/IL.Sign+person+request#MVS-passport-registry-verification

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

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

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

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18051334172/PIS.+Confidant+patient+sign-up+registration#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050908197/PIS.+Complete+Update+Person+details#MVS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050580524/GraphQL+Update+Person#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/EDDR/pages/18050613264/Sign+person+request+v2#MVS-passport-registry-verification

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

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

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

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

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18051334172/PIS.+Confidant+patient+sign-up+registration#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050908197/PIS.+Complete+Update+Person+details#MVS-passport-registry-verification

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

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

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

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

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 Persons v2.drawio

Status in the stream

Reason in the stream

Conditions

Description of target verification status

Method to turn the status

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/18052251672

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#DMS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050678807/IL.Sign+person+request#DMS-passport-registry-verification

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

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

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

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18051334172/PIS.+Confidant+patient+sign-up+registration#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050908197/PIS.+Complete+Update+Person+details#DMS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050580524/GraphQL+Update+Person#DMS-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/EDDR/pages/18050613264/Sign+person+request+v2#DMS-passport-registry-verification

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050678807/IL.Sign+person+request#DMS-passport-registry-verification

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

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

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

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18051334172/PIS.+Confidant+patient+sign-up+registration#Create-person

https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050908197/PIS.+Complete+Update+Person+details#DMS-passport-registry-verification

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

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

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/18050711556

NOT_VERIFIED

AUTO_NOT_VALID

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

Verification job responded that person's passport is considered not valid 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_VALID

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

Verification job responded that person's passport is considered valid according to the EIS MVS registry

DRACS verification

DRACSG status model.drawio.png

Source:

...