ЕСОЗ - публічна документація
RC_Confidant person relationship data model (DRACS 2.0)
Schema
Source:
Tables
confidant_person_relationships
The table in MPI db is used to store relationships between persons (Confidant Patients and Related Patients)
Name | Type | M/O | Description |
---|---|---|---|
id | uuid | M | System identifier of the relationship between persons |
confidant_person_id | uuid | M | Person mpi identifier of Confidant Patient |
person_id | uuid | M | Person mpi identifier of Related Patient |
is_active | boolean | M | Status if the relationship is active or not |
active_to | datetime | O | Date the record will become inactivate |
verification_status | varchar | M | Verification status according to dictionary |
verification_reason | varchar | M | Reason of the verification status according to dictionary |
verification_comment | varchar | O | Comment for the verification status |
unverified_at | datetime | O | Date and time of confidant person relationship verification status change to ‘NOT_VERIFIED’ |
dracs_birth_act_id | uuid | O | Identifier of the record from mimir.dracs_birth_acts |
dracs_birth_synced_at | datetime | O | Date and time of the last synchronization with DRACS birth acts registry |
inserted_by | uuid | M | User who triggered the record creation (system user if job; employee user if online using person request or api calls from admin panel). |
updated_by | uuid | M | User who triggered the record update (system user if job; employee user if online using person request or api calls from admin panel). |
inserted_at | datetime | M | Date and time the record was created |
updated_at | datetime | M | Date and time the record was updated |
confidant_person_relationship_documents
The table in MPI db is used to store documents that prove relationships between persons
Атрибут | Type | M/O | Description |
---|---|---|---|
id | uuid | M | System identifier of the relationship between persons |
confidant_person_relationship_id | uuid | M | Mpi identifier of the relationship between persons (confidant_person_relationships db) |
type | varchar | M | Document type according to dictionary |
number | varchar | M | Document number |
issued_at | varchar | O | Document compose date |
issued_by | varchar | O | Organization that composed the document |
active_to | date | O | Document finish date |
inserted_by | uuid | M | User who triggered the record creation (system user if job; employee user if online using person request or api calls from admin panel). |
updated_by | uuid | M | User who triggered the record update (system user if job; employee user if online using person request or api calls from admin panel). |
inserted_at | datetime | M | Date and time the record was created |
updated_at | datetime | M | Date and time the record was updated |
confidant_person_relationship_verification_candidates
The table in MPI db is used to store links between confidant_person_relationship_id and entities that were created as the result of comparing person and relationship data with external registries
Name | Type | M/O | Description |
---|---|---|---|
id | uuid | M | Internal record identifier |
confidant_person_relationship_id | uuid | M | Confidant person relationship 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:
|
status | varchar | M | Status of verification candidate Values:
|
status_reason | varchar | O | Optional reason of verification candidate status Values:
|
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 |
ЕСОЗ - публічна документація