...
Example: https://github.com/Bahmni/default-config/blob/master/openmrs/apps/ot/app.json
Key Fields
Key | Use | Mandatory |
---|---|---|
id | Some unique ID for this block. | Yes |
Extension Params | ||
ignoredTabularViewHeadings | To ignore columns when viewing patient search queues in tabular view | No |
defaultViewAsSurgeonBased | Setting below config as | No |
identifierHeadings | To set a particular column as an identifier when viewing patient search queue in tabular view | Yes |
patientDashboardUrl | When user wants to edit a surgical appointment, the link can be configured to any url configured with additional context passed through query parameters. | Yes |
primarySurgeonsForOT | The configuration is an array of surgeon names. The name correspond to the person name of the provider that you have configured in OpenMRS provider management module. | No |
printListViewTemplateUrl | The print html is configurable to allow to custom print the columns or information needed. | Yes |
calendarView | The start time, end time and the interval of the calendar are configurable. The start time and end time are in 24 hr formats with hours and minutes separated by ‘:’. The dayViewSplit is the interval to be configured in minutes. | No |
startOfWeek | Start day of the week ("Monday") | No |
additionalCustomParam | To exhibit the primary diagnosis of a patient in list view, where a patient has multiple primary diagnoses recorded | No |
Configure patient dashboard link for the Patient Id
...
Code Block | ||||
---|---|---|---|---|
| ||||
“calendarView”: { “dayViewStart”: ”08:00”, “dayViewEnd” : ”18:00”, “dayViewSplit”: ”60” } |
Primary Diagnosis Information in the OT list view
Incorporating the provided configuration, the list view can now exhibit the primary diagnosis of a patient. In cases where a patient has multiple primary diagnoses recorded, all of them will be showcased within the OT list view. Below is a sample configuration to enable this functionality:
Code Block | ||||
---|---|---|---|---|
| ||||
"additionalCustomParam": "patientObservations" |
Note | ||
---|---|---|
| ||
This feature is accessible only if the operation theatre backend supports reading this value. To enable this functionality, set the `obs.conceptMappingsForOT` parameter to `"org.openmrs.module.emrapi:Coded Diagnosis,org.openmrs.module.emrapi:Non-coded Diagnosis"`. This parameter is a comma-separated list of key-value pairs in the format of source:code for concept mappings, determining which observations are to be displayed in the OT module List view. For instance, if we aim to retrieve observations recorded under the concept mappings with the source "org.openmrs.module.emrapi" and code "Coded Diagnosis," and another with the source "org.openmrs.module.emrapi" and code "Non-coded Diagnosis," the parameter value should be set as follows: `"org.openmrs.module.emrapi:Coded Diagnosis,org.openmrs.module.emrapi:Non-coded Diagnosis"`. Note that the source and code key-value pairs are separated by a colon symbol. |