Info |
---|
Info |
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
Update activity status to completed (update also updated_at, updated_by)
Set outcome_codeable_concept
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
eHealth/care_plan_activity_complete_reasons
eHealth/care_plan_activity_outcomes
Input parameters
Description of input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | patient_id |
| String | MPI identifier of the patient |
|
2 | care_plan_id |
| String | Care Plan identifier |
|
3 | id |
| String | activity identifier |
|
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
...
Key | Value | Mandatory | Description | Example | |||||
---|---|---|---|---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json | ||||
2 | Authorization | Bearer {{access_tokenaccess_token}} | Authorization:Bearer {{access_token}} | ||||||
3 | API-key | {{mis_client_secret}}Authorization | API-key:Bearer {{accessmis_client_tokensecret}} | 3 | API-key | {{mis_client_secret}} | API-key:{{mis_client_secret}} |
...
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 = 'care_plan:write')
Return (403, 'Your scope does not allow to access this resource. Missing allowances: care_plan:write') in case of invalid scope(s)
Request to process the request using a token in the headers
Validate legal entity
Extract client_id from token
Check legal entity status is ACTIVE
In case of error - return 409 (Legal entity must be ACTIVE)
Check legal entity type in ME_ALLOWED_TRANSACTIONS_LE_TYPES config parameter
in case of error - return 409 ('client_id refers to legal entity with type that is not allowed to create medical events transactions')
...
if activity kind = medication_request:
Check there is no medication request requests in status
NEW
based on the activityin case of error - return 409 (Unable to complete activity with new Medication Request requests).
Check there is no medication requests in status
ACTIVE
based on the activityin case of error - return 409 (Unable to complete activity with active Medication requests).
if activity kind = service_request:
Check availability of service requests withstatus = active. If such service requests exist, then needs to check availability of service requests withprogram_processing_status:ifprogram_processing_statusis undefined (NULL), then return error 409 (Unable to complete activity with Service requests in status <status value> and program processing status is NULL or not completed)ifprogram_processing_statusis defined, then needs to check thatprogram_processing_status = complete. Otherwise, return error 409 (Unable to complete activity with Service requests in status <status value> and program processing status is NULL or not completed)
Check all related service requests in final status: completed, recalled or entered_in_error.
in case at least one is active - return error 409 (Unable to complete activity with Service requests in active status)
Validate outcome
Validate value in the field $.outcome_codeable_concept, required
Validate field type is array of codeable concepts
Validate each value in array:
it refers to the
eHealth/care_plan_activity_outcomes
dictionaryvalue within 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-специфікацією)
...
See on API-specification
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | Базові | ||||||||||
2 | 201 | use payload from response | sync | ||||||||
3 | 202 | use Get job details to get processing result. Response payload will be returned in the job details | async: default method | ||||||||
4 | 401 | Invalid access token |
| ||||||||
5 | 401 | Unauthorized | Помилка підтвердження | 6 | 403 | Access denied |
| ||||
76 | 403 | Your scope does not allow to access this resource. Missing allowances: care_plan:write | |||||||||
87 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | 9 | 404 | not found | The submitted activity is not related to the Patient Care Plan | ||
108 | 409 | client_id refers to legal entity with type that is not allowed to create medical events transactions | Validation error | ||||||||
119 | 409 | Invalid activity status | |||||||||
1210 | 409 | Legal entity must be ACTIVE | |||||||||
1311 | 409 | Unable to cancel activity with new Medication Request requests | |||||||||
1412 | 409 | Unable to cancel activity with active Medication requests | |||||||||
1513 | 409 | Unable to complete activity with new Medication Request requests | |||||||||
1614 | 409 | Unable to cancel activity with Service requests in active status | |||||||||
1715 | 422 | value is not allowed in enum | Validation error | ||||||||
1816 | Специфічні | ||||||||||
19 | 422 | Only for active MPI record can be created medication request!17 |
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 | ||||
---|---|---|---|---|
|
...