Table of Contents

Page Properties

id	API_Specification

Link	https://ehealthmisapi1.docs.apiary.io/#reference/public.-medical-service-provider-integration-layer/merge-request/reject-merge-request	Посилання на Apiary або Swagger
Resource	/api/merge_requests/{{id}}/actions/reject	Посилання на ресурс, наприклад: /api/persons/create
Scope	merge_request:write	Scope для доступу
Components	Patient registry	Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription
Microservices	API paragraph not found	Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC
Protocol type	REST	Тип протоколу, який використовується запитом, наприклад: SOAP \| REST
Request type	PATCH	Тип запиту API, наприклад: GET, POST, PATCH…
Sync/Async	Sync	Метод є синхронним чи асинхронним?
Public/Private/Internal	Public	Потрібно зазначити тип методу за ступенем доступності

Logic

Only authenticated and authorized SPECIALIST, ASSISTANT or RECEPTIONIST employees can use this WS.
Usage of this WS allowed in EMERGENCY or OUTPATIENT legal entities.
Only NEW or APPROVED merge request can be rejected.
The request can be rejected only by employee who made the request.
Change status should be logged in the Event manager.

...

Verify the validity of access token
1. Return 401 in case validation fails
Check user scopes in order to perform this action (scope = 'merge_request:write')
1. Return 403 in case invalid scope(s)
Check the employee has created this merge request. Thus select inserted_by from il.merge_requests of this merge request and compare it with user_id from the token.
1. If not match - return 403 error (Only author of merge request is allowed to reject it)
Check that client_id from the token maches with il.merge_requests.legal_entity_id
1. If not match - return 422 error (User doesn’t belong to legal entity where the merge request was created)

Headers

Наприклад:

Content-Type:application/json

...