Versions Compared

Old Version 3

changes.mady.by.user Anzhela Kovalenko (SoE eHealth)

Saved on

compared with

New Version 4

changes.mady.by.user Iryna Lishtaba (SoE eHealth)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

REST API method / Метод REST API (настанова) (remove the link block before publishing the document)

...

Page Properties
idpage_properties_method_REST API

Document type

Метод REST API

Guideline ID

GUI-0011

Author

@

Document version

1

Document status

DRAFT

Date of creation

ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD)

Date of update

ХХ.ХХ.ХХХХ (дата зміни версії)

Method API ID

API-005-008-002-0151

Microservices (namespace)

IL

Component

ePrescription

Component ID

COM-005-008

Link на API-специфікацію

https://ehealthmisapi1.docs.apiary.io/#reference/public.-reimbursement/medication-request/get-medication-request-printout-form

Resource

{{host}}/api/medication_requests/{{id}}/printout_form

Scope

medication_request:details

Protocol type

REST

Request type

GET

Sync/Async

Sync

Public/Private

Public

...

Access to the method is defined by the scope medication_request:details. Permission for this scope is determined by the System administrator by configuring scopes in the context of clients and roles.

Dictionaries

Provides a list of links to dictionaries that are available in ConfluenceNo

Input parameters

Description of input parameters

Input parameter

Mandatory

Type

Description

Example

1

person_id

  M

String

person_id of a patient. Required.

5e661b15-a39a-4713-b18e-ba03a4a48ecc

2

id

M

String

Medication request identifier. Required.

d290f1ee-6c54-4b01-90e6-d701748f0851

Request structure

See on API-specification (посилання на сторінку з API-специфікацією)

Description of the REST API request structure, example

Expand
titleExample
Code Block
...
Perform Get medication requests details with corresponding validations.
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:details')
    • Return (403, 'Your scope does not allow to access this resource. Missing allowances: medication_request:details') in case of invalid scope(s).
Access to the resource is also managed by ABAC rules (EN) .
Processing
Get Medication request by ID
...
Parameter
Source
id
MEDICATION_REQUEST_REQUEST_PRINTOUT_FORM_TEMPLATE_ID
 
Logic of generation of fields for the printout form is described in 1f1fa-1f1e6Sign Medication Request Request.
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)
Description of the REST API response structure, example
 Expand
titleExample
 Code Block
{
  "meta": {
    "code": 200,
    "url": "https://example.com/resource",
    "type": "object",
    "request_id": "req-adasdoijasdojsda"
  },
  "data": {
    "id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
    "printout_form": "Medication request content"
  }
}
...
401
Response code
HTTP Status code
Message
Internal name
Description
1
Базові
2
200
Response
 
3
Invalid access token
 
4
401
Unauthorized
Помилка підтвердження
5
403
Your scope does not allow to access this resource. Missing allowances: medication_request:details
6
1000
404
Composition not found
COMPOSITION_NOT_FOUND_404
Не знайдено медичний висновок
7
Специфічні
8
422
Only for active MPI record can be created medication request!
Специфічні
5
Post-processing processes
Description of actions performed on data after processingNo
Technical modules where the method is used
List of pages describing technical modules where the method is used
 Page Properties Report
headingsID ТМ, Статус
cqllabel = "tr-mis"
...