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

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

Version 1 Current »

Schema

Source file:

Tables

person_verifications

The table in MPI db is used to store results of synchronization with external registries that characterizes a person

Name

Type

M/O

Description

id

uuid

M

Internal eHealth identifier

person_id

uuid

M

Person mpi identifier, unique

drfo_data_id

uuid

O

Identifier of the record from mimir.drfo_data

drfo_data_result

smallint

O

Result of the last synchronization with DRFO. Value according to DRFO_RESULT dictionary

drfo_synced_at

datetime

O

Date and time of the last synchronization with DRFO

drfo_verification_status

varchar

M

Verification status according to DRFO for the current person

drfo_verification_reason

varchar

M

Reason of the DRFO verification status

dracs_death_act_id

uuid

O

Identifier of the record from mimir.dracs_death_acts

dracs_death_online_status

varchar

M

Online sync status with DRACS death acts registry for the current person

Values:

  • READY

  • IN_PROCESS

  • COMPLETED

dracs_death_verification_status

varchar

M

Verification status according to DRACS death acts for the current person

dracs_death_verification_reason

varchar

M

Reason of the DRACS death acts verification status

dracs_death_verification_comment

varchar

O

Comment for DRACS death acts verification status

nhs_verification_status

varchar

M

Verification status according to manual NHS rules for the current person

nhs_verification_reason

varchar

M

Reason of the manual NHS rules verification status

nhs_verification_comment

varchar

O

Comment for manual NHS rules verification status

inserted_at

datetime

M

Date and time the record was created

inserted_by

uuid

M

User who triggered the record creation (system user if job; employee user if online using person request or DRFO api calls from admin panel).

updated_at

datetime

M

Date and time the record was updated

updated_by

uuid

M

User who triggered the record update (system user if job; employee user if online using person request or DRFO api calls from admin panel).

Assumed unique constraint on person_id:

create unique index person_verifications_person_id_index
    on person_verifications (person_id);

person_verification_candidates

The table in MPI db is used to store links between person_id and dracs_death_act_id that were created as the result of comparing persons data with death act data

Name

Type

M/O

Description

id

uuid

M

Internal record identifier

person_id

uuid

M

Person mpi identifier, unique

entity_id

uuid

M

Identifier of entity that created candidate, type is specified in entity_type field

entity_type

varchar

M

Type of entity that triggered verification candidate pair

Values:

  • dracs_death_act

status

varchar

M

Status of verification candidate

Values:

  • NEW

  • CONFIRMED

  • NOT_CONFIRMED

  • DEACTIVATED

status_reason

varchar

O

Optional reason of verification candidate status

Values:

  • PERSON_UPDATED

  • DEATH_ACT_UPDATED

  • PERSON_DEACTIVATED

config

jsonb

O

Variables that were used in comparison process

details

jsonb

O

Additional details of comparison process

score

float

O

Logistic regression comparison score

inserted_at

timestamp

M

Date and time the record was created

updated_at

timestamp

M

Date and time the record was updated

  • No labels