Purpose

This method allows to get the context of Medication Statement in order to create approval on episode and receive access to other medical events.

Specification

Logic

Service returns context (episode), medication statement based on:

• Get Medication Statement object by medication_statement_id from medication_statements (MongoDB)

• Get medication_statement.context.identifier from Medication Statement object

• Call Get Encounter context :

  • Get Encounter object by medication_statement.context.identifier (medication_statement.context.identifier = encounter._id)
    AFTER

  • Get encounter.episode from Encounter object

• Render a response according to specification

Input parameters

Request structure

See on Apiary

Authorize

• 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)

Headers

• Content-Type:application/json

• Authorization:Bearer mF_9.B5f-4.1JqM

Request data validation

Validate Person

• Get Person identifier from the URL

• Check it exists in DB

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

Validate Encounter

• Get Medication Statement identifier from the URL

  • Check it exists in DB

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

  • Check Medication Statement belongs to patient

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

Processing

API paragraph not found

Response structure

See on Apiary

Post-processing processes

API paragraph not found

HTTP status codes