Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel3

...

This web service is designed to return allergy intolerances info by patient_ id, episode_id or encouner_id.

Specification

Page Properties

Link

https://ehealthmedicaleventsapi.docs.apiary.io/#reference/medical-events/allergy-intolerance/get-allergy-intolerance-by-id

Resource

/api/patients/{{patient_id}}/allergy_intolerances/{{allergy_intolerance_id}}

Scope

allergy_intolerance:read

Components

Episode of Care

Microservices

API paragraph not found

Protocol type

REST

Request type

GET

Sync/Async

Async

Public/Private/Internal

Public

Logic

API paragraph not foundThis web service is designed to return allergy intolerances info by id.

Input parameters

Input parameter

Values

Type

Description

Example

patient_id

String

Patient identifier

70a9e15b-b71b-4caf-8f2e-ff247e8a5677

allergy_intolerance_id

String

Allergy intolerance identifier

a10aeafb-0df2-4091-bc83-f07e92a100ae

...

Request to process the request using a token in the headers

Headers

Наприклад:

  • Content-Type:application/json

  • Authorization:Bearer mF_9.B5f-4.1JqM

Request data validation

Validate token

  • Verify the validity of access token

    • Return 401 in case validation fails

  • Verify token is not expired

    • in case error return 401 

Validate scopes

  • Check user scopes in order to perform this action (scope = 'allergy_intolerance:read')

    • Return 403 in case invalid scope(s)

Headers

  • Content-Type:application/json

  • Authorization:Bearer {{access_token}}

  • API-key:{{secret}}

Request data validation

Access to the resource is also managed by ABAC module.

...

HTTP status code

Message

What caused the error

 200

 

 

401

 

Access token validation failed

403

 

Invalid scope