Purpose
This WS is designed to search (get list) Requests for Medication request in the care plan context. If the user has approval of the care plan, he will receive a list of Medication request requests regardless of the legal entity which are created on the basis of this care plan.
Specification
Logic
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 party_id from $.context.user_id
Get list from $.prm.employees for this party_id
Get care_plan_id from url
Check $.approvals for user's employees (granted_to) on care_plan_id (granted_resources) and $.medication_request_requests.person_id (granted_by)
Search Medication request requests by filters: care_plan_id
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)
Preconditions
No
Global and configurable parameters
No
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
care_plan_id |
Filters
See on Apiary
Request structure
API paragraph not found
Authorize
Request to process the request using a token in the headers
Headers
Content-Type:application/json
Authorization:Bearer c2778f3064753ea70de870a53795f5c9
Validate request
API paragraph not found
Request data validation
API paragraph not found
Parameters that are used when processing the request
Configuration parameters
Access to the method is defined by the scope medication_request_request:read. Permission for this scope is determined by the System administrator by configuring scopes in the context of clients and roles.
Dictionaries
API paragraph not found
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 | Invalid scope |
Backward compatibility
API paragraph not found