...
The reference application provides a clinician-facing dashboard that is highly configurable–it has two columns, and an implementer, via json can configure a variety of different widgets to appear within these two columns. However, previously only a single clinicial-dashboard was available. Context-specific dashboards allow implementer to define multiple dashboard configuration based on context. The only concrete implementation at the moment are program-specific dashboards, but the functionality is meant to support a variety of different configurations in the future.
How they work
The standard clinical dashboard is configured via several extension points, including:
- patientDashboard.firstColumnFragments
- patientDashboard.secondColumnFragments
- patientDashboard.overallActions
- patientDashboard.visitActions
- patientDashboard.otherActions
- patientDashboard.includeFragments
This functionality has bene extended so that the clinical dashboard page controller takes in an optional parameter dashboard the controller will look for a different set of extension points, with the "patientDashboard" component of the extension point name replaced with the parameter passed in to "dashboard". For example, if the page request includes "dashboard=myFirstDashboard" then coreapps module will load any extensions it finds for the following extension points:
- myFirstDashboard.firstColumnFragments
- myFirstDashboard.secondColumnFragments
- myFirstDashboard.overallActions
- myFirstDashboard.visitActions
- myFirstDashboard.otherActions
- myFirstDashboard.includeFragment
Additionally, if message property is defined in the format myFirstDashboard.custom.title, this title will be rendered at the top of the dashboard (below the patient header but above the two dashboard columns)
Program-Specific Dashboards