Purpose

This WS method gives opportunity to reject and close preperson merge request by hand.

Specification

...

Logic

1. Only authenticated and authorized

...

1. SPECIALIST,

...

1. ASSISTANT or RECEPTIONIST

...

1. employees can use this WS.

2. Usage of this WS allowed in EMERGENCY

...

1. or OUTPATIENT legal entities.

2. Only NEW or APPROVED

...

1. merge request can be rejected.

2. The request can be rejected only by employee who made the request.

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

Input parameters

...

Authorize

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 = '

...

1. merge_request:write')

   1. Return 403 in case invalid scope(s)

2. 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)

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

...

Authorization:Bearer {{access_token}}

Api-key:{{secret}}

Request data validation

Validate merge request

1. Validate

...

1. merge request id exists in DB

   1. In case of error - return 404

2. Check

...

1. merge request status is NEW or APPROVED

   1. In case of error - return

...

1. 1. 409 (Invalid merge request

...

Validate employee

Validate employee as on create preperson merge request, but in addition check the employee has created this merge request:

1. Select inserted_at from il.person_requests of this preperson merge request

2. Compare user_id with inserted_at.

   1. If not match - return 422 error (User created preperson merge request does’nt match with current)

1. 1. status)

Processing

Update object in DB

mpi.personmerge_requeststable

Response structure

See on Apiary

Example:

{
  "meta": {
    "code": 200,
    "url": "https://example.com/resource",
    "type": "object",
    "request_id": "6617aeec-15e2-4d6f-b9bd-53559c358f97#17810"
  },
  "data": {
    "id": "7c3da506-804d-4550-8993-bf17f9ee0404",
    "master_person_id": "7c3da506-804d-4550-8993-bf17f9ee0402",
    "merge_person_id": "7c3da506-804d-4550-8993-bf17f9ee0403",
    "status": "REJECTED",
    "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