Table of Contents

minLevel	1
maxLevel	3

This method must be used to cancel of existing activity from patient's Care plan.s Care plan.

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/2125038637/care+plan#%D0%92%D1%96%D0%B4%D0%BC%D1%96%D0%BD%D0%B0-%D0%BF%D0%B5%D1%80%D0%B2%D0%B8%D0%BD%D0%BD%D0%BE%D0%B3%D0%BE-%D0%BF%D1%80%D0%B8%D0%B7%D0%BD%D0%B0%D1%87%D0%B5%D0%BD%D0%BD%D1%8F

Specification

Page Properties

Link	https://medicaleventsmisapi.docs.apiary.io/#reference/care-plan/cancel-care-plan-activity/cancel-care-plan-activity
Resource	/api/patients/{{patient_id}}/care_plans/{{care_plan_id}}/activities{{id}}/actions/cancel
Scope	care_plan:write
Components	Care plan
Microservices	me/api-medical-events me/event-consumer me/kafka-consumer il/api(rpc)
Protocol type	REST
Request type	PATCH
Sync/Async	Async
Public/Private/Internal	Public

...

Status can be changed by employee who has an Approval granted by the patient on write Care plan resource.
Cancel should be signed with DS. So, all the activity data should be submitted.
Activities status has changed in async way. The result of the job should be a link on the Care plan activity details.be a link on the Care plan activity details.

Global and configurable parameters

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/2125039308/Care+Plan+dictionaries+and+configurable+parameters+UA#%D0%9A%D0%BE%D0%BD%D1%84%D1%96%D0%B3%D1%83%D1%80%D0%B0%D1%86%D1%96%D0%B9%D0%BD%D1%96-%D0%BF%D0%B0%D1%80%D0%B0%D0%BC%D0%B5%D1%82%D1%80%D0%B8

https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/583402009/Medical+Events+Dictionaries+and+configurations#ME_ALLOWED_TRANSACTIONS_LE_TYPES

Input parameters

Input parameter	Type	Description	Example
patient_id	String	MPI identifier of the patient	`7c3da506-804d-4550-8993-bf17f9ee0402`
care_plan_id	String	Care Plan identifier	`7c3da506-804d-4550-8993-bf17f9ee0403`
id	String	activity identifier	`7c3da506-804d-4550-8993-`

bf17f9ee0404

Filters

No

Dictionaries

...

bf17f9ee0404

Filters

No

Dictionaries

eHealth/care_plan_activity_cancel_reasons

eHealth/care_plan_activity_outcomes

eHealth/ICPC2/condition_codes

eHealth/ICD10_AM/condition_codes

eHealth/care_plan_activity_goals

eHealth/care_plan_activity_complete_reasons

eHealth/ucum/units

MEDICATION_UNIT

DAYS_OF_WEEK

EVENT_TIMING

SPECIALITY_TYPES_ALLOWED

PROVIDING_CONDITIONS_ALLOWED

INNM_DOSAGE

Request structure

See on Apiary

...

Expand

title	Request example

Code Block

