...
...
...
...
Purpose
This WS is designed to return medication request details by MSP users. Receiving Medication request is possible by identifier or request_number
Specification
...
Link
...
...
Посилання на Apiary або Swagger
...
Resource
...
/api/persons/{{person_id}}/medication_requests/{{id}}
...
Посилання на ресурс, наприклад: /api/persons/create
...
Scope
...
medication_request:details
...
Scope для доступу
...
Components
...
ePrescription
...
Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription
...
Microservices
...
API paragraph not found
...
Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC
...
Protocol type
...
REST
...
Тип протоколу, який використовується запитом, наприклад: SOAP | REST
...
Request type
...
GET
...
Тип запиту API, наприклад: GET, POST, PATCH…
...
Sync/Async
...
Sync
...
Метод є синхронним чи асинхронним?
...
Public/Private/Internal
...
Public
Logic
Процеси роботи з випискою електронних рецептів
Service returns specified Medication requests related to the patient:
Get Medication requests from medication_requests (OPS database)
Validate data consistency:
Ensure that requested Medication requests relates to requested Patient (from URL)
Return 403 ('Access denied') in case of error
Render a response according to specification
Calculate medication remaining quantity:
Select all Medication dispenses in status PROCESSED related to the Medication request
Sum medication_qty in the filtered Medication dispenses as dispensed_qty
Calculate medication_remaining_qty = medication_qty - dispensed_qty
Return medication_remaining_qty in the response
Preconditions
No
Global and configurable parameters
No
Input parameters
...
Input parameter
...
Values
...
Type
...
Description
...
Example
...
person_id
...
String
...
person_id of a patient. Required.
...
5e661b15-a39a-4713-b18e-ba03a4a48ecc
...
id
...
String
...
Medication Request identifier OR request_number. Required.
...
48416485-cc98-46c4-8bba-e321de9e1ecd
Filters
No
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: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) .
Headers
Content-Type:application/json
Authorization:Bearer c2778f3064753ea70de870a53795f5c9
Validate request
API paragraph not found
Request data validation
API paragraph not found
Dictionaries
API paragraph not found
Processing
API paragraph not found
Response structure
See on Apiary
Example:
Expand | ||
---|---|---|
| ||
|
Post-processing processes
No
HTTP status codes
...
HTTP status code
...
Message
...
What caused the error
...
200
...
Response
...
...
401
...
Invalid access token
...
...
403
...
Your scope does not allow to access this resource. Missing allowances: medication_request:details
Access denied
Backward compatibility
API paragraph not foundThe page is not supported. The method requirements can be found here Get medication requests details [API-005-008-002-0148]