ЕСОЗ - публічна документація

RC_[NEW] Get Device context

Purpose

This method allows to get an ID of the episode that is a context of the Device, in order to create an approval on the episode, and receive access to the medical events related to that episode, including the Device.

Specification

Apiary

Authorization

  • 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 = 'medical_event_context:read')

    • Return (403, 'Your scope does not allow to access this resource. Missing allowances: medical_event_context:read') in case of invalid scope(s)

Validations

Validate Person

  • Get Person identifier from the URL

    • Check it exists in DB

      • Return 404 ('not_found') in case of error

Validate Device

  • Get Device identifier from the URL

    • Check it exists in DB

      • Return 404 ('not_found') in case of error

    • Check Device belongs to the patient

      • Return 404 ('not_found') in case of error

Service logic

Service returns context_episode_id of the device:

  • Get device.context_episode_id from Device object

  • Enrich response with context_episode_id and render the response according to JSON Schema

ЕСОЗ - публічна документація