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

[AUTO] Terminate declaration requests

Owned by sveta vedmed (Unlicensed)
Last updated: Nov 23, 2023 by Dmytro Omelchenko (SoE eHealth)Version comment
1 min read

Purpose

  1. All the declaration_requests that hasn't been completed in time should be expired.

  2. Personal data in declaration_requests should be automatically deleted according to the global parameters configuration. In order not to store personal data in the declaration_requests longer than it is allowed by the law.

Global parameters

declaration_request_expiration

declaration_request_term_unit

 logic

 

Description

Value

Description

Value

(Cron Format) How often to perform termination

0 0 0 1/1 * ? *

Expiration

If declaration_request.inserted_at > now() - declaration_request_expiration and status in ('NEW', 'APPROVED')

  • delete some personal data in declaration_requests: data, authentication_method_current, printout_content, data_legal_entity_id, data_employee_id, data_person_tax_id, data_person_first_name, data_person_first_name, data_person_birth_date.

  • update declaration_requests

    • status –> EXPIRED

    • status_reason: request_overdue

    • updated_by = SYSTEM_USER

    • updated_at = timestamp

Data clean up

If declaration_request.inserted_at > now() - declaration_request_expiration and data is not NULL:

  • delete some personal data in declaration_requests: data, authentication_method_current, printout_content, data_legal_entity_id, data_employee_id, data_person_tax_id, data_person_first_name, data_person_first_name, data_person_birth_date.

  • update declaration_requests

    • updated_by = SYSTEM_USER

    • updated_at = timestamp

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