ЕСОЗ - публічна документація
Party verification status model
- Viacheslav Tybin (SoE eHealth)
- Yuliia Mazur (UA SoE eHealth)
Cumulative verification status
Cumulative verification status in prm.parties.verification_status
Cumulative verification status is implemented. It allows:
achieve scalable verification data model for future needs of verification with other external registers
reflect general status of verification of parties' data with external national registers and according specific NHS manual rules
independent status flows for each stream (verification with registers or according to specific NHS rules)
Cumulative verification status has simplified status flow with three statuses:
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
Verification status | Conditions | Description |
|---|---|---|
NOT_VERIFIED | (DRFO verification status = 'NOT_VERIFIED') OR (DRACS death acts 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') | 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') | At least one of the stream for Party is not in final status ('VERIFIED' or 'NOT_VERIFIED') |
DRFO verification
Status | Reason | Conditions | Description of target verification status | Method to turn the status |
|---|---|---|---|---|
|
| 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. |
|
| Any verification status. | Marks parties as those requiring immediate verification because their data has been changed. | Approve or Reject employee Request https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249206457 (Private) |
|
| Any verification status. DRFO verification job has started by schedule. | Marks party that are processing by the DRFO verification job at the moment. | |
|
| Party has verification status | 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. | |
|
| Party has verification status | Verification job responded that party’s data is valid and present in the DRFO registry. Correction from MIS is not required. |
DRACS verification
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. | Marks parties as those requiring immediate verification because their data has been changed. | Approve or Reject employee Request https://e-health-ua.atlassian.net/wiki/spaces/DRACS/pages/17249206457(Private) |
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 | Party has verification status NOT_VERIFIED MIS user conducts verification. | Party marked as verified with appropriate reason by a MIS user | |
VERIFIED | OFFLINE_VERIFIED | Prerequisites
| 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 |
ЕСОЗ - публічна документація