Table of Contents |
---|
...
Purpose
This WS is designed to return Request for Medication request detail.
Specification
...
Page Properties | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
JSON Schema response |
specs | |
Purpose
This WS is designed to return Request for Medication request detail.
APIary
get-request-for-medication-request-by-id
Input parameters (filters)
|
Logic
Logic WS
Verify the validity of access token.
Check user scopes in order to perform this action (scope = 'medication_request_
for_medication_request:read').
Search Requests for Medication request by id in WS url:
languageCode Block sql SELECT * FROM requests_for_medication_request_requests WHERE id=$.id AND legal_entity_id = $.context.legal_entity_id
Response (output)
- Return object with responce structure from WS Create Medication Request SP.
- If according to filters requests are not found, WS returns 404 error message ("Not found request!").
Logic WS for medication request requests based on care plan
Get party_id from $.context.user_id
Get list from $.prm.employees for this party_id
Get care_plan_id from $.medication_request_requests.data_based_on_care_plan_id
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: data_based_on_care_plan_id, person_id
Code Block SELECT * FROM medication_request_requests MRR WHERE MRR.id = $.id AND MRR.data_based_on_care_plan_id = $.id AND MRR.person_id = $.id AND MRR.is_active = TRUE
Preconditions
API paragraph not found
Global and configurable parameters
No
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
id | String | Required | 48416485-cc98-46c4-8bba-e321de9e1ecd |
Filters
No
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
Validate FK
Validate id - medication_request_request_id exists:
return 422 in case validation fails (422 EView).
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
API paragraph not found
Response structure
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
Post-processing processes
No
HTTP status codes
HTTP status code | Message | What caused the error |
---|---|---|
200 | Response |
|
422 | Error |
Backward compatibility
API paragraph not found