{
  "id": "75a5d991-0bf7-476f-b3cf-bec73f044b2e",
  "author": {
    "identifier": {
      "type": {
        "coding": [
          {
            "system": "eHealth/resources",
            "code": "employee"
          }
        ]
      },
      "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
    }
  },
  "care_plan": {
    "identifier": {
      "type": {
        "coding": [
          {
            "system": "eHealth/resources",
            "code": "care_plan"
          }
        ]
      },
      "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
    }
  },
  "detail": {
    "kind": "service_request",
    "product_reference": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "service"
            }
          ],
          "text": ""
        },
        "value": "97d57238-ffbe-4335-92ea-28d4de117ea3"
      }
    },
    "reason_code": [
      {
        "coding": [
          {
            "system": "eHealth/ICD10_AM/condition_codes",
            "code": "X85"
          }
        ]
      }
    ],
    "reason_reference": [
      {
        "identifier": {
          "type": {
            "coding": [
              {
                "system": "eHealth/resources",
                "code": "condition"
              }
            ]
          },
          "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
        }
      }
    ],
    "goal": [
      {
        "coding": [
          {
            "system": "eHealth/care_plan_activity_goals",
            "code": "diabetes_treatment"
          }
        ]
      }
    ],
    "quantity": {
      "value": 13,
      "system": "MEDICATION_UNIT",
      "code": "MG",
      "unit": "мг"
    },
    "scheduled_timing": {
      "event": [
        "2018-08-02T10:45:16Z"
      ],
      "repeat": {
        "bounds_duration": {
          "value": 10,
          "comparator": ">",
          "unit": "доба",
          "system": "eHealth/ucum/units",
          "code": "day"
        },
        "count": 10,
        "count_max": 20,
        "duration": 15,
        "duration_max": 25,
        "duration_unit": "day",
        "frequency": 1,
        "frequency_max": 4,
        "period": 1,
        "period_max": 3,
        "period_unit": "day",
        "day_of_week": [
          "mon"
        ],
        "time_of_day": [
          "16:00:00"
        ],
        "when": [
          "WAKE"
        ],
        "offset": 20
      },
      "code": {
        "coding": [
          {
            "system": "TIMING_ABBREVIATION",
            "code": "Q4H"
          }
        ]
      }
    },
    "location": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "division"
            }
          ]
        },
        "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
      }
    },
    "performer": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "employee"
            }
          ]
        },
        "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
      }
    },
    "daily_amount": {
      "value": 13.5,
      "system": "MEDICATION_UNIT",
      "code": "MG",
      "unit": "мг"
    },
    "description": "Some activity description",
    "do_not_perform": false,
    "program": {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "medical_program"
            }
          ]
        },
        "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
      }
    },
    "status": "scheduled",
    "status_reason": {
      "coding": [
        {
          "system": "eHealth/care_plan_activity_cancel_reasons",
          "code": "some code"
        }
      ]
    }
  },
  "outcome_reference": [
    {
      "identifier": {
        "type": {
          "coding": [
            {
              "system": "eHealth/resources",
              "code": "encounter"
            }
          ]
        },
        "value": "9183a36b-4d45-4244-9339-63d81cd08d9c"
      }
    }
  ],
  "outcome_codeable_concept": [
    {
      "coding": [
        {
          "system": "eHealth/care_plan_activity_outcomes",
          "code": "some code"
        }
      ]
    }
  ],
  "inserted_at": "2017-04-20T19:14:13Z",
  "inserted_by": "e1453f4c-1077-4e85-8c98-c13ffca0063e",
  "updated_at": "2017-04-20T19:14:13Z",
  "updated_by": "2922a240-63db-404e-b730-09222bfeb2dd"
}

Authorize

Verify the validity of access token
1. Return (401, 'Invalid access token') in case of validation fails
Verify that token is not expired
1. in case of error - return (401, 'Invalid access token')
Check user scopes in order to perform this action (scope = 'care_plan:write')
1. 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

Headers

Наприклад:

Content-Type:application/json
Authorization:Bearer

...

{{access_token}}
API-key:{{mis_client_secret}}

Request data validation and processing

Validate legal entity

Extract client_id from token
Check legal entity status is ACTIVE
1. In case of error - return 409 (Legal entity must be ACTIVE)
Check legal entity type in ME_ALLOWED_TRANSACTIONS_LE_TYPES config parameter
1. in case of error - return 409 ('client_id refers to legal entity with type that is not allowed to create medical events transactions')

Validate User

Extract user_id from token.
Check user has an active and approved employee that:
1. has an active Approval granted by the Patient on write the Care plan resource (care plan id from URL)
  1. Return 403 ('Access denied') in case employee has no Approval on write

Validate data consistency

Ensure that submitted activity relates to the Patient and Care Plan (from URL)
1. Return 404 (not found) in case of error

Validate Digital Sign

