[Discussion] Reference Application 2.6 Roadmap for April 28, 2017 Release

Hi all,

1. Big features

Alongside adopting bootstrap we would be keen for a general UI re-thinking. And we see this happening on at least two levels:

  1. Dashboards re-thinking At the very least the patient dashboard must undergo some serious changes (and in particular patientdashboard/visits.gsp). In our experience at least this page is not good enough from the user’s perspective and it is a nightmare from the developer’s perspective. But perhaps this leads to re-thinking the CF dashboard as well? Perhaps one larger, better designed dashboard would be more useful as a central place to offer a synoptic view of the patient, including its history of visits & encounters.

  2. Number of clicks One design flaw of the Ref App is that users must perform too many clicks. There are many examples of this, but here is one: when finding one patient (so when the result of finding a patient is a unique occurrence) the patient CF dashboard should open right away on that patient. From a usability standpoint, we would be better off staying mostly on one page (the idealised dashboard mentioned in point 1 above) and use widgets to rapidly visualise further data, rather than always accessing other pages to visualise further data. In fact what I am saying here is that each app, or each piece of functionality that is rendered fully through an ad-hoc page, should provide at least one widget that could be inserted into dashboards (or not, depending on the desired configuration). Some modules/apps/functions already do that: Allergy UI, VDUI, Appointment Scheduling UI, … etc, some don’t: Chart Search. Leveraging reusable UI components paves the way to this. One should produce configurable UI widgets, then those widgets could be used with a compact display for dashboards insertions or in a full size display for the ad-hoc page.

It is very possible the above two points are out of reach for end of March, and in that case we would love to keep them in mind for later releases.

2. Small features

We could bring in the Sticky Note feature. We will create ad-hoc RA tickets for this.