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

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 9 Next »

General

Release 1

  1. DLS Registry is managed by NHS
  2. DLS Registry must be updated in eHealth daily by NHS (DB inserts, DB updates)
  3. eHealth processes DLS Replica daily to reflect division statuses

DLS Replica structure

DB: DLS

Table: dls_registry

ParameterTypeM/ODescription
division_iduuidMDivision identifier in eHealth
dls_idvarchar(20)MDLS identifier
dls_statusvarchar(50)MDLS status
inserted_attimestampM

DLS Processor

Each record from DLS Replica must be processed

  1. Find division in PRM using replica division_id
    1. In case division by id not found - log error (including id) and skip this record
  2. Update only divisions with type DRUGSTORE and DRUGSTORE_POINT
PRM.divisionsDLS.dls_registry
dls_iddls_id
dls_statusdls_status

DLS statuses

There are two DLS statuses: ACTIVE and INACTIVE. Status changes is managed by the NHS side and goes through such a process:

  1. Initial status changed in DLS Registry by NHS side

  2. The DLS registry is updated daily by the eHealth service (DB inserts, DB updates)

  3. eHealth processes DLS Replica daily to reflect DLS statuses

  4. From DLS registry statuses are replicated in PRM DB

References


Deactivate Medical Program Provision

In case division becomes not verified in DLS (dls_verified=false) (according to link)

  1. If DISPENSE_DIVISION_DLS_VERIFY chart parameter is on:

    • deactivate related to the division all active medical program provision entities:

      • set is_active = false

      • set deactivate_reason = AUTO_DIVISION_DLS_NOT_VERIFIED 

      • set updated_at, updated by 

  2. If DISPENSE_DIVISION_DLS_VERIFY is off, then skip this event

  • No labels