Check DS is valid and not expired
Validate that DS belongs to the user
1. Check that DRFO from DS and user's party.tax_id matches
  1. in case of error - return 409 (“Signer DRFO doesn't match with requester tax_id“)

Validate status transition

Get activity by id
Check activity.detail.status: activity status should be changed according to activity

...

status model.
1. Return 409 (Invalid activity status) in case of error
Check activity.detail.status in (in_progress, scheduled)
1. in case of error - return 409 ('Activity can be cancelled only if it has in_progress or scheduled status')

Validate status reason

Validate value in the field $.detail.status_reason, required

Validate field type is codeable concept
Check that codeable concept refers to the eHealth/care_plan_activity_cancel_reasons dictionary
Validate value within dictionary specified above
1. in case of error - return 422 ('value is not allowed in enum')

Validate related entities

if activity kind = medication_request:
1. Check there is no medication request requests in status NEW based on the activity
  1. in case of error - return 409 (Unable to cancel activity with new Medication Request requests).
2. Check there is no medication requests in status ACTIVE based on the activity
  1. in case of error - return 409 (Unable to cancel activity with active Medication requests).
if activity kind = service_request:
1. ~~Check availability of service requests with~~ ~~status = active~~.~~If such service requests exist, then needs to check availability of service requests with~~ ~~program_processing_status~~:
  1. if ~~program_processing_status~~ ~~is undefined (~~~~NULL~~~~), then return error 409 (Unable to cancel activity with Service requests in status <status value> and program processing status is NULL or not completed)~~
  2. if ~~program_processing_status~~ ~~is defined, then needs to check that~~ ~~program_processing_status = complete~~~~. Otherwise~~

...

1. 1. ~~, return error 409 (Unable to cancel activity with Service requests in status <status value> and program processing status is NULL or not completed)~~
2. Check all related service requests in final status: completed, recalled or entered_in_error.
  1. in case at least one is active - return error 409 (Unable to cancel activity with Service requests in

...

1. 1. active status)
if activity kind = device_request:
- Check there is no device requests in status ACTIVE based on the activity
  - in case of error - return 409 (Unable to cancel activity with active Device requests).

Validate content

Signed content must match with activity in DB in order to be changed

...

Expand

title	Response example

Code Block

{
  "data": {
    "status": "pending",
    "eta": "2018-08-02T10:45:16.000Z",
    "links": [
      {
        "entity": "job",
        "href": "/Jobs/NBXk9EyErUZv1RhXgyvgg"
      }
    ]
  },
  "meta": {
    "code": 202,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  }
}

Post-processing processes

API paragraph not found

HTTP status codes

Page Properties

HTTP status code	Message	What caused the error
201201	use payload from response	sync
202202	use Get job details to get processing result. Response payload will be returned in the job details	async: default method
401	Invalid access token	validation fails token is expired
403	Your scope does not allow to access this resource. Missing allowances: care_plan:write Access denied	invalid scope(s) employee has no Approval on write
404	not found	The submitted activity is not related to the Patient Care Plan
409	client_id refers to legal entity that is not active client_id refers to legal entity with type that is not allowed to create medical events transactions Invalid activity status Unable to cancel activity with new Medication Request requests Unable to cancel activity with active Medication requests ~~Unable to cancel activity with Service requests in status <status value> and program processing status is NULL or not completed~~ Unable to cancel activity with Service requests in active status	Validation error
422	Value is not allowed in enum Signed content doesn't match with previously created activity	Validation error

...

Versions Compared

Old Version 16

New Version Current

Key

Specification

Global and configurable parameters

Input parameters

Filters

Dictionaries

Filters

Dictionaries

Request structure

Authorize

Headers

Request data validation and processing

Validate legal entity

Validate User

Validate data consistency

Validate Digital Sign

Validate status transition

Validate status reason

Validate related entities

Validate content

Post-processing processes

HTTP status codes

Page Comparison

Versions Compared

Old Version 16

New Version Current

Key

Specification

Global and configurable parameters

Input parameters

Filters

Dictionaries

Filters

Dictionaries

Request structure

Authorize

Headers

Request data validation and processing

Validate legal entity

Validate User

Validate data consistency

Validate Digital Sign

Validate status transition

Validate status reason

Validate related entities

Validate content

Post-processing processes

HTTP status codes