...

Preconditions

Merge request must be approved.

...

1. Only authenticated and authorized SPECIALIST employees can use this WS.

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

3. Employee should sign merge request to link person with preperson.

4. Only request APPROVED by person can be signed.

5. The request can be signed only by employee who made the request.

6. Create objects in DB should be done in one transaction.

7. Status change of the merge request and preperson should be logged in the Event manager.

8. Succesfull merge does not create record in MPI.persons table for preperson, but deactivates record in MPI.prepersons and linked document in patient collection (mongo)

9. Data from the field data_to_be_signed used as request data for sign method.

Input parameters

Request structure

See on Apiary

...

• Check decoded signed content with previously created on IL.db.

SELECT data
FROM merge_requests
WHERE id = {:id}

In case if they are not equal - generate 422 error (message: "Signed content does not match the previously created content")

...

1. Get url for merge request upload.

1. Upload signed merge request to media storage.

Create object in DB

mpi.merged_pairs table

Update object in DB

1. il.merge_requeststable

2. mpi.prepersons table

3. patients collection (mongo, separate job)

Response structure

See on Apiary

...

{
  "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": "SIGNED",
    "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"
  }
}

Post-processing processes

...

HTTP status codes

...