/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document)

Properties of a REST API method document

Purpose

This WS allows to mark Specimen as unsatisfactory.

Key points

1. Only authenticated and authorized employee with appropriate scope can update a Specimen.

2. DS isn't used here.

3. The specimen is rejected asynchronously

Logic

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17629118915/RC.#%D0%9F%D0%BE%D0%B7%D0%BD%D0%B0%D1%87%D0%B5%D0%BD%D0%BD%D1%8F-%D0%97%D1%80%D0%B0%D0%B7%D0%BA%D0%B0-%D0%B1%D1%80%D0%B0%D0%BA%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%BC

Configuration parameters

N/A

Dictionaries

specimen_reject_reasons

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17629119370/RC.+Specimen+dictionaries+and+configurable+parameters#Dictionaries

Input parameters

Request structure

See on API-specification

Headers

Headers

Request data validation

Authorization

• Verify the validity of access token

  • in case of error - return 401 (“Invalid access token”) in case of validation fails

• Verify that token is not expired

  • in case of error - return 401 (“Invalid access token”)

• Check user scopes in order to perform this action (scope = 'specimen:reject')

  • return 403 (“Your scope does not allow to access this resource. Missing allowances: specimen:reject”) in case of invalid scope(s)

• If BLOCK_UNVERIFIED_PARTY_USERS is true, then check party's data match following condition: verification_status != NOT_VERIFIED or (verification_status = NOT_VERIFIED and updated_at > current_date - UNVERIFIED_PARTY_PERIOD_DAYS_ALLOWED):

  • in case not match - return 403 ("Access denied. Party is not verified")

• If BLOCK_DECEASED_PARTY_USERS is true, check that party is not deceased (party_verification record does not equal to: dracs_death_verification_status = VERIFIED and dracs_death_verification_reason = MANUAL_CONFIRMED):

  • in case of error - return 403 ("Access denied. Party is deceased")

Validate legal entity

• Extract client_id from token

• Check legal entity status (status = ACTIVE)

  • In case of error - return 409 ('client_id refers to legal entity that is not active')

Validate data consistency

• Ensure that submitted Specimen relates to the Patient (from URL)

  • in case of error - return 404 (not found)

Validate status transition

• Get Specimen by id

• Check Specimen’s status is available

  • in case of error - return 409 ('Specimen is not in available status')

Validate request

Validate request by schema and return 422 error code with the list of validation errors in case of fails. User fills following fields in the request:

1. Status reason

Validate value in the field $.status_reason, CodeableConcept type, required.

• Check that value is in allowed values from specimen_reject_reasons dictionary.

  • in case of error - return 422 ('value is not allowed in enum')

Processing

1. Create job and return it’s id.

2. Update specimen record with following:

   1. status = unsatisfactory

   2. status_reason = $.status_reason

   3. updated_at = current datetime

   4. updated_by = user_id from token

Response structure examples

See on API-specification

HTTP status codes

Post-processing processes

N/A

Technical modules where the method is used