Info |
---|
Note |
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Info |
---|
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
Expand | ||
---|---|---|
| ||
MIS/Medical employee->Compositions: Create Composition POST/patients/composition |
Configuration parameter
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
...
N/A
Dictionaries
N/A
Input parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | compositionId |
| String ($uuid) (path) | Composition object ID | 8c696fa4-6607-4aef-bab7-33cabc2dda2c |
2 | patientId | String ($uuid) (path) | Patient object ID | 6a524088-c3f6-44ef-bcea-12a8e2900431 | |
3 | episodeId | String ($uuid) (path) | Episode of care object ID | e4f8c204-4879-4a90-a89f-707ffd7f02c4 | |
4 | encounterId | String ($uuid) (path) | Encounter object ID | d44ac2e9-9c83-4f5a-9ce1-0b764f260fff |
...
Expand | ||
---|---|---|
| ||
|
Headers
...
Key
...
Value
...
Mandatory
...
Description
...
Example
...
Content-Type
...
application/json
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer {token}
...
Перевірка користувача
...
Authorization: Bearer {token}
...
api-key
...
{secret}
...
Секретний ключ
...
api-key: {secret}
Request data validation
|
Headers
Request data validation
Authorize
Check user scopes in order to perform this action (scope = 'composition:read')
return 401 (Unauthorized) in case of invalid scope(s)
Composition is not directly involved in the processing of the access authorization module (in the ABAC rules and in the creation of approvals). However, the getComposition request contains encounter's and episod's IDs. That's mean approve for obtain a composition is inherited from these objects and determined by the approvals on them.
...
In case of wrong request data - return 404 “Not Found“ - “no Route matched with those values”
Processing
...
Processing
N/A
Response structure examples
...
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
Response code | HTTP Status code | Message | Internal name | Description | ||||
---|---|---|---|---|---|---|---|---|
1 | Базові | |||||||
2 | 401(Unauthorized) in case of invalid scope(s) | 3 | 403 | Access denied | In the case of access denied to view the Composition according to the rules of ABAK | |||
43 | 404 | In case the Composition does not exist | The Composition wasn’t found | |||||
54 | Специфічні | |||||||
65 |
Post-processing processes
Description of actions performed on data after processing
Technical modules where the method is used
List of pages describing technical N/A
Technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|
...