Page Comparison

id

uuid

M

Autogenerated

name

varchar

M

is_active

boolean

M

type

varchar

M

Dictionary: MEDICAL_PROGRAM_TYPE

medication_request_allowed

boolean

M

medication_dispense_allowed

boolean

M

medication_request_allowed_text

varchar

O

medication_dispense_allowed_text

varchar

O

medical_program_settings

jsonb

null

O

skip_mnn_in_treatment_period

boolean

false

M

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

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"]

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"]

care_plan_required

boolean

false

M

Allow to create medication request for with reference on care plan

skip_employee_validation

boolean

false

M

Allows to skip all employee validations, including restrictions in the employee_types_to_create_medication_request and speciality_types_

allowed parameters. So, any user who has a scope can create medication request

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

conditions_icpc2_allowed

[varchar]

null

O

 Array of condition codes from eHealth/ICPC2/actions 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

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

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"]

medical_program_settings_text

varchar

O

 Comment on update medical_program_settings

inserted_at

Timestamp: now()

M

Get current date-time

inserted_by

Token: user_id

M

Extract user from token

updated_at

Timestamp: now()

M

Get current date-time

updated_by

Token: user_id

M

Extract user from token