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

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 2 Current »

Service logic

  1. Update device request status to completed (update also updated_at, updated_by)

  2. Get person's authentication_method according to logic:

    1. If authorize_with inform_with exists in device request and is not empty, check:

      1. Authentication method exists in person_authentication_methods table in MPI DB (with is_active=true), is active (ended_at > now() or null)

      2. Get value of THIRD_PERSON_CONFIDANT_PERSON_RELATIONSHIP_CHECK config parameter, if it is set to true - for authentication method with type = THIRD_PERSON check that person from value is an approved confidant for a person from device request – exists active and approved confidant person relationship between person from request and confidant_person_id from authentication method value (using following logic /wiki/spaces/CSI/pages/17667883028 with person_id = person from request and confidant_person_id = value from auth method - expected :ok, :approved response)

        1. in case any validation failed - do not send SMS to person

        2. else - get authentication_method from authorize_with inform_with

    2. If authorize_with inform_with does not exist in device request or is empty - get default authentication_method of person from MPI using logic https://e-health-ua.atlassian.net/wiki/spaces/CSI/pages/17613029453

  3. If authentication_method == OTP or THIRD_PERSON (with OTP) :

    1. Check if sms notifications are enabled:

      1. check config parameter DEVICE_REQUESTS_SMS_ENABLED is set in true

        1. else return an error 409 “Action is disabled by the configuration”

      2. Generate text SMS with template COMPLETE_DEVICE_REQUEST_SMS_TEMPLATE.

      3. Send SMS

  4. Save internal information to corresponding DB

  5. Send StatusChangeEvent to the Event Manager

  • No labels