Note |
---|
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Info |
---|
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
...
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
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
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
...
Response structure examples
See on API-specification
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...