ЕСОЗ - публічна документація

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Purpose

This WS merges person with preperson after merge request has been signed by employee.

Specification

Apiary

Service logic

  1. Only authenticated and authorized SPECIALIST or RECEPTIONIST 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)

Authentication

  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)

Validate digital signature

Validate digital sign as described on sign patient request process

Validate schema

Validate request using schema (TBD)

Validate merge request

  1. Validate merge request id exists in DB

    1. In case of error - return 404

  2. Check merge request status is APPROVED

    1. In case of error - return 422 (Incorrect status to sign merge request)

Check signed content

  1. Get previously request data from il.merge_requests.data.

  2. Compare it with request data.

    1. In case they are not equal - return 422 error (Signed content does not match the previously created content)

  3. Check patient_signed = true. It means that person signed printout content.

    1. In case of error - return 422 error (Patient must sign merge request form).

Validate legal entity

Validate legal entity as on create merge request process.

Validate person

Validate person as on create merge request process.

Validate preperson

Validate preperson as on create merge request process, but w/o searching pending merge requests and episodes.

Validate employee

Validate employee as described on reject merge request process.

Save signed merge request to media storage

  1. Get url for merge request upload. Ensure new entity doesn’t rewrite existent.

Parameter

Source

action

'GET'

bucket

'MERGE_REQUESTS'

resource_id

: MERGE_REQUEST_ID

resource_name

: MERGE_REQUEST_NAME

timestamp

:TIMESTAMP

2. Upload signed merge request to media storage.

Create object in DB

mpi.merged_pairs table

Parameter

Source

Description

id

uuid

Authogenerated, required.

master_person_id

merge_requests.master_person_id

Identifier of the person in MPI.persons, required

merge_person_id

merge_requests.merge_person_id

Identifier of the preperson in MPI.prepersons, required

inserted_at

timestamp

Get current date-time

updated_at

timestamp

Get current date-time

Update object in DB

  1. il.merge_requests table

Parameter

Source

Description

status

string

Status of the request, required. Set SIGNED

merged_pair_id

uuid

Identifier of merged pair. Get from mpi.merged_pair.id

patient_signed

bool

Evidence that person has signed the merge request. Set from Request, should be true.

updated_by

uuid

Extract user from token

updated_at

timestamp

Get current date-time

2. mpi.prepersons table

Parameter

Source

Description

status

string

Status of the preperson, required. Set inactive

updated_by

uuid

Extract user from token

updated_at

timestamp

Get current date-time

3. patients collection (mongo, separate job)

Parameter

Source

Description

status

string

Status of the preperson, required. Set inactive

updated_by

uuid

Extract user from token

updated_at

timestamp

Get current date-time

  • No labels