Purpose

...

Logic

1. Verify the validity of access token:

   1. return 401 in case validation fails.

2. Check user scopes in order to perform this action (scope = 'medication_request_request:read'):

   1. return 403 in case invalid scope(s).

3. Get `my_party_id`  from `$.context.user_id`

   1. return 500 in case ("Not found party for this user!") . 

4. Get list of employees for this `party_id`  & `$.context.legal_entity_id` (if not NULL).

5. Search Requests for Medication request by filters in WS url:

   1. SELECT * FROM requests_for_medication_request WHERE <filters>

   2. optional filters:

      1.  list employee_id (uuid). By default returned all data.

      2. person_id (uuid). By default returned all data.

      3.  status (Dictionary:  REQUEST_FOR_MEDICATION_REQUEST_STATUS). By default returned all rows with status=NEW.

      4. limit (limit response size - quantity of innm objects). By default returned 50 objects.

      5. starting_after (cursor to fetch next page)

      6. ending_before (cursor to fetch previous page)

...

Parameters that are used when processing the request

Configuration parameters

Доступ до методу визначається скоупом Access to the method is defined by the scope medication_request_request:read. Дозвіл на даний скоуп визначається адміністратором Системи шляхом конфігурування скоупів в контексті клієнтів і ролейPermission for this scope is determined by the System administrator by configuring scopes in the context of clients and roles.

Dictionaries

API paragraph not found

...