...

Purpose

Describe the purpose of the API method, add Key points (if necessary)

Logic

...

Purpose

This web service is designed to close an episode.

Logic

This web service is designed to close an episode of care.

Configuration parameters

Description of the configuration parameters that are used when processing a request in the system

Dictionaries

Provides a list of links to dictionaries that are available in Confluence

Input parameters

Description of input parameters

Request structure

See on Apiary

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API request structure, example

{
  "period": {
    "end": "2018-08-02T10:45:16.000Z"
  },
  "closing_summary": "Носові шляхи вільні, горло рожеве, температура в нормі",
  "status_reason": {
    "coding": [
      {
        "system": "eHealth/episode_closing_reasons",
        "code": "cured"
      }
    ],
    "text": ""
  }
}

Headers

Request data validation

Describe the process of checking the input data transmitted in the request for compliance with the given rules and restrictions set in the API

Processing

A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API

Response structure examples

Description of the REST API response structure, example

...

...

Request data validation

Validate token

• check value of ALLOW_OTHER_LE_EMPLOYEES_TO_MANAGE_EPISODE variable in charts configuration

  • if its value is equal to false, verify that user’s employees from care_manager belongs to one of the user_id from token

    • in case of error - return 422 ('User is not allowed to perform this action')

  • otherwise, verify that user’s employees from care_manager belongs to the same Legal Entity as author of the episode

    • in case of error - return 422 ('User is not allowed to perfom this action')

Validate legal entity

1. Validate episode belongs to the legal entity where the current user works

   • ME.episode.managing_organization==token.client_id

     • in case of error return 422 "Managing_organization does not correspond to user`s legal_entity"

Validate request

1. Validate episode.status!= "entered_in_error" or "closed"

   1. in case of error "Episode in {episode_status} can not be closed"

2. Validate that "closing_reason" is a valid value from the corresponding dictionary 

   1. $.closing_reason.coding[*].system == "eHealth/episode_closing_reasons"

3. Validate period as Period (consider period.start_date from the episode)

Processing

1. Set the status of the episode in "closed"

2. Set closing_reason in status_reason

3. Set closing_summary

4. Set period.end

5. Create a record in episode.status_history

Response structure examples

See on Apiary

See on API-specification (посилання на сторінку з API-специфікацією)

{
  "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"
  }
}

{
  "meta": {
    "code": 404,
    "url": "http://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  },
  "error": {
    "type": "NOT_FOUND",
    "message": "Patient not found"
  }
}

HTTP status codes

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

...