Table of Contents |
---|
...
Then person will be verified online with DRFO registry via separate process: /wiki/spaces/RNOKPP/pages/17158275099 RC_DRFO data synchronization for Persons (CSI-2823)
DRACS death acts registry verification
...
Then person will be verified online with DRACS death acts registry via separate process: https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249763472
MVS passport registry verification
If person’s data match following rules: person has document with type ‘PASSPORT’ or ‘NATIONAL_ID’ (check in Request, within $.person.documents)
thenonline verification with MVS passports registry needed. Set to person verification record:
mvs_passport_data_id = NULL
mvs_passport_data_status = NULL
mvs_passport_synced_at = NULL
mvs_passport_verification_status = VERIFICATION_NEEDED
mvs_passport_verification_reason = ONLINE_TRIGGERED
Then person will be verified online with MVS passports registry via separate process: https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050908162
If person’s data does not match rules from above – online verification with MVS passports registry is not needed. Set to person verification record:
mvs_passport_data_id = NULL
mvs_passport_data_status = NULL
mvs_passport_synced_at = NULL
mvs_passport_verification_status = VERIFICATION_NOT_NEEDED
mvs_passport_verification_reason = AUTO_DATA_ABSENT
DMS passport registry verification
If person’s data match following rules: person has document with type ‘PASSPORT’ or ‘NATIONAL_ID’ (check in Request, within $.person.documents)
thenonline verification with DMS passports registry needed. Set to person verification record:
dms_passport_data_id = NULL
dms_passport_data_status = NULL
dms_passport_synced_at = NULL
dms_passport_verification_status = VERIFICATION_NEEDED
dms_passport_verification_reason = ONLINE_TRIGGERED
Then person will be verified online with DMS passports registry via separate process: https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050711556
If person’s data does not match rules from above – online verification with DMS passports registry is not needed. Set to person verification record:
dms_passport_data_id = NULL
dms_passport_data_status = NULL
dms_passport_synced_at = NULL
dms_passport_verification_status = VERIFICATION_NOT_NEEDED
dms_passport_verification_reason = AUTO_DATA_ABSENT
UNZR registry verification
If person’s data match following rules: ‘unzr’ is submitted and is not null (check in Request, within $.person.unzr)
thenonline verification with UNZR registry needed. Set to person verification record:
unzr_data_id = NULL
unzr_data_status = NULL
unzr_synced_at = NULL
unzr_verification_status = VERIFICATION_NEEDED
unzr_verification_reason = ONLINE_TRIGGERED
Then person will be verified online with UNZR registry via separate process: https://e-health-ua.atlassian.net/wiki/spaces/EDDR/pages/18050351106
If person’s data does not match rules from above – online verification with UNZR registry is not needed. Set to person verification record:
unzr_data_id = NULL
unzr_data_status = NULL
unzr_synced_at = NULL
unzr_verification_status = VERIFICATION_NOT_NEEDED
unzr_verification_reason = AUTO
Calculate cumulative verification status
Calculate persons cumulative verification status based on persons verification status in each stream: Manual NHS verification, DRFO registry verification, DRACS death acts registry verification, MVS passport registry verification, DMS passport registry verification,UNZR registry verification according to logic described at https://e-health-ua.atlassian.net/wiki/spaces/EDDREH/pages/1804848339116755458061/Person+verification+status+model#Cumulativemodel_EN#Cumulative-verification-status :
Set calculated status to persons.verification_status field
Create StatusChangeEvent in event manager with new verification status if it was changed