ЕСОЗ - публічна документація

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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 specific NHS manual rules.

  • independent status flows for each stream (verification with registers or according to specific NHS rules (e.g. NHS manual verification rules - set of specific verification controls implemented to creation/update of persons records and authentication methods)

Cumulative verification status has simplified status flow with three statuses.

  1. NOT_VERIFIED - if any 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

Verification status

Conditions

Description

NOT_VERIFIED

(DRFO verification status = ‘NOT_VERIFIED’)

OR

(DRACS death acts verification status = ‘NOT_VERIFIED’)

OR

(Manual NHS verification status = ‘NOT_VERIFIED’)

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

VERIFIED

(DRFO verification status = ‘VERIFIED’)

AND

(DRACS death acts verification status = ‘VERIFIED’)

AND

(Manual NHS 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’)

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

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 reasonRULES_TRIGGERED

Manual change of verification status is invoked.

Means that person is being verified by NHS employee

(GraphQL) Update Person verification status

NOT_VERIFIED

MANUAL

Person has verification status IN_REVIEW

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

Comment is required.

(GraphQL) Update Person verification status

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.

(GraphQL) Update Person verification status

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.
Create/Update person has been invoked.

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

IL.Sign person request
(GraphQL) Update Person in NHS Admin

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.

DRFO verification job

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.

DRFO verification job

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.

DRFO verification job

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

IL.Sign person request

(GraphQL) Update Person in NHS Admin

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
VERIFICATION_NEEDED

MANUAL_NOT_CONFIRMED
MANUAL_CONFIRMED

Person has verification status NOT_VERIFIED

MIS user conducts verification.

Person marked as verified with appropriate reason by a MIS user

Update Person verification status

IN_REVIEW

MANUAL

Person with

  • verification status VERIFICATION_NEEDED with on of the reasons MANUAL_NOT_CONFIRMED,
    MANUAL_CONFIRMED or

  • person without a declaration has verification status NOT_VERIFIED with one of the reasons AUTO_ONLINE, AUTO_OFFLINE

  • person with a declaration, but was not verified by a Doctor or medical employee during parametrized period (for example 30 days)

 

Manual change of verification status is invoked.

Means that person is being verified by NHS employee

(GraphQL) Update Person verification status

NOT_VERIFIED

MANUAL

Person has verification status IN_REVIEW

Multi purpose action:

  • either NHS employee has concerns regarding provided feedback by a Doctor or medical/employee

  • or it is not possible to make a decision about possible related death acts (grey zone) at a moment and it will allow to postpone blocking of patient record for certain time.

(GraphQL) Update Person verification status

VERIFIED

MANUAL_NOT_CONFIRMED
MANUAL_CONFIRMED

Person has verification status IN_REVIEW

  • MANUAL_NOT_CONFIRMED. Describes that person is verified manually and found by the system death acts does not corresponds to that person

  • MANUAL_CONFIRMED. Describes that person is verified manually and there is one active death act, related to the person

Comment will be set to NULL in DB.

(GraphQL) Update Person verification status

VERIFIED

OFFLINE_VERIFIED

prerequisites

  • All death acts for 2014-2022 period were downloaded from DRACS register and processed by eHealth system's Offline verification process and

  • persons are still in status VERIFICATION_NEEDED with reason INITIAL after processed 2014-2022 death acts

One time migration for such persons to VERIFIED status with OFFLINE_VERIFIED reason)

To be conducted within system support process.

  • No labels