Table of Contents | ||||
---|---|---|---|---|
|
...
QES - qualified electronic signature (KEP)
Specification
Link |
Resource | /patients/composition/{compositionId}/cancel |
Scope | composition:cancel |
Components | |
Using Microservices | API paragraph not found |
Protocol type | REST |
Request type | PATCH |
Sync/Async | Async |
Public/Private/Internal | Public |
Logic
...
View file | ||
---|---|---|
|
Configurable parameters
Link to configurable parameters
...
EMAL_REPLACEMENT_FLOW_DISABILITY_ALLOWED_CANCELLATION_REASONS: “INCORRECT_CATEGORY,INCORRECT_DISABILITY_PERIOD,INCORRECT_INOXICATION,INCORRECT_PATIENT,INCORRECT_TRITMENT_VIOLATION”
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
compositionId | String ($uuid) (path) | Composition object ID | 89edcfb2-3479-4565-885b-d0ce7f9d081e | |
Request body | String($uuid) | Request body with signed composition. | { |
Dictionaries
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Request structure
Authorize
Check user scopes in order to perform this action (scope = 'composition:cancel')
...
For conclusions that have the relatesTo.code=REPLACES attribute set, a verification of the MC record to which the relatesTo link is reffered
if the MC referred to by the current MC is not found — the task completes its execution with the code CANT_CANCEL_NOT_FOUND (1137)
if the MC referred to by the current MC does not have the AMENDED status - the task completes its execution with the code CANT_CANCEL_NONAMENDED_COMPOSITION (1136). In an ideal situation, this code should never occur
if the checks are passed, the MC to which the link is set changes its status from AMENDED to FINAL.
The body of the cancellation request signed by QES is stored in the Ceph object storage.
The MС status is set to ENTERED_IN_ERROR.
If the authorization method is specified, an SMS is sent.
The task of canceling the MC in the ERLN is planned.
Response structure
Example:
Expand | ||
---|---|---|
| ||
|
HTTP status codes
HTTP status code | Message | What caused the error |
---|---|---|
200 | In case of successful cancellation of the Composition | Successful cancellation |
400 | Invalid request format | Error during formation or incorrect use of parameters in the request |
401 | The user role does not allow the operation to be performed | The role or scopes assigned to the user who generated the request do not allow such an operation to be done. |
404 | The object of the Composition was not found | The object of the Composition was not found or incorrect ID |
500 | Subordinate service error | Subordinate service error |