General
All the data received from EDR must be stored locally as an evidence. It could be used for investigations, monitoring approaches and as a source for FE comparison
Storage data model
EDR_VERIFICATIONS
DB: prm
Table name: edr_verifications
| Parameter | Type | M/O | Description |
|---|---|---|---|
| id | uuid | M | Unique record identifier |
| legal_entity_id | uuid | M | |
| status_code | varchar(3) | O | HTTP Response code received from EDR API |
| edr_status | varchar(30) | O | Verification result based on predefined rules IL.Create/Update Legal Entity#EDRValidation Enum:
|
| edr_state | integer | O | State of Legal Entity in EDR |
| edr_data | jsonb | O | Data received from EDR |
| legal_entity_data | jsonb | O | |
| inserted_at | timestamp | M | Inserted datetime |
| error_message | text | O | Error message Error raised on ehealth side |
MV_EDR_VERIFICATIONS
DB: prm
Type: materialized view
View name: mv_edr_verifications
| Parameter | Type | M/O | Description |
|---|---|---|---|
| legal_entity_id | uuid | M | |
| edr_data | jsonb | O | EDR response converted to required structure See. EDR_DATA_STRUCTURE |
| legal_entity_data | jsonb | O | Legal entity data converted to required structure See. LEGAL_ENTITY_DATA_STRUCTURE |
| last_verified_date | timestamp | M | Last verified date |
| verification_result | varchar(30) | M |