ЕСОЗ - публічна документація
RC._Process Specimen_EN
Purpose
This WS allows to set date and time when Specimen was received for processing by laboratory employee.
Specification
Link | |
Resource | /api/patients/patient_id/specimens/id/actions/ |
Scope | specimen:process |
Components | Specimen |
Microservices |
|
Protocol type | REST |
Request type | PATCH |
Sync/Async | Async |
Public/Private/Internal | Public |
Key points
Only authenticated and authorized employee with appropriate scope can process a Specimen.
DS isn't used here.
The specimen is processed asynchronously
Logic
RC._Процеси роботи зі зразком біоматеріалу | Облік дати та часу отримання Зразка
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id |
| String | Unique patient identifier |
|
id |
| String | Unique specimen identifier | aff00bf6-68bf-4b49-b66d-f031d48922b3 |
Request structure
See on Apiary
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:process')
return 403 (“Your scope does not allow to access this resource. Missing allowances: specimen:process”) 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")
Headers
Content-Type:application/json
Authorization:Bearer mF_9.B5f-4.1JqM
api-key:aFBLVTZ6Z2dON1V
X-Custom-PSK:a2aa05c76f3f2d91870f923a53cc8aa8f23bbc01a8238d1c2c26d4299715a7e4
Request data validation
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. Received datetime
Validate value in the field $.received_time, timestamp, required
Check it hasn’t set yet (empty before the process invoked)
in case of error - return 422 ('Value is already set and cannot be changed')
Check $.received_time is between current datetime and (collected_date_time OR collected_period.end)
in case of error - return 422 ('Should be between collected datetime and current datetime')
Processing
Create job and return it’s id.
Update specimen record with following:
received_time = $.received_time
updated_at = current datetime
updated_by = user_id from token
Response structure
See on Apiary
HTTP status codes
HTTP status code | Message | What caused the error |
401 | Invalid access token |
|
403 | Access denied. Party is not verified |
|
403 | Access denied. Party is deceased |
|
403 | Your scope does not allow to access this resource. Missing allowances: specimen:process |
|
404 | not found |
|
409 | client_id refers to legal entity that is not active |
|
409 | Specimen is not in available status |
|
422 | Should be between collected datetime and current datetime |
|
422 | Value is already set and cannot be changed |
|
ЕСОЗ - публічна документація