/
[DRAFT] Get Diagnostic Report by search params (Patient Summary) [API-007-008-006-0288]

ЕСОЗ - публічна документація

[DRAFT] Get Diagnostic Report by search params (Patient Summary) [API-007-008-006-0288]

Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою.

https://e-health-ua.atlassian.net/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document)

Properties of a REST API method document

Document type

Метод REST API

Document title

[DRAFT] Get Diagnostic Report by search params (Patient Summary) [API-007-008-006-0288]

Guideline ID

GUI-0011

Author

@Mykhaylo Khapchyk (SoE eHealth)

Document version

1

Document status

DRAFT

Date of creation

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

Date of update

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

Method API ID

API-007-008-006-0288

Microservices (namespace)

ME

Component

Patient Summary

Component ID

COM-007-008

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

https://medicaleventsmisapi.docs.apiary.io/#reference/medical-events/patient-summary/get-diagnostic-report-by-search-params

Resource

{{host}}/api/patients/{{patient_id}}/summary/diagnostic_reports/

Scope

patient_summary:read

Protocol type

REST

Request type

GET

Sync/Async

Sync

Public/Private

Public

Purpose

This web service is designed to return diagnostic reports list for a specified patient.

Logic

N/A (Not applicable)

Configuration parameters

N/A (Not applicable)

Dictionaries

  1. eHealth/resources - patient (parameter “patient_id“ in request)

  2. eHealth/resources - service (parameter “code“ in request / response)

  3. eHealth/resources - service_request (parameter “based_on“ in response)

  4. eHealth/diagnostic_report_statuses (parameter “status“ in response)

  5. eHealth/diagnostic_report_categories (parameter “category“ in response)

  6. eHealth/ICD10_AM/condition_codes (parameter “conclusion_code“ in response)

  7. eHealth/resources - specimen (parameter “specimens“ in response)

  8. eHealth/resources - equipment (parameter “used_references“ in response)

  9. eHealth/resources - employee (parameter “recorded_by“ in response)

  10. eHealth/resources - encounter (parameter “encounter“ in response)

  11. eHealth/resources - episode (parameter “origin_episode“ in response)

  12. eHealth/resources - division (parameter “division“ in response)

  13. eHealth/resources - legal_enity (parameter “managing_organization“ in response)

  14. eHealth/resources - employee (parameter “performer“ in response)

  15. eHealth/report_origins (parameter “report_origin“ in response)

  16. eHealth/resources - employee (parameter “results_interpreter“ in response)

  17. eHealth/cancellation_reasons (parameter “cancellation_reason“ in response)

Input parameters

Input parameter

Mandatory

Type

Description

Example

Input parameter

Mandatory

Type

Description

Example

1

patient_id

 M

String

Unique MPI patient identifier

70a9e15b-b71b-4caf-8f2e-ff247e8a5677

2

issued_from

 

String

 

1990-01-01

3

issued_to

 

String

 

2017-01-01

4

code

 

String

Service code

12345

5

page

 

Number

Page number

2

6

page_size

 

Number

A limit on the number of objects to be returned, between 1 and 100. Default: 50

50

Request structure

See on API-specification

Headers

See on Headers

Authorize

Request to process the request using a token in the headers

Request data validation

Validate token

  • Verify the validity of access token

    • Return 401 in case validation fails

  • Verify token is not expired

    • in case error return 401 

Validate scopes

  • Check user scopes in order to perform this action (scope = 'patient_summary:read')

    1. Return 403 in case invalid scope(s)

Access to the resource is also managed by ABAC module.

Validate patient

  • Validate patient exists in MongoDB

    • In case of error return 404 not found

Processing

  1. Get all patient's diagnostic reports

  2. Filter using Forbidden Groups

  3. Filter using configuration param SUMMARY_DIAGNOSTIC_REPORTS_ALLOWED in order to return only allowed codes

  4. Apply filters provided by user

  5. Render a response according to specification

Response structure examples

See on API-specification

HTTP status codes

Response code

HTTP Status code

Message

Internal name

Description

Response code

HTTP Status code

Message

Internal name

Description

1

Базові

2

 

200

 

 Response

 

3

 

401

 

Access token validation failed

 

4

 

401

 

Access token expired

 

5

 

403

Your scope does not allow to access this resource. Missing allowances: patient_summary:read 

Forbiden

 

6

 

403

Access denied

Forbiden

 

7

 

404

 

Not found

 

8

Специфічні

Post-processing processes

N/A (Not applicable)

Technical modules where the method is used

N/A (Not applicable)

ЕСОЗ - публічна документація