Note |
---|
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Table of Contents | ||
---|---|---|
|
...
Document type
...
Метод REST API
...
Document title
...
Note |
---|
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Table of Contents | ||
---|---|---|
|
Document type | Метод REST API |
---|---|
Document title | [DRAFT] Get Service request details [API-007-010-001-0311] |
Guideline ID | GUI-0011 |
Author | @ |
Document version | 1 |
Document status | DRAFT |
Date of creation | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) |
Method API ID | API-007-010-001-0311 |
Microservices (namespace) | ME |
Component | Service request |
Component ID | COM-007-010 |
Link на API-специфікацію |
Resource | {{host}}/api/patients/{{patient_id}}/service_requests/{{service_request_id}} |
---|---|
Scope | service_request:read |
Protocol type | REST |
Request type | GET |
Sync/Async | Sync |
Public/Private | Public |
Purpose
This method returns the details of the service request by identifier. without specifying the episode of care
Logic
Description of the working algorithm of the API method and the interaction of services with each other add Service logic (if necessary)N/A
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
Provides a list of links to dictionaries that are available in ConfluenceN/A
Dictionaries
N/A
Input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | patient_id |
| String | Unique patient identifier |
|
2 | service_request_id |
| String | Unique service request identifier |
|
Request structure
See on Apiary
See on API-specification
...
title | Example |
---|
...
Headers
Key
Value
Mandatory
Description
Example
Content-Type
application/json
M
Тип контенту
Content-Type:application/json
Authorization
Bearer {token}
Authorization: Bearer {token}
api-key
{secret}
|
Request structure
See on API-specification
Expand | ||
---|---|---|
| ||
|
Headers
Request data validation
Authorize
Verify the validity of access token
Return (401, 'unauthorized') in case of validation fails
Verify that token is not expired
in case of error - return (401, 'unauthorized')
Check user scopes in order to perform this action (scope = 'service_request:read')
Return (403, 'invalid scopes') in case of invalid scope(s)
...
Response structure examples
...
See on API-specification
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Expand | |||||
---|---|---|---|---|---|
| |||||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | |
---|---|---|---|---|---|
1 | Базові | ||||
2 |
401 |
Unauthorized |
3 | 403 | Access denied | |||
4 | 403 |
Invalid scopes | ||
5 | 404 |
Service request not found |
| ||||
6 | Специфічні | ||||
7 |
|
Post-processing processes
Description of actions performed on data after processingN/A
Technical modules where the method is used
List of pages describing technical modules where the method is used
Название | ID ТМ | Статус |
---|---|---|
TM0112 | ||
...