REST API method / Метод REST API (настанова) (remove the link block before publishing the document)
Properties of a REST API method document
Purpose
This WS is designed to return records about Medication request Requests in a person’s context by search params
Logic
Процеси роботи з випискою електронних рецептів
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
eHealth/SNOMED/additional_dosage_instructions
eHealth/SNOMED/anatomical_structure_administration_site_codes
eHealth/SNOMED/route_codes
eHealth/SNOMED/administration_methods
eHealth/SNOMED/dose_and_rate
eHealth/ICD10_AM/condition_codes
eHealth/ICPC2/condition_codes
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | person_id | M | String | person_id of a patient | 5e661b15-a39a-4713-b18e-ba03a4a48ecc |
2 | legal_entity_id | O | String | Unique legal entity identifier | 7124259c-eeb1-4cbb-acac-ada2162675d1 |
3 | employee_id | O | String | Unique doctor identifier | 7124259c-eeb1-4cbb-acac-ada2162675d1 |
4 | episode_id | O | String | Unique episode identifier, look into episode in encounter | 6f305d0e-1758-4920-9167-d4f97225ad7e |
5 | care_plan_id | O | String | Unique care plan identifier | 8838982b-6a77-4cb5-87cd-cdb82eb55364 |
6 | activity_id | O | String | Unique activity identifier | d1e07d06-d063-4d19-b9ae-88fc1c7a8682 |
7 | encounter_id | O | String | Unique encounter identifier | 7075e0e2-6b57-47fd-aff7-324806efa7e5 |
8 | status | O | Enum | Status of medication request request. Default
| NEW |
9 | intent | O | String | Medication request request intent | order |
10 | page | O | Number | Page number | 2 |
11 | page_size | O | Number | A limit on the number of objects to be returned, between 1 and 300. Default: 50 | 50 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Request data validation
Authorize
Verify the validity of access token
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 = 'medication_request_request:read')
Return (403, 'Your scope does not allow to access this resource. Missing allowances: medication_request_request:read') in case of invalid scope(s)
Access to the resource is also managed by ABAC rules (EN).
Processing
Service returns all Medication request requests related to the person filtered by submitted parameters:
Get all Medication request requests by person_id from medication_request_requests (IL database)
Validate data consistency:
Ensure that requested Medication request requests have ABAC context
Return 403 ('Access denied') in case of error
Filter list above by submitted search parameters
Render a response according to specification with found Medication request requests entities.
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 | 401 | Invalid access token | Недійсний токен доступу | ||
3 | 403 | Your scope does not allow to access this resource. Missing allowances: medication_request_request:read | Для вашої ролі відсутній доступ до цього ресурсу. Необхідний доступ на перегляд заявки на електронний рецепт | ||
4 | 403 | Access denied | Доступ заборонено | ||
5 | Специфічні | ||||
6 |
Post-processing processes
No
Technical modules where the method is used
List of pages describing technical modules where the method is used