Purpose

The method is designed to obtain information on the integration processes of interaction with third-party registries in the context of compositions. When composition data is transferred to an external registry and processed there, the method returns the status of data processing by the third-party registry.

Integration with the following third-party registries is implemented:

• Electronic sick leave register (ERLN) - for MVTN (temporary desability).

• State register of acts of civil status of citizens (DRACSG) - for MVN (newborn).

Also, the method transmits integration data of DIIA processing.

Getting integration data processes depends on the type of composition.

Used in processes:

Create/Sign composition (general process)

Extension / reduction MVTN

Refinement (preperson -> person) for MVTN

Creating "a replacement" composition

Specification

Preconditions

• The method can only be executed by a user with access to composition.

• The method can only be executed for a composition with the status:

  • FINAL

  • AMENDED

  • ENTERED_IN_ERROR

Logic

1. An authorized user with MIS creates and signs a composition, information from which can be used in a third-party registry.

2. The signed composition is stored in the ESOZ.

3. An authorized user can make a request and receive in response the status of processing in a third-party register.

Configurable parameters

Link to page with configurable parameters

VAR NAME:

• EMAL_INTEGRATION_NEWBORN_CLIENTS_MEMBER_CODE_NAMES (Mapping request components by getComposition MVN (integration data))

Input parameters

Dictionaries

• COMPOSITION_PROCESSING_STATUS (parameter “integrationStatus“ in response)

• COMPOSITION_PROCESSING_SYSTEMS (parameter “component“ in response):

• COMPOSITION_PROCESSING_TASKS (parameter “type“ in response):

• COMPOSITION_PROCESSING_TASK_STATUS (parameter “taskStatus“ in response):

• ERLN_RESULT_CODES (parameters “statusCode“ and “statusMessage“ in response - for ERLN only):

Request structure

See on SwaggerHub (2.39.2)

Description:

Authorize

A token in the headers.

Check user scopes in order to perform this action (scope = 'composition:read')

• return 401 (Unauthorized) in case of invalid scope(s)

Headers

• Content-Type: application/json

• Authorization: Bearer {token}

• api-key: {secret}

Response structure

See on SwaggerHub

In addition to parameters from the Dictionaries, the response contains the following subparameters, depending on parameter values:

1. “updatedAt” - the date of the last update of the status of the integration process

2. “details“ - the data set defined by the integration component:

   1. “component“: “MJU_DRACZ“

      1. "type": "NEWBORN_POST_COMPOSITION"

         1. “personId“ - the identifier of the created record about the identified child.

   2. “component“: “ERLN“

      1. "type": "CREATE_ERLN_RECORD”

         1. “SL_NUM” - ELN registration number

         2. “SL_REG_DATETIME” - ELN registration date and hour

         3. “SL_STOP” - ELN closing date

         4. “SL_START” - ELN open (extension) date

         5. “IC_NUM” - Number of temporary disability case

      2. "type": "CANCEL_ERLN_RECORD”

         1. "SL_NUM" - ELN registration number

         2. "SL_REG_DATETIME" - ELN registration date and hour

         3. "IC_NUM" - Number of temporary disability case

Response examples:

• Creation of composition type “temp_disability“. Response with information on the ERLN integration process:

• Creation of composition type “newborn“. Response with information on DIIA integration process:

• Creation of composition type “newborn“. Response with information on DRACSG integration process:

• Cancellation of composition type “temp_disability“. Response with information on the ERLN integration process:

HTTP status codes