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

DRFO integration data model_EN

Schema

Source file:

Tables

The tables used in the DRFO synchronization process are listed there.

drfo_data

The table in MIMIR db used to store drfo data about person that were received from DRFO registry. Records should not should not store links to mpi.

Name

Type

M/O

Description

Name

Type

M/O

Description

id

uuid

M

 Internal eHealth identifier

rnokpp

varchar(10)

M

Identifier of the person in the DRFO registry. May contain tax ID, passport number, ID passport

last_name

varchar(60)

M

Last name of the person

first_name

varchar(60)

M

First name of the person

middle_name

varchar(60)

O

Second name of the person

date_birth

date

M

Birth date of the person

info_result

smallint

M

Result of InfoRNOKPP call

info_error_message

varchar(255)

O

Error message from InfoRNOKPP call. Returns in Errormsg field if Result != 0

applications

[jsonb]

O

Result of FindRNOKPPQuery call

find_result

smallint

O

Result of FindRNOKPPAnswer call

find_error

smallint

O

Error code from FindRNOKPP (Query or Answer) call. Returns in error field

find_error_message

varchar(255)

O

Error description from FindRNOKPP (Query or Answer) call. Returns in errorMsg field

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 or synchronized with DRFO registry

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 rnokpp:

create unique index drfo_data_rnokpp_index on drfo_data (rnokpp);

person_verifications

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

Model described https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271129363/Person+verification+data+model_EN#person_verifications

party_verifications

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

Model described https://e-health-ua.atlassian.net/wiki/spaces/RNOKPP/pages/17271130356/Party+verification+data+model_EN#party_verifications

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