| Status | ||
|---|---|---|
|
| Table of Contents |
|---|
Schema
Examples
Services - Service Groups relations example
...
| Name | Type | M/O | Description | |||
|---|---|---|---|---|---|---|
| id | UUID | M | unique identifier of the record | |||
| code | string | M | service code | |||
| name | string | M | service name | |||
| is_active | boolean | M | parent_id | UUID | O | for future use (composition_idused for deletion purposes (since we can not delete data from e-Health) |
| category | string | MOenum | category of service | |||
| is_composition | boolean | M | for future use | |||
| request_allowed | boolean | M | if true - service request can be created using this service | |||
| inserted_at | datetime | M | date and time when record was inserted | |||
| inserted_by | datetimeuuid | M | id of the user who inserted this record | |||
| updated_at | datetime | M | date and time when record was updated | |||
| updated_by | datetimeuuid | M | id of the user who updated this record |
Service group
| Name | Type | M/O | Description |
|---|---|---|---|
| id | UUID | M | unique identifier of the record |
| code | string | M | service group code |
| name | string | M | name of the service group |
| is_active | boolean | M | used for deletion purposes (since we can not delete data from e-Health) |
| parent_group_id | UUID | O | identifier of parent group |
| request_allowed | boolean | M | if true - service request can be created using this group |
| inserted_at | datetime | M | date and time when record was inserted |
| inserted_by | datetimeuuid | M | id of the user who inserted this record |
| updated_at | datetime | M | date and time when record was updated |
| updated_by | datetimeuuid | M | id of the user who updated this record |
Service in group
| Name | Type | M/O | Description |
|---|---|---|---|
| id | UUID | M | unique identifier of the record |
| service_id | UUID | M | id of service |
| group_id | UUID | M | if of group |
| alias | string | O | "name" for link between service and group |
| is_active | boolean | M | used for deletion purposes (since we can not delete data from e-Health) |
| inserted_at | datetime | M | date and time when record was inserted |
| inserted_by | datetimeuuid | M | id of the user who inserted this record |
| updated_at | datetime | M | date and time when record was updated |
| updated_by | datetimeuuid | M | id of the user who updated this record |
Programs (existing reimbursement medical_programs table is used)
...
Name | Type | M/O | Description and constraints | Status |
|---|---|---|---|---|
| id | uuid | M | unique identifier of the record | |
| is_active | boolean | M | used for deletion purposes (since we can not delete data from e-Health) | |
| name | varchar | M | name of the medical program | |
| inserted_at | timestamp | M | date and time when record was inserted | |
| inserted_by | uuid | M | id of the user who inserted this record | |
| updated_at | timestamp | M | date and time when record was updated | |
| updated_by | uuid | M | id of the user who updated this record | |
same_mnn_in_treatment_period | boolean | M | Not used for service programs | |
| type | varchar | M | medication, service | NEW |
| legal_entity_types | jsonb | M | Used for service programs, array of legal_entity_types dictionary values. Program can be set on service request if it were created by an employee from legal entity with one of types listed in array | NEW |
Program_services (new table)
Name | Type | M/O | Description and constraints | Status |
|---|---|---|---|---|
| id | uuid | M | unique identifier of the record | |
| service_id | uuid | O | service_id OR service_group_id is mandatory | |
| medical_program_id | uuid | M | id of medical program | |
| service_group_id | uuid | O | service_id OR service_group_id is mandatory | |
request_allowed | boolean | M | if true - service request can be created using the service or service group under the program | |
| consumer_price | double | M | price for service/service group provision under the program | |
| description | text | O | used for text description of un-automated conditions which should be checked for program member vs patient qualification (e.g. sex or age of patient) | |
| is_active | boolean | M | used for deletion purposes (since we can not delete data from e-Health) | |
| inserted_at | timestamp | M | date and time when record was inserted | |
| inserted_by | uuid | M | id of the user who inserted this record | |
| updated_at | timestamp | M | date and time when record was updated | |
| updated_by | uuid | M | id of the user who updated this record |
contract_program_
membersservices (new table)
Name | Type | M/O | Description and constraints | Status |
|---|---|---|---|---|
| id | uuid | M | unique identifier of the record | |
| contract_id | uuid | M | FK(contract_id) | |
| program_memberservices_id | uuid | M | FK(program_membersservices) | |
| is_active | boolean | M | used for deletion purposes (since we can not delete data from e-Health) | |
| inserted_at | timestamp | M | date and time when record was inserted | |
| inserted_by | uuid | M | id of the user who inserted this record | |
| updated_at | timestamp | M | date and time when record was updated | |
| updated_by | uuid | M | id of the user who updated this record |
Endpoint response tree structure
Node 1service_groups w/o sub-groups, w/o parent_group_idservice_groups with sub-groups, w/o parent_group_idservices which aren't included in any service_groups
Node 2service_groups with parent_group_id with service_groups of the first nodeservices which are included in the service_groups of the Node 1
Node 3service_groups with parent_group_id with service_groups from the second nodeservices which are included in the service_groups of the Node 2
Node 4service_groups with parent_group_id with service_groups from the third nodeservices which are included in the service_groups of the Node 3
Node 5services which are included in the service_groups of the Node 4