Versions Compared

Key

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

...

This WS is designed to search (get list) Requests for Medication request requests in the care plan context. If the user has approval of on the care plan, he will receive a list of Medication request requests regardless of the legal entity which are created on the basis of based on this care plan.

Specification

Page Properties

Project Name

Електронний рецепт

COVID-certificate

Project abreviation

ePrescription

SVC

Developer

API paragraph not found

Edenlab

Розробник методу API. Наприклад, Edenlab

Project Manager

API paragraph not foundMari Hulko (Unlicensed)

Mykhailo Zhushman (Unlicensed)

Tech Lead

API paragraph not foundMynchenko Andrii (SoE eHealth)

Product Owner

API paragraph not foundIgor Kostyria

Yevhen Batura NHSU

Вusiness analyst

API paragraph not foundIryna Lishtaba (SoE eHealth) Oleksandr Zhuk (SoE eHealth) Oksana Demchenko

Taras Khometa (Unlicensed)

Status

Status
colourGreen
titleAPPROVED

Status
colourGreen
titleAPPROVED

Version

API paragraph not found

1.0

Date of release

API paragraph not foundPROD

Link

https://uaehealthapiehealthmisapi1.docs.apiary.io/#reference/public.-reimbursement/medication-request-requests/get-medication-request-requests-in-care-plan-context

Посилання на Apiary або Swagger

Resource

/api/care_plans/{{care_plan_id}}/medication_request_requests

Наприклад: /api/persons/create

Scope

medication_request_request:read

Зазначається потрібний scope

Components

ePrescription, Reimbursement

Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription

Microservices

API paragraph not found

Перелік мікросервісів, які використовує метод API. Наприклад: Auth, ABAC

Protocol type

REST

Тип протоколу, який використовується запитом, наприклад: SOAP | REST

Request type

GET

Тип HTTP методу, який використовується запитом, наприклад: POST | GET…

Sync/Async

Sync

Метод є синхронним чи асинхронним?

Logic

...

Verify the validity of access token

  1. Return 401 in case validation fails

...

API paragraph not found

Preconditions

No

Global and configurable parameters

No

Input parameters

Input parameter

Values

Type

Description

Example

care_plan_id

Filters

See on Apiary

Request structure

API paragraph not found

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

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

...

Get party_id  from $.context.user_id

...

Get list from $.prm.employees for this party_id

...

Get care_plan_id from url

...

Check $.approvals for user's employees (granted_to) on care_plan_id (granted_resources) and $.medication_request_requests.person_id (granted_by)

...

Search Medication request requests by filters: care_plan_id

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

  2. starting_after (cursor to fetch next page)

  3. ending_before (cursor to fetch previous page)

Preconditions

No

Global and configurable parameters

No

Input parameters

...

Input parameter

...

Values

...

Type

...

Description

...

Example

...

care_plan_id

Filters

See on Apiary

Request structure

API paragraph not found

Authorize

...

Access to the resource is also managed by ABAC rules .

Headers

Content-Type:application/json

...

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

Processing

If according to filters requests are not found, WS returns empty data array

...

determined by the System administrator by configuring scopes in the context of clients and roles.

Dictionaries

API paragraph not found

Processing

Service returns all Medication request requests related to the care plan filtered by submitted parameters:

  1. Get all Medication request requests by care_plan_id from medication_request_requests (IL database).

  2. Validate data consistency:

    • Ensure that requested Medication request requests have ABAC context

      • Return 403 ('Access denied') in case of error.

  3. Filter list above by submitted search parameters.

  4. Render a response according to specification with found Medication request requests entities.

Response structure

See on Apiary

...

HTTP status code

Message

What caused the error

200

Response

 

401

Invalid access token

 

403Invalid

scopeYour scope does not allow to access this resource. Missing allowances: medication_request_request:read

Backward compatibility

API paragraph not found