Table of Contents |
---|
Purpose
This method is designed to stop previously created Device dispense
...
Only authenticated and authorized users of legal entity who has created Device dispense can stop Device dispense
Device dispense can be rejected only from ‘IN_PROGRESS' status.
Specification
Page Properties | ||
---|---|---|
| ||
...
|
Logic
Update Device dispense data in device_dispenses (MongoDB):
set status = ‘stopped’
updated_by = user_id
updated_at = now()
Send
StatusChangeEvent
to Event Manager
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
patient_id | String | Unique patient identifier |
|
Request structure
API paragraph not found
Authorize
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 = 'device_dispense:stop')
return 403 (“Your scope does not allow to access this resource. Missing allowances: device_dispense:stop”) in case of invalid scope(s)
...
Headers
API paragraph not found
Request data validation
Validate Legal entity
Extract client_id from token
Check legal entity exists and its status is ACTIVE
In case of error - return 409 ('client_id refers to legal entity that is not active')
...
Update Device dispense data in device_dispenses (MongoDB):
set status = ‘stopped’
updated_by = user_id
updated_at = now()
...
For more information look at Device dispense status model .
Service logic
https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17492805190 .
Processing
API paragraph not found
Response structure
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
Post-processing processes
API paragraph not found
HTTP status codes
Page Properties | ||||||
---|---|---|---|---|---|---|
| ||||||
|