| Table of Contents |
|---|
Purpose
...
| Table of Contents |
|---|
Purpose
This WS serves for receiving approval from a person on the action of merging with preperson.
Specification
| Page Properties | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
|
Preconditions
Merge request must be created.
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.
Person should confirm merge with preperson by auth method chosen on create patient request or create declaration request processes.
The request can be approved only by employee who made the request.
Change status should be logged in the Event manager.
Input parameters
Input parameter | Values | Type | Description | Example |
|---|---|---|---|---|
id | String | Identifier of the |
merge request. Required | 7c3da506-804d-4550-8993-bf17f9ee0404 |
Dictionaries
GENDER
DOCUMENT_TYPE
ADDRESS_TYPE
COUNTRY
SETTLEMENT_TYPE
STREET_TYPE
PHONE_TYPE
CONFIDANT_PERSON_TYPE
PREFERRED_WAY_COMMUNICATION
DOCUMENT_RELATIONSHIP_TYPE
Request structure
Example:
...
Verify the validity of access token
Return 401 in case validation fails
Check user scopes in order to perform this action (scope = 'merge_request:write')
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.
If not match - return 403 error (Only author of merge request is allowed to approve it)
Check that client_id from the token maches with il.merge_requests.legal_entity_id
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 c2778f3064753ea70de870a53795f5c9api{{access_token}}
Api-key:uXhEczJ56adsfh3Ri9SUkc4en{{secret}}
Request data validation
Validate schema
...
Get authorization_method from il.merge_requests.authentication_method_current.
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
Check if person has confidant_person block:
if has - select printout form with confidant person
if not - select printout form w/o confidant person
Invoke MAN to render print form.
Request mapping:
Parameter | Source |
|---|---|
id | MERGE REQUEST |
Set
il.merge_requests.printout_form
Update object in DB
il.merge_requeststable
Parameter | Source | Description |
|---|---|---|
status | Request: status | Status of the request, required. Set APPROVED |
data | Request: data | Request data for sign, required. Save master_person and merge_person blocks with detailed information, printout form, merge request id, patient_signed (master person) and status field. |
printout_form | text | Generated printout form (PREPERSON MERGE REQUEST) |
updated_by | uuid | Extract user from token |
updated_at | timestamp | Get current date-time |
Response structure
See on Apiary
...
| Page Properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|