Purpose
Use this method to obtain the list of Medication request Requests for an employee_id
Specification
Logic
Процеси роботи з випискою електронних рецептів
Preconditions
No
Global and configurable parameters
No
Input parameters
No
Filters
See on Apiary
Request structure
API paragraph not found
Authorize
Request to process the request using a token in the headers
Verify the validity of access token:
return 401 in case validation fails.
Check user scopes in order to perform this action (scope = 'medication_request_request:read'):
return 403 in case invalid scope(s).
Get `my_party_id` from `$.context.user_id`
return 500 in case ("Not found party for this user!") .
Get list of employees for this `party_id` & `$.context.legal_entity_id` (if not NULL).
Search Requests for Medication request by filters in WS url:
SELECT * FROM requests_for_medication_request WHERE <filters>
optional filters:
list employee_id (uuid). By default returned all data.
person_id (uuid). By default returned all data.
status (Dictionary: REQUEST_FOR_MEDICATION_REQUEST_STATUS). By default returned all rows with status=NEW.
limit (limit response size - quantity of innm objects). By default returned 50 objects.
starting_after (cursor to fetch next page)
ending_before (cursor to fetch previous page)
Headers
Content-Type:application/json
Authorization:Bearer c2778f3064753ea70de870a53795f5c9
Request data validation
API paragraph not found
Dictionaries
REQUEST_FOR_MEDICATION_REQUEST_STATUS
Processing
If according to filters requests are not found, WS returns empty data array.
WS also returns pagination data - for technical info.
Response structure
See on Apiary
Example:
Post-processing processes
No
HTTP status codes
HTTP status code | Message | What caused the error |
---|---|---|
200 | Response |
|
401 | Invalid access token |
|
403 | Your scope does not allow to access this resource. Missing allowances: medication_request_request:read |
|
500 | Not found party for this user! |
Backward compatibility
API paragraph not found