...

Logic

1. Only authenticated and authorized SPECIALIST, ASSISTANT or RECEPTIONIST employees can use this WS.

2. Usage of this WS allowed in EMERGENCY or OUTPATIENT legal entities.

3. Person should confirm merge with preperson by auth method chosen on create patient request or create declaration request processes.

4. The request can be approved only by employee who made the request.

5. Change status should be logged in the Event manager.

...

1. Verify the validity of access token

   1. Return 401 in case validation fails

2. Check user scopes in order to perform this action (scope = 'merge_request:write')

   1. Return 403 in case invalid scope(s)

3. 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 approve it)

4. 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

...

Next steps is similar to determine authorization method and check OTP/check Documents process on approve patient request.

...

Get all the preperson episodes for the printout form (mongodb, episodes collection).

Generate printout form

1. Check if person has confidant_person block:

   1. if has - select printout form with confidant person

   2. if not - select printout form w/o confidant person

1. Invoke MAN to render print form.

...

il.merge_requests.printout_form

Update object in DB

il.merge_requeststable

...