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

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 6 Next »

REST API method / Метод REST API (настанова) (remove the link block before publishing the document)

Properties of a REST API method document

Document type

Метод REST API

Document title

[Document status] REST API [Назва методу] [ID методу]

Guideline ID

GUI-0011

Author

@

Document version

1

Document status

DRAFT

Date of creation

ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD)

Date of update

ХХ.ХХ.ХХХХ (дата зміни версії)

Method API ID

API-005-009-003-0188

Microservices (namespace)

IL

Component

Legal Entities

Component ID

COM-005-009

Link на API-специфікацію

https://ehealthmisapi1.docs.apiary.io/#reference/public.-medical-service-provider-integration-layer/licenses/create-license

Resource

{{host}}/api/licenses

Scope

license:write

Protocol type

REST

Request type

POST

Sync/Async

Sync

Public/Private

Public

Purpose

This WS allows to create a license for a legal entity

Key points

  1. Only authenticated and authorized user with an appropriate scope can create licenses.

  2. The license can be created for PRIMARY_CARE, EMERGENCY, OUTPATIENT, or PHARMACY legal entity.

  3. The license can be created for legal entities in ACTIVE or SUSPENDED statuses.

  4. Only an additional license can be created with this WS.

  5. The additional license can be created for legal entities with an active primary license.

Logic

Save new license in licenses table (PRM DB)

Configuration parameters

N/A

Dictionaries

  • LICENSE_TYPE

  • LEGAL_ENTITY_<LEGAL_ENTITY_TYPE>_ADDITIONAL_LICENSE_TYPES

Input parameters

Input parameter

Mandatory

Type

Description

Example

1

2

Request structure

See on API-specification

 Example
{
  "type": "MSP",
  "license_number": "fd123443",
  "issued_by": "Кваліфікацйна комісія",
  "issued_date": "2022-02-28",
  "expiry_date": "2026-02-28",
  "active_from_date": "2022-02-28",
  "what_licensed": "реалізація наркотичних засобів",
  "order_no": "ВА43234",
  "is_primary": false
}

Headers

Headers

Request data validation

Authorize

  • Verify the validity of access token

    • in case of error - return 401 (“Invalid access token”) in case of validation fails

  • Verify that token is not expired

    • in case of error - return 401 (“Invalid access token”)

  • Check user scopes in order to perform this action (scope = 'license:write')

    • return 403 (“Your scope does not allow to access this resource. Missing allowances: license:write”) in case of invalid scope(s)

Validate request

  • Validate request using JSON schema

    • in case of error - return 422

Validate legal entity

  • Extract legal entity id from access token. Check that legal entity is in ‘ACTIVE’ or ‘SUSPENDED’ status

    • in case of error - return 422 (“Legal entity must be in active or suspended status”)

Validate license type

  • Check that additional license was passed in request ($.is_primary = false)

    • in case of error - return 422 (“Only additional license can be created”)

  • Check that license type in request exists in LICENSE_TYPE dictionary

    • in case of error - return 422 (“value is not allowed in enum”)

  • Check that license type in request exists in chart parameter LEGAL_ENTITY_<LEGAL_ENTITY_TYPE>_ADDITIONAL_LICENSE_TYPES based on legal entity type

    • in case of error - return 409 (“Legal entity type and license type mismatch")

  • Check that legal entity has active primary license (request: select id from licenses where is_active=true and is_primary=true and legal_entity_id=$.legal_entity.id and (expiry_date >= current_date() or expiry_date is null); returns at least one value)

    • in case of error - return 404 (“No active primary license found for legal entity”)

  • Check that legal entity does not have license with type same as in request ($.type)

    • in case of error - return 409 (“License with type $.type is already present”) where $.type = license type from request

Validate license dates

  • Check that $.issued_date is not greater than $.active_from_date

    • in case of error - return 422 (“License can not be issued later than active from date”)

  • Check that $.active_from_date is not greater than $.expiry_date

    • in case of error - return 422 (“License can not have active from date later than expiration date”)

  • Check that $.expiry_date is not lesser than current_date

    • in case of error - return 409 (“License is expired”)

Processing

N/A

Response structure examples

See on Apiary

See on API-specification

 Example
{
  "meta": {
    "code": 200,
    "url": "https://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  },
  "data": {
    "id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
    "type": "MSP",
    "license_number": "fd123443",
    "issued_by": "Кваліфікацйна комісія",
    "issued_date": "2022-02-28",
    "expiry_date": "2026-02-28",
    "active_from_date": "2022-02-28",
    "what_licensed": "реалізація наркотичних засобів",
    "order_no": "ВА43234",
    "legal_entity_id": "28d9c1be-08f0-403b-aa76-bff228c9904f",
    "is_primary": true
  }
}

HTTP status codes

Response code

HTTP Status code

Message

Internal name

Description

1

Базові

2

201

Response

 

3

401

Invalid access token

 

4

403

Your scope does not allow to access this resource. Missing allowances: license:write

 

5

404

No active primary license found for legal entity

 

6

409

Legal entity type and license type mismatch

 

7

409

License with type $.type is already present

8

409

License is expired

9

422

Legal entity must be in active or suspended status

 

10

422

License can not be issued later than active from dateLicense can not have active from date later than expiration date

11

422

License can not have active from date later than expiration date

12

422

Only additional license can be created

13

422

Value is not allowed in enum

14

Специфічні

15

Post-processing processes

N/A

Technical modules where the method is used

  • No labels