| Table of Contents | ||||
|---|---|---|---|---|
|
Purpose
This WS is designed to verify approval on entity, which aggregate other entities (episode_of_care, diagnostic_report, care_plan), OR forbidden group OR diagnoses group, OR on service_request including it’s permitted_resources OR on cancel for encounter and procedure OR patient.
Specification
...
Link
...
https://medicaleventsmisapi.docs.apiary.io/#reference/approvals/verify-approval/verify-approval
...
Resource
| Table of Contents |
|---|
user POST /api/patients/
...
{
...
id
...
}/
...
approval_request/
...
{id
...
}
...
Scope
...
approval:create
...
Components
...
Approvals
...
Microservices
...
API paragraph not found
...
Protocol type
...
REST
...
Request type
...
PATCH
...
Sync/Async
...
Async
...
Public/Private/Internal
...
Public
Input parameters
...
Input parameter
...
Values
...
Type
...
Description
...
Example
...
patiend_id
...
String
...
mpi_id. Required
...
aff00bf6-68bf-4b49-b66d-f031d48922b3
...
id
...
String
...
approval_id. Required
...
aff00bf6-68bf-4b49-b66d-f031d48922b3
Request structure
See on Apiary
Example:
| Expand | ||
|---|---|---|
| ||
|
Authorize
Verify the validity of access token
Check user scope approval:create in order to perform this action
Headers
Наприклад:
Content-Type:application/json
Authorization:Bearer d368a4b0-4a0e-457a-b267-32359fa6288f
Logic
...
/action/approve with the verification code received from the patient
Validate request
Authorize
Logic
- system checks verification code via otp_verification service PATCH /verifications/:phone_number/actions/complete
- if verification code matches -
...
- system creates new approval
- If not - return
...
If authentication_method_current.type = offline
change status to active
HTTP status codes
...
HTTP status code
...
Message
...
- error
...
200
...
Response
...