A display control is a widget that displays a specific medical domain object. It takes in configuration that specifies the context (patient, visit etc) and other parameters (display specific feature toggles), retrieves relevant data on its own and displays it where it is placed on the application.
This page lists down currently existing display controls, places where they can currently be configured to be used and the configuration details.
Jump to one of the sections:
Specify one or two column layout
We can specify one or two column layout for display controls. Options can be "Full-Page" and "Half-Page", with "Half-Page" being the default. When the "Full-Page" layout is specified for a display control it should appear on the top of the dashboard.
Sample
"sections": {
"diagnosis": {
"title": "Diagnosis",
"name": "diagnosis",
"showCertainty": true,
"showOrder": true,
"displayType": "Full-Page"
},
"disposition": {
"title": "Disposition",
"name": "disposition",
"numberOfVisits": 1,
"displayType": "Full-Page"
},
"radiology": {
"title": "Radiology",
"name": "radiology"
},
"programs": {
"title": "Programs",
"name": "programs"
}
}
Observation Control
Sample config
"nutritionalValues": {
"title": "Nutritional Values",
"name": "vitals",
"isObservation": true,
"dashboardParams": {
"conceptNames": ["Height", "Weight", "BMI", "BMI STATUS"],
"scope": "latest" or "numberOfVisits": "4",
"showGroupDateTime": false
} ,
"allObservationDetails": {
"conceptNames": ["Height", "Weight", "BMI", "BMI STATUS"],
"showDetailsButton": true,
"pivotTable": {
"numberOfVisits": "4",
"groupBy": "encounters",
"obsConcepts": ["Vitals", "Height", "Weight", "Pathology"],
"drugConcepts": "",
"labConcepts": ""
},
"observationGraph" : {
"type": "observationGraph",
"name": "observationGraph",
"title": "Temperature",
"config": {
"yAxisConcepts": ["Temperature"],
"numberOfVisits": 3
}
}
}
}
Key | Info |
---|---|
Title | Indicates the title that will be displayed on the dashboard/visit page for the section |
Name | The name/id for the control that needs to be picked from the code |
conceptNames | Specify the concept names of the concepts that need to be displayed in this section |
scope | Can be latest/blank. If "latest", then the latest value of the observation across visits is shown. If a scope is not mentioned, then the number of visits has to be mentioned. Otherwise if the scope is blank then the observation values across all visits are displayed |
isObservation | Specifies whether the given section is an observation control or a disease template control. If this is set to true then the section behaves as an observation control |
observationGraph | Indicates the configuration for the pivot table/flowsheet |
numberOfVisits | Specifies the number of visits for which data has to be displayed on the pivot table |
groupBy | Can be encounters/visits. If grouped by the encounter, then the data is displayed per encounter in the pivot table. If grouped by the visit, then the latest value of the observations in each visit is displayed in the pivot table. |
obsConcept | Implementor must specify the concept names of the observations that need to be displayed in the pivot table |
drugConcept | Implementor must specify the concept names of the drugs that need to be displayed in the pivot table |
labConcept | Implementor must specify the concept names of the lab tests that need to be displayed in the pivot table |
dashboardParams | Indicates the configuration for the dashboard |
allObservationDetails | Indicates the configuration for the details page (All Observations Page) |
showDetailsButton | Configuration to display audit information when '+ ' sign is clicked. If set to false, the '+' button will not be displayed. |
showGroupDateTime | Configuration to display grouped encounter date time. If set to false, it is hidden. Default value is true(which means it is treated as true, if nothing specified). Should be separately configured for both dashboard and allDetails page |
For Initial And Latest Observations
Sample config
"atAdmission": {
"type": "observation",
"title": "At Admission",
"config": {
"conceptNames": ["Weight", "Height", "BMI"],
"scope": "initial"
}
}
"atDischarge": {
"type": "observation",
"title": "At Discharge",
"config": {
"conceptNames": ["Weight"],
"scope": "latest"
}
}
Disease Template Control
Sample config
"diabetes": {
"title": "Diabetes",
"templateName": "Diabetes Templates",
"name": "diseaseTemplate",
"dashboardParams":{
"showOnly": [],
"showGroupDateTime": false
},
"allDiseaseDetails": {
"showOnly":[],
"showDetailsButton": true,
"pivotTable": {
"numberOfVisits": "15",
"groupBy": "encounters",
"obsConcepts": ["Weight", "Height", "Systolic", "Diastolic", "Diabetes, Foot Exam", "Diabetes, Eye Exam","Diabetes, Diabetes, Complications"],
"drugConcepts": ["Ipratropium Pressurised", "Garbhpal Rasa", "Lente Insulin"],
"labConcepts": ["RBS", "FBS", "PP2BS", "Hb1AC", "Creatinine", "Albumin", "Polymorph"]
},
"observationGraph" : {
"type": "observationGraph",
"name": "observationGraph",
"title": "Temperature",
"config": {
"yAxisConcepts": ["Temperature"],
"numberOfVisits": 3
}
}
}
}
Key | Info |
---|---|
title | Indicates the title that will be displayed on the dashboard/visit page for the section |
templateName | indicates the name of the disease template in openMRS that needs to be displayed |
name | the name/id for the control that needs to be picked from the code |
showOnly | specify the concept names of the concepts that need to be displayed in this section. If blank, then all the concepts in that disease template will be displayed |
pivotTable | indicates the configuration for the pivot table/flowsheet |
observationGraph | indicates the configuration for the observationGraph (OPTIONAL) |
numberOfVisits | specifies the number of visits for which data has to be displayed on the pivot table |
groupBy | can be encounters/visits. If grouped by the encounter, then the data is displayed per encounter in the pivot table. If grouped by the visit, then the latest value of the observations in each visit is displayed in the pivot table. |
obsConcepts | implementor must specify the concept names of the observations that need to be displayed in the pivot table |
drugConcepts | implementor must specify the concept names of the drugs that need to be displayed in the pivot table |
labConcepts | implementor must specify the concept names of the lab tests that need to be displayed in the pivot table |
dashboardParams | indicates the configuration for the dashboard |
allDiseaseDetails | indicates the configuration for the details page (All Disease Details Page) |
showDetailsButton | Configuration to display audit information when '+ ' sign is clicked. If set to false, the '+' button will not be displayed. |
showGroupDateTime | Configuration to display grouped encounter date time. If set to false, it is hidden. Default value is true(which means it is treated as true, if nothing specified). Should be separately configured for both dashboard and allDetails page. |
Drug Order Control
Sample config
"treatment": {
"title": "Treatments",
"name": "treatment",
"dashboardParams": {
"showFlowSheet": false,
"showListView": true,
"showRoute": false,
"showDrugForm": false,
"numberOfVisits": 2,
"showOtherActive": true,
"showDetailsButton": false
},
"allTreatmentDetails": {
"title": "Treatments",
"showFlowSheet": false,
"showListView": true,
"showRoute": true,
"showDrugForm": true,
"numberOfVisits": 5,
"showOtherActive": true,
"showDetailsButton": true
}
}
Key | Info |
---|---|
title | Indicates the title that will be displayed on the dashboard/visit page for the section |
name | the name/id for the control that needs to be picked from the code |
showFlowSheet | configuration to display the flowsheet (treatment chart). If it is on, the flowsheet will be displayed along with the treatment details for IPD patients. |
showListView | configuration to display the treatment details list. If set to false along with showFlowSheet, only the header will be displayed. |
showRoute | configuration to display the route information. If you don't specify the "showRoute" in the treatment section, the default value will be false. |
showDrugForm | configuration to display the drug form information. If you don't specify the "showDrugForm" in the treatment section, the default value will be false. |
numberOfVisits | specifies the number of visits for which data has to be displayed |
showOtherActive | if set to true, then display a separate section "Other Active Drugs" which displays active drugs from other visits. |
showDetailsButton | Configuration to display audit information when '+ ' sign is clicked. If set to false, the '+' button will not be displayed. |
dashboardParams | indicates the configuration for the dashboard |
allTreatmentDetails | Indicates the configuration for the details page (All Treatments Page) |
Lab Result Control
Sample config
"labResults": {
"title": "Lab Results",
"name": "labOrders",
"dashboardParams": {
"title": null,
"numberOfVisits": 1,
"showChart": false,
"showTable": true,
"showDetailsButton": false,
"showNormalLabResults": true,
"showCommentsExpanded": true,
"showAccessionNotes": true,
"visitUuids": null, //ignores numberOfVisits if provided
"patientUuid: null, //mandatory if numberOfVisits provided
},
"allLabDetails": {
"numberOfVisits": 3,
"observationGraph" : {
"type": "observationGraph",
"name": "observationGraph",
"title": "Temperature",
"config": {
"yAxisConcepts": ["Temperature"],
"numberOfVisits": 3
}
}
}
Key | Info |
---|---|
dashboardParams | indicates the configuration for the dashboard |
title | Indicates the title that will be displayed on the dashboard/visit page for the section |
name | the name/id for the control that needs to be picked from the code |
numberOfVisits | specifies the number of visits for which data has to be displayed |
showChart | configuration to display the investigation chart. If it is on, the investigation chart will be displayed along with the lab results table for IPD patients |
showTable | configuration to display the lab results table. If set to false along with showFlowSheet, only the header will be displayed. |
showDetailsButton | Configuration to display audit information when '+ ' sign is clicked. If set to false, the '+' button will not be displayed. |
showNormalLabResults | Show lab results that are not marked abnormal in OpenElis. |
showCommentsExpanded | Show comments expanded where they are present. The comments section will be collapsed by default if there are no comments mentioned in OpenElis |
showAccessionNotes | Display Accession Notes provided by Lab Manager in OpenElis |
allLabDetails | indicates the configuration for the details page (All LabDetails Page) |
observationGraph | indicates the configuration for the observationGraph (OPTIONAL) |
Diagnosis Control
Sample config
"diagnosis": {
"title": "Diagnosis",
"showRuledOutDiagnoses": false,
"name": "diagnosis",
"showCertainty": true,
"showOrder": true,
},
Key | Info |
---|---|
title | Indicates the title that will be displayed on the dashboard/visit page for the section |
name | the name/id for the control that needs to be picked from the code |
showRuledOutDiagnoses | Indicates whether to filter out ruled out diagnoses or not. If set to false, ruled out diagnoses will not be displayed in the display control |
showCertainty | Indicates whether certainty(CONFIRMED/PRESUMED) of the diagnosis should be displayed for each diagnosis in the display control. If set to false, certainty of the diagnosis will not be displayed for the diagnoses. |
showOrder | Indicates whether order(PRIMARY/SECONDARY) of the diagnosis should be displayed for each diagnosis in the display control. If set to false, orders for the diagnosis will not be displayed for the diagnoses. |
Patient Profile Control
Sample config
"patientInformation": {
"title" : "Patient Information",
"name" : "patientInformation",
"patientAttributes" : ["caste", "class", "education", "occupation"],
"showDOB" : false
}
Key | Info |
---|---|
showDOB | Indicates whether date of birth should be displayed in the control. Default value is true if nothing mentioned |
Disposition Control
Sample config
"disposition": {
"title": "Disposition",
"name":"disposition",
"numberOfVisits": 2
}
Graph Control
Sample config
"temperature": {
"type": "observationGraph",
"name": "observationGraph",
"title": "Temperature",
"config": {
"yAxisConcepts": ["Temperature"],
"xAxisConcept" : "observationDateTime",
"numberOfVisits": 3
}
}
Key | Info |
---|---|
type | the type/id for the control that needs to be picked from the code. (Required in Visit page) |
name | the name/id for the control that needs to be picked from the code. (Required) |
title | indicates the title that will be displayed on the dashboard/visit page for the section. (Required) |
yAxisConcepts | array of concepts for which observations need to be plotted on the graph. (Required) |
xAxisConcepts | concept on X Axis (observationDateTime, age or any concept) (Required) |
numberOfVisits | specifies the number of visits for which data has to be displayed. (Optional) |
Graph With Reference Data Control
Graph Control Config becomes Chart With Reference Data Config with the addition of the 'referenceData' in the config section referring to the .csv file as shown below
"growthChart": {
"type": "observationGraph",
"name": "observationGraph",
"title": "Growth Chart",
"config": {
"yAxisConcepts": [ "Weight" ],
"referenceData": "growthChartReference.csv",
"numberOfVisits": 20
}
}
Key | Info |
---|---|
yAxisConcepts | It can be any Numeric Concept name. |
referenceData | It would be name of the csv file to be loaded. |
numberOfVisits | It is the number of visits for which data has to be displayed. |
Sample Reference Data CSV file
Gender, Age, Ref1, Ref2
M, 1, 10.5, 12.5
M, 2, 20.5, 22.5
F, 1, 9.5, 12
F, 2, 19.5, 22
- First row is the header row
- Age, Gender column name should always be 'Age', 'Gender' labels
- Age, Gender columns are mandatory
- Age is always assumed to be months (you can give decimals to represent days)
- Other columns will correspond to the each reference line
Orders Control
Displays all the orders (for configured number of visits) and associated observations (scope latest always) for an orderType configured below.
Sample config
"labOrdersControl": {
"orderType": "Lab Order",
"name": "ordersControl",
"title": "Lab Orders Display Control",
"dashboardParams": {
"conceptNames": ["Systolic", "Diastolic", "Posture", "Temperature"],
"numberOfVisits": "4"
} ,
"allOrdersDetails": {
"conceptNames": ["Systolic", "Diastolic", "Posture", "Temperature"]
}
}
Key | Info |
---|---|
orderType | type of the order you want to display (Required) |
name | the name/id for the control that needs to be picked from the code. (Required) |
title | indicates the title that will be displayed on the dashboard/visit page for the section. (Required) |
conceptNames | Specify the concept names of the concepts that need to be displayed in this section. (Required) |
numberOfVisits | specifies the number of visits for which orders has to be displayed. (Optional) |
dashboardParams | indicates the configuration for the dashboard |
allOrdersDetails | Indicates the configuration for the details page (All Orders Page) |
Orders Control on the Visit Page
The configuration of the visit page is the "visit.json" file that is under Clinical App. To configure the orders control on the visit page, add the following config.
"radiologyOrderControl": {
"type": "order",
"title": "Radiology Order Display Control",
"config": {
"title": "Radiology Order Display Control",
"name": "ordersControl",
"orderType": "Radiology Order",
"conceptNames":["Systolic", "Diastolic", "Posture", "Temperature"]
}
}
Programs Control
"programs": {
"title": "Programs",
"name": "programs"
}
Key | Information |
---|---|
title | The title to be shown in the display control |
name | Should be 'programs' |
Pacs Orders Control
"allPackOrders": {
"orderType": "Radiology Order",
"name": "pacsOrders",
"title": "ALL PACS ORDER",
"dashboardParams":{
"pacsImageUrl":"http://10.0.0.10:8080/oviyam2/viewer.html?patientID={{patientID}}&accessionNumber={{orderNumber}}",
"numberOfVisits":4
}
}
Key | Information | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
title | The title to be shown in the display control | ||||||||||||
name | Should be 'pacsOrders' | ||||||||||||
orderType | Only the orders of this type will shown in the display control | ||||||||||||
dashboardParams |
|
Flow Sheet Control
The flow sheet found in the Observations Display Control and the Disease Template Display Control can be independently set on the dashboard by using the flow sheet display control.
"flowsheet": { "name": "flowSheet", "title": "Diabetes Flow Sheet", "dashboardParams": { "numberOfVisits": "5", "groupBy": "visits", "obsConcepts": [ "Diabetes, Blood Pressure", "Diabetes, A1C" ], "labConcepts": [ "RBS", "FBS" ] }, "allFlowSheetDetails": { "numberOfVisits": "10", "groupBy": "visits", "obsConcepts": [ "Diabetes, Blood Pressure", "Diabetes, A1C", ], "labConcepts": [ "RBS", "FBS" ], "drugConcepts": [ "Metformin" ], } }
Key | Information | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
title | Title of the visit tab. | ||||||||||||||
dashboardParams | Parameters of display control on the dashboard.
| ||||||||||||||
allFlowSheetDetails | Parameters for configuration in the expanded view. Elements inside have the same format as elements inside dashboardParams. If empty, defaults to dashboardParams | ||||||||||||||
Custom Control
Bahmni allows implementers to create their own custom display control.
The following configuration needs to be added in visit.json (openmrs/apps/clinical/visit.json) which will display the custom display control in different visit tabs.
We are configuring the birth certificate in the following example.
"birthCertificate": { "title": "Birth Certificate", "printing": { "title": "Bahmni", "header": "Certificate", "logo": "../images/bahmniLogo.png" }, "sections": { "Birth Certificate": { "type": "custom", "config": { "title": "Birth Certificate", "template": "<birth-certificate></birth-certificate>" } } } }
Key | Information |
---|---|
title | Title of the visit tab. |
printing | Add printing section to enable the print button on visit page. |
title - Title in print out. | |
header - Header in print out. | |
logo - Logo to display in print out. | |
type | "custom" (Required and should always be custom) |
config | configuration for the custom display control. |
title - title of the custom directive | |
template - the directive which you want to show. |
Bahmni provides customDisplayControl module which will provide basic connection b/w the app and config.
You can add new directives as per your requirement in the "openmrs/apps/customDisplayControl/js/customControl.js" file. (Make sure you can create new custom directives only in the existing file)
New directives should be under the same module. ("bahmni.common.displaycontrol.custom"). The scope of the new directive will have patient, visitUuid and config.
We are adding a birthCertificate as new directive in the following example:
'use strict'; angular.module('bahmni.common.displaycontrol.custom') .directive('birthCertificate', ['observationsService', 'appService', 'spinner', function (observationsService, appService, spinner) { var link = function ($scope) { var conceptNames = ["HEIGHT"]; $scope.contentUrl = appService.configBaseUrl() + "/customDisplayControl/views/birthCertificate.html"; spinner.forPromise(observationsService.fetch($scope.patient.uuid, conceptNames, "latest", undefined, $scope.visitUuid, undefined).then(function (response) { $scope.observations = response.data; })); }; return { restrict: 'E', template: '<ng-include src="contentUrl"/>', link: link } }])
In the above example, we are configuring the concept names we want to fetch in the variable conceptNames.
You can create your own template in the directive "openmrs/apps/customDisplayControl/views/"
We are creating a birthCertificate.html in the following example:
<div> {{config.title}} <section class="dashboard-section"> <ul class="form-field"> <li ng-repeat="obsGroup in observations"> <span class="obs-date"> {{obsGroup.conceptNameToDisplay }} </span> <span class="obs-date"> {{obsGroup.value}} </span> </li> </ul> </section> </div>
Note:
1. Make sure you don't create a different file for new directives (all custom directives should be in the same file.)
2. Don't forget to change the contentUrl to the html file you are referring to.
Navigation Links Control
To configure the navigation links control on a Dashboard Page, as an example, add the configuration below in the "dashboard.json" file that is under the Clinical App.
Sample Config
"navigationLinksControl": {
"title": "Navigation Links Control",
"name": "navigationLinksControl",
"links": [
{
"title": "Home Dashboard",
"url": "../home/#/dashboard"
},
{
"title": "Patient Visit Page",
"url": "../clinical/#/patient/{{patientUuid}}/dashboard/visit/{{visitUuid}}"
},
{
"title": "Patient ADT Page",
"url": "../adt/#/patient/{{patientUuid}}/visit/{{visitUuid}}/"
}
]
}
Key | Info |
---|---|
title | Title of the section that will be displayed on a Clinical Dashboard, ADT Dashboard or Visit page |
name | Name of the display control |
links | List of links that the user would like to navigate to. Each link has a title and a url. |
title: Text to display in the link | |
url: Url to navigate to |
Obs To Obs Flow Sheet
To configure the Obs to Obs Flow Sheet on a Dashboard Page, as an example, add the configuration below in the "dashboard.json" file that is under the Clinical App.
"Bacteriology Concept Set": { "displayType": "Full-Page", "translationKey": "DASHBOARD_TITLE_BACTERIOLOGY_RESULTS_KEY", "name": "obsToObsFlowSheet", "dashboardParams": { "numberOfVisits": 1, "initialCount": 3, "latestCount": 4, "pivotOn": "column", "templateName": "BACTERIOLOGY CONCEPT SET", "groupByConcept": "Specimen Collection Date", "name": "DstExtension", "conceptNames": [ "Specimen Id" ], "isEditable": true }, "allDetailsParams": { "templateName": "BACTERIOLOGY CONCEPT SET", "groupByConcept": "Specimen Collection Date" } }
Key | Info | Required |
---|---|---|
name | obsToObsFlowSheet (If you configure the name with obsToObsFlowSheet, it will show the obs in tabular view) | Yes |
numberOfVisits | Which is used to see specific number of visits data. If you don't provide, it will show data from all visits. | No |
initialCount | Initial set of observations to be displayed within number of visits | No |
latestCount | Latest set of observations to be displayed within number of visits | No |
templateName | Name of the template which has to be shown in flowsheet | Yes |
groupByConcept | The member of template which is used for grouping | Yes |
name | The name which specifies the file name(groovy extension), so that you can configure extensions for individual obsToObsFlowSheet (DST, ECG READINGS, CHEST X-RAY etc) to support month calculation. | No |
conceptNames | The concept names which you want to see in that table. By default it will show all leaf member in that template. | No |
pivotOn | The orientation of the table. By default it will display row oriented table. | No |
isEditable | The configuration that enables you to edit the each line entry of the flow sheet | No |
Month Extension
Sample Groovy Code: DstExtension.groovy, you can find it at
https://github.com/Bhamni/endtb-config/commit/ca0380f88aad728b9aeae87894ca82abafba5333
This file should copied into config under /openmrs/treatmentRegimenExtension/ package.
ArrayList<BahmniObservation> obs = pivotRow.getColumns().get("Specimen Collection Date");
In the code at line "Specimen Collection Date" is groupByConcept for the Flowsheet.
Note: Make sure that the extension file is copied to "/home/Username/.OpenMRS/bahmni_config/openmrs/treatmentRegimenExtension/" directory.
Showing Highest Observation Value : In order to display only the highest observation value for any coded question concept instead of comma separated values, refer the link https://github.com/Bhamni/endtb-config/commit/700823bed1b36cf54e1a52780c56a0f43260a317 where you have to specify the descending order of values and pass it to the comparator. Refer the below example :
List<String> cultureResultObsValueInDescendingOrder = Arrays.asList("Positive for M. tuberculosis", "Negative for M. tuberculosis", "Contaminated", "Only positive for other mycobacterium", "Other") ArrayList<BahmniObservation> cultureResultObs = pivotRow.getColumns().get("Bacteriology, Culture results"); if(cultureResultObs != null && cultureResultObs.size() > 1) { Collections.sort(cultureResultObs, new obsValueComparator(cultureResultObsValueInDescendingOrder)); pivotRow.getColumns().remove("Bacteriology, Culture results"); pivotRow.addColumn("Bacteriology, Culture results", cultureResultObs.get(0)); }
In above example "cultureResultObsValueInDescendingOrder" holds the fully specified names of coded answers in the descending order. "Bacteriology, Culture results" is the
variable | description |
---|---|
cultureResultObsValueInDescendingOrder | Variable that holds the fully specified names of coded answers in the descending order |
Bacteriology, Culture results | Question concept fully specified name |
Chronic Treatment Chart
To configure the Chronic Treatment Chart on a Dashboard Page, add the configuration below in the "dashboard.json" file that is under the Clinical App.
"Chronic Treatment Chart": { "displayType": "Full-Page", "title": "Chronic Treatment Chart", "name": "chronicTreatmentChart", "dashboardParams": { "drugs": [] }, "allDetailsParams": { "drugs": [] } }
Key | Value | Required |
---|---|---|
name | chronicTreatmentChart (If you configure the name with chronicTreatmentChart, it will show the chronicTreatmentChart display control) | true |
Drugs | drugs concept name which you want to show. (If you don't specify drugs it shows all the drugs which patient is undergoing) | optional |
Month Extension
If you want month column to be shown in chronicTreatmentChart, then add the following groovy extension.
Sample Groovy Code: TreatmentRegimenExtension.groovy, you can find it at
https://github.com/Bhamni/endtb-config/commit/ca0380f88aad728b9aeae87894ca82abafba5333
This file should copied into config under /openmrs/treatmentRegimenExtension/ package.
Note: Make sure that the extension file is copied to "/home/Username/.OpenMRS/bahmni_config/openmrs/treatmentRegimenExtension/" directory.
Drug Order Details Control
Add the below config under drugOrder --> sections in app.json to see it on treatment page or else in dashboard.json --> sections to see it on dashboard.
Sample config
"treatmentsDetails": {
"title":"Treatments Details",
"translationKey" : "DASHBOARD_TITLE_TREATMENT_DETAIL",
"name": "drugOrderDetails",
"displayOrder": 3,
"dashboardParams": {
"showOnlyActive":true,
"drugConceptSet": "All TB Drugs"
}
}
Key | Info |
---|---|
title | Indicates the title that will be displayed on the dashboard for the section |
name | the name/id for the control that needs to be picked from the code |
drugConceptSet | Drug orders will be filtered upon the concepts specified as part of this concept set. If not specified, it will display all drug orders. |
dashboardParams | indicates the configuration for the dashboard |
showOnlyActive | Set this to "true" to display only active drug orders. If "false" or not configured anything will show all the drugs |