Cumulative verification status
Cumulative verification status in mpi.persons.verification_status
Source:
Cumulative verification status is implemented. It allows
achieve scalable verification data model for future needs of verification with other external registers
to reflect general status of verification of persons' data with external national registers and according to specific NHS manual rules.
independent status flow for each stream (verification with registers; according to specific NHS manual verification controls and rules, which are implemented to creation/update of persons records and authentication methods)
Cumulative verification status has simplified status flow with four statuses.
CHANGES_NEEDED - if any of streams has got NOT_VERIFIED status
VERIFIED - if all registers/streams have got VERIFIED status
VERIFICATION_NEEDED - if any verification stream has not got a final status as VERIFIED or NOT_VERIFIED
NOT_VERIFIED - if manually has been set into DB
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 |
NHS manual verification rules
Source:
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 | |
NOT_VERIFIED | MANUAL | Person has verification status IN_REVIEW | Describes that person's info is incomplete and correction from MIS needed. Comment is required. | |
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. |
DRFO verification
Source:
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. | Marks persons as those requiring immediate verification because their data has been changed. | https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249206422 |
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 |
NOT_VERIFIED | AUTO | Person has verification status IN_REVIEW | 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 |
VERIFIED | AUTO | Person has verification status IN_REVIEW | 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 |
UNZR verification
This status model is valid for UNZR synchronization with EIS MVS register to check whether it is valid or not.
Source:
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. | Marks persons as those requiring immediate re-verification (w/o person’s data update) | |
VERIFICATION_NEEDED | ONLINE_TRIGGERED | Any verification status. | Marks persons as those requiring immediate verification because their data has been changed. | |
VERIFICATION_NOT_NEEDED | AUTO | Any verification status. | 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 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 |
|
|
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:
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. | Marks persons as those requiring immediate re-verification (w/o person’s data update) | |
VERIFICATION_NEEDED | ONLINE_TRIGGERED | Any verification status. | Marks persons as those requiring immediate verification because their data has been changed. | |
VERIFICATION_NOT_NEEDED | AUTO_DATA_ABSENT | Any verification status. | 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/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 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 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:
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. | Marks persons as those requiring immediate re-verification (w/o person’s data update) | |
VERIFICATION_NEEDED | ONLINE_TRIGGERED | Any verification status. | Marks persons as those requiring immediate verification because their data has been changed. | |
VERIFICATION_NOT_NEEDED | AUTO_DATA_ABSENT | Any verification status. | 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/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 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 responded that person's passport is considered valid according to the EIS MVS registry |
DRACS verification
Source:
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 with DRACS register (by online or offline verification process). | By migration procedure |
VERIFICATION_NEEDED | ONLINE_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 as those requiring verification with online DRACS register | https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249206422 https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249599639 |
VERIFIED | AUTO_ONLINE AUTO_OFFLINE | Person has verification status VERIFICATION_NEEDED,IN_REVIEW, NOT_VERIFIED, VERIFIED | Marks person as VERIFIED in case related death act is found, or in case Job 1 has not found any related act. Comment will be set to NULL in DB. | Two jobs conducts verification of a persons:
|
NOT_VERIFIED | AUTO_ONLINE AUTO_OFFLINE | Person has verification status VERIFICATION_NEEDED,IN_REVIEW, NOT_VERIFIED, VERIFIED | Marks person as NOT_VERIFIED in case JOB1 and/or JOB2 found possible related death act(s) (grey zone) Comment will be set to NULL in DB. | Two jobs conducts verification of a persons:
|
VERIFIED | MANUAL_NOT_CONFIRMED | Person has verification status NOT_VERIFIED MIS user conducts verification. | Person marked as verified with appropriate reason by a MIS user | |
IN_REVIEW | MANUAL | Person with
Manual change of verification status is invoked. | Means that person is being verified by NHS employee | https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17251991577 |
NOT_VERIFIED | MANUAL | Person has verification status IN_REVIEW | Multi purpose action:
| https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17251991577 |
VERIFIED | MANUAL_NOT_CONFIRMED | Person has verification status IN_REVIEW |
Comment will be set to NULL in DB. | https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17251991577 |
VERIFIED | OFFLINE_VERIFIED | prerequisites
| One time migration for such persons to VERIFIED status with OFFLINE_VERIFIED reason) | To be conducted within system support process. |