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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Parameter

Type

Default

M/O

Description

1

skip_mnn_in_treatment_period

boolean

null

O

Allow to create medication request with the same innm in one treatment period

2

employee_types_to_create_medication_request

[varchar]

null

O

Allow to create medication request for particular types of employees (if empty - all employee types, which have scopes can create medication request without limitations). Fills with values from EMPLOYEE_TYPE dictionary.

Example: ["DOCTOR", "SPECIALIST"]

3

speciality_types_allowed

[varchar]

null

O

Allows to create:

  • Medication Request for particular specialities $.employees.speciality.speciality(speciality_officio == true) of employees with SPECIALIST type (if empty - all specialists who have scopes can create medication request w/o limitations). 

  • care plan's Activity for particular specialities $.employees.speciality.speciality(speciality_officio == true) of employees. If empty - all employees who have scopes can create Activity w/o any limitations.

Fills with values from SPECIALITY_TYPE dictionary. For example: ["ENDOCRINOLOGY", "FAMILY_DOCTOR"]

4

care_plan_required

boolean

false

M

Allow to create medication/service request for with reference on care plan

5

skip_employee_validation

boolean

null

O

Allows to skip all employee validations, including restrictions in the employee_types_to_create_medication_request and speciality_types_to_create_medication_request parameters. So, any user who has a scope can create medication request

6

conditions_icd10_am_allowed

[varchar]

null

O

Array of condition codes from eHealth/ICD10_AM/condition_codes dictionary. For example: ["M61.25", "L70.0"]

Allows to create:

  • Medication Request Request with encounter in context that should have primary diagnosis with code that correspond to config. 

  • Activity with addresses field of related Care plan that should have condition codes that correspond to config.

If absent - any ICD10_AM condition codes allowed.

Can be combined with codes in conditions_icpc2_allowed

7

conditions_icpc2_allowed

[varchar]

null

O

 Array of condition codes from eHealth/ICPC2/condition_codes dictionary. For example: ["R25","R80","L09"]

Allows to create Medication Request Request or Activity according to the logic as described for conditions_icd10_am_allowed

If absent - any ICPC2 condition codes allowed.

Can be combined with codes in conditions_icpc2_allowed

8

medication_request_max_period_day

integer

null

O

Maximum period length (in days) allowed for the Medication request with the medical program. Has a precedence over the same chart parameter

9

providing_conditions_allowed

[varchar]

null

O

 Allowed terms of service for a Care plan to create activity with the medical program. Fills with values from PROVIDING_CONDITION dictionary. For example: ["INPATIENT", "OUTPATIENT"]

10

skip_medication_request_employee_declaration_verify

boolean

null

O

Allows to skip verification if employee has declaration with patient to create medication request. If true - declaration wont be checked; null/false - declaration will be checked on employee level.

11

skip_medication_request_legal_entity_declaration_verify

boolean

null

O

Allows to skip verification if employee in legal entity that has declaration with patient to create medication request. If true - declaration wont be checked; null/false - declaration will be checked on legal entity level.

12

multi_medication_dispense_allowed

boolean

null

O

Check if medication request can be dispensed partially. If true - one medication request can have multiple medication dispenses; null/false - one medication request can have only one dispense (with the same medication quantity)

13

skip_medication_dispense_sign

boolean

null

O

Check if process medication dispense should be invoked using digital sign. If true - medication dispense process should be performed without usage of digital sign; null/false - medication dispense process should be performed using digital sign.

14

medication_request_notification_disabled

boolean

false

O

Check if patient should not be notified via SMS on operations with medication request (create/reject/resend). If true - patient wont be notified; null/false - patient should be notified.

15

medication_dispense_period_day

integer

null

O

Medication dispense period (in days). If it is absent - get value from medication_dispense_period global parameter

16

skip_contract_provision_verify

boolean

null

O

Check if validations of Contract and Medical Program Provisions should be invoked for the medical program. If true - validations should be skipped, if null/false (absent) - validations should be invoked.

  • No labels