Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
field | value |
---|---|
|
|
|
|
| $.id |
| $.status |
| $.update_at |
| $.changed_by |
f the medication request is based on the activity with quantity:
Recalculate and set remaining_quantity for the activity as described at Create Medication Request: Validate based_on (p. 2.d.1 )and do not include current MR but include all MD which related to current MR
...
MEDICATION_REQUEST_BLOCK_REASON
MEDICATION_REQUEST_INTENT
MEDICATION_REQUEST_CATEGORY
MEDICATION_REQUEST_PRIORITY
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
ADDRESS_TYPE
SETTLEMENT_TYPE
STREET_TYPE
PHONE_TYPE
DIVISION_TYPE
POSITION
MEDICATION_FORM
MEDICATION_UNIT
eHealth/clinical_impression_patient_categories
LICENSE_TYPE
FUNDING_SOURCE
MR_BLANK_TYPES
MEDICATION_REQUEST_REJECT_REASON
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | id | M | String | medication request identifier | a89f6a26-4221-4597-a1d2-542d5e40b565 |
2 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
...
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 = 'medication_request:reject')
return 403 (“Your scope does not allow to access this resource. Missing allowances: medication_request:reject”) in case of invalid scope(s)
If BLOCK_UNVERIFIED_PARTY_USERS is true, then check party's data match following condition: verification_status != NOT_VERIFIED or (verification_status = NOT_VERIFIED and updated_at <= current_date - UNVERIFIED_PARTY_PERIOD_DAYS_ALLOWED):
in case not match - return 403 ("Access denied. Party is not verified")
Check signed content
Check that signed content contains all required fields and is equal to stored object:
...
For more information look at Medication request status model .
Validate reject reason code
Validate $.reject_reason_code is a value from MEDICATION_REQUEST_REJECT_REASON dictionary
in case of error - return 422 ("value is not allowed in enum")
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
Expand | ||
---|---|---|
| ||
|
...
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 |
| 3 |
| 4 | |
5 | Специфічні | ||||
6 | 400 | document must be signed by 1 signer but contains 0 signatures | На документ має бути накладено 1 цифровий підпис за допомогою КЕП, проте маємо 0 цифрових підписів | ||
3 | 400 | Invalid signature | Некоректний КЕП | ||
4 | 401 | Invalid access token | Недійсний токен доступу | ||
5 | 403 | Your scope does not allow to access this resource. Missing allowances: medication_request:reject | Для вашої ролі відсутній доступ до цього ресурсу. Необхідний доступ на відхилення рецепта | ||
6 | 403 | Access denied. Party is not verified | Доступ заборонено. Працівник не перевірений | ||
7 | 404 | Not found | не знайдено | ||
8 | 409 | Employee is not author of medication request, doesn't have approval or required employee type | Співробітник не є автором електронного рецепта, не має доступу до нього або не належить до необхідного типу працівника | ||
9 | 409 | Invalid status Medication request for reject transition! | Некоректний статус електронного рецепта для його відхилення | ||
10 | Специфічні | ||||
11 | 422 | Does not match the signer drfo | РНОКПП користувача не співпадає з РНОКПП, зазначеним у КЕП | ||
12 | 422 | schema does not allow additional properties' OR 'required property type was not present | схема не допускає додаткових властивостей АБО не вказано ТИП | ||
13 | 422 | Signed content does not match the previously created content | Підписані дані не відповідають раніше створеним | ||
14 | 422 | value is not allowed in enum | Недопустиме значення |
Post-processing processes
Description of actions performed on data after processing
Technical modules where the method is used
List of pages describing technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|
...