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

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 4 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-007-002-002-0232

Microservices (namespace)

ME

Component

Devices and equipment

Component ID

COM-007-002

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

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

Resource

{{host}}/api/equipment

Scope

equipment:write

Protocol type

REST

Request type

POST

Sync/Async

Sync

Public/Private

Public

Purpose

This WS is designed for registration equipment in divisions of legal entities

Logic

  1. Only authenticated and authorized HR, ADMIN, OWNER employees can register equipments.

  2. Equipments can be registered in MSP, OUTPATIENT, PRIMARY_CARE and EMERGENCY legal entities.

  3. Equipment has to be linked to division. One division can have many equipments.

  4. Legal entity can register equipments for its own divisions only.

Configuration parameters

Description of the configuration parameters that are used when processing a request in the system

Dictionaries

Provides a list of links to dictionaries that are available in Confluence

Input parameters

Description of input parameters

Input parameter

Mandatory

Type

Description

Example

1

composition_id

 M

String ($uuid) (path)

Composition object ID

 89678f60-4cdc-4fe3-ae83-e8b3ebd35c59

2

Request structure

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API request structure, example

 Example
{
  "division_id": "8be63914-a278-470b-b868-1af5b9087332",
  "type": "23143534",
  "external_id": "123-ASD-#1",
  "udi": [
    {
      "value": "IMEI 49015420323751",
      "type": "default",
      "assigner_name": "Ukrainian center of the certification"
    }
  ],
  "lot_number": "RZ12345678",
  "manufacturer": "GlobalMed, Inc",
  "manufacture_date": "1999-01-01",
  "expiration_date": "2020-01-01",
  "model_number": "NSPX30",
  "part_number": "#e30-SD",
  "version": "v1.0.1",
  "name": "Рентген апарат флюрографічній",
  "serial_number": "S/N234554",
  "note": "Технічний огляд раз на рік"
}

Headers

Key

Value

Mandatory

Description

Example

1

Content-Type

application/json

M

Тип контенту

Content-Type:application/json

2

Authorization

Bearer c2778f3064753ea70de870a53795f5c9

Authorization:Bearer c2778f3064753ea70de870a53795f5c9

3

API-key

uXhEczJ56adsfh3Ri9SUkc4en

API-key:uXhEczJ56adsfh3Ri9SUkc4en

Request data validation

Validate legal entity

Check that legal entity is active (status = ACTIVE, SUSPENDED)

  1. Extract client_id from token (token.client_id == legal_entity_id)

  2. Check legal entity status (status = ACTIVE, SUSPENDED)

    1. In case of error - return 409 (Legal entity must be ACTIVE or SUSPENDED)

Validate request

Validate request using schema

Validate division

A division_id should be passed in request body:

  1. Validate division_id in request body - division exists and is_active = true

    1. Return 422 in case validation fails

  2. Check division_id belongs to the same legal_entity_id (from token) as the user

    1. Return 422 with message  "Division is not within current legal entity" in case validation fails.

  3. Check division status =ACTIVE.

    1. Return 422 with message "Division is not active" in case validation fails.

Validate type

  1. Validate that an equipments type value exists in dictionary "EQUIPMENT_TYPE"

    1. in case of error "Submitted code is not allowed for this field"

Validate external identifier 

  1. Check an external_id field is not empty

    1. Return 422 (required property external_id was not present) in case of error

Processing

Save object to DB

1. equipments table

Parameter

Source

Description

id

UUID

Autogenerated

type

Request: type

Get from request body

external_id

Request: external_id

Get from request body

division_id

Request: division_id

Get from request body

udi

Request: udi

Get from request body

lot_number

Request: lot_number

Get from request body

manufacturer

Request: manufacturer

Get from request body

manufacture_date

Request: manufacture_date

Get from request body

expiration_date

Request: expiration_date

Get from request body

model_number

Request: model_number

Get from request body

part_number

Request: part_number

Get from request body

version

Request: version

Get from request body

name

Request: name

Get from request body

serial_number

Request: serial_number

Get from request body

note

Request: note

Get from request body

legal_entity_id

Token: client_id

Extract client from token

status

Const: ACTIVE

By default ACTIVE for new records

is_active

Const: TRUE

Always TRUE for new records

inserted_at

Timestamp: now()

Get current date-time

inserted_by

Token: user_id

Extract user from token

updated_at

Timestamp: now()

Get current date-time

updated_by

Token: user_id

Extract user from token

2. equipment_status_hstr table

Parameter

Source

Description

id

UUID

Autogenerated

equipment_id

UUID

Reference to equipments.id

status

Const: ACTIVE

By default ACTIVE for new records

inserted_by

Token: user_id

Extract user from token

inserted_at

Timestamp: now()

Get current date-time

Response structure examples

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API response structure, example

 Example
{
  "meta": {
    "code": 201,
    "url": "https://example.com/resource",
    "type": "object",
    "request_id": "6617aeec-15e2-4d6f-b9bd-53559c358f97#17810"
  },
  "data": {
    "id": "7c3da506-804d-4550-8993-bf17f9ee0402",
    "division_id": "8be63914-a278-470b-b868-1af5b9087332",
    "legal_entity_id": "483af06f-d4c6-4c9e-8d9b-680b5ef7270d",
    "type": "23143534",
    "external_id": "123-ASD-#1",
    "udi": [
      {
        "value": "IMEI 49015420323751",
        "type": "default",
        "assigner_name": "Ukrainian center of the certification"
      }
    ],
    "lot_number": "RZ12345678",
    "manufacturer": "GlobalMed, Inc",
    "manufacture_date": "1999-01-01",
    "expiration_date": "2020-01-01",
    "model_number": "NSPX30",
    "part_number": "#e30-SD",
    "version": "v1.0.1",
    "name": "Рентген апарат флюрографічній",
    "serial_number": "S/N234554",
    "note": "Технічний огляд раз на рік",
    "status": "ACTIVE",
    "is_active": true,
    "inserted_at": "2017-04-20T19:14:13Z",
    "inserted_by": "e1453f4c-1077-4e85-8c98-c13ffca0063e",
    "updated_at": "2017-04-20T19:14:13Z",
    "updated_by": "2922a240-63db-404e-b730-09222bfeb2dd"
  }
}

HTTP status codes

Response code

HTTP Status code

Message

Internal name

Description

1

Базові

2

201

 Response

 

3

401

 

Access token validation failed

4

401

Unauthorized

Помилка підтвердження

5

403

 

Invalid scope(s)

6

1000

404

Composition not found

COMPOSITION_NOT_FOUND_404

Не знайдено медичний висновок

7

409

 

Validation failed

8

409

Legal entity must be ACTIVE or SUSPENDED

9

422

 

Validation failed

10

422

Division is not within current legal entity

11

422

Division is not active

12

422

required property external_id was not present

13

Специфічні

14

422

Only for active MPI record can be created medication request!

Post-processing processes

Description of actions performed on data after processing

Technical modules where the method is used

List of pages describing technical modules where the method is used

  • No labels