...

This WS allows linking medical data of an unidentified person to a person in eHealth. Thus it helps a person who was unidentified during some period to store all its medical history.

Specification

Logic

1. Only authenticated and authorized SPECIALIST, ASSISTANT or RECEPTIONIST employees can merge prepersons with prepersons.

2. Prepersons can be merged in EMERGENCY or OUTPATIENT legal entities.

3. Employee can merge any active preperson to any active person.

4. To merge person with preperson only their MPI ids needed.

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

Dictionaries

• AUTHENTICATION_METHOD

• DOCUMENT_TYPE

Request structure

Example:

...

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)

Headers

Наприклад:

Content-Type:application/json

Authorization:Bearer c2778f3064753ea70de870a53795f5c9api{{access_token}}

Api-key:uXhEczJ56adsfh3Ri9SUkc4en{{secret}}

Request data validation

Validate request

...

• If type is OTP or THIRD_PERSON - Generate verification code as on create patient request process.

• If type is OFFLINE - Generate uploaded URLs as on create patient request process. Set il.merge_requests.documents

In case no auth methods found (null) - return error with code 409 (Person has no auth methods)

Processing

Save object to DB

il.merge_requeststable

...