Service Queues Improvements

O3 has a “Service Queues“ app that is built to help manage outpatient clinics, by tracking the patients who are waiting and giving clinic users a detailed display of who is waiting, how long they’ve been waiting for and what they have been waiting for. While this app basically works, it has been missing a lot of TLC, so the goal of this project is to give the service queues app the TLC it needs.

Specifically, screens like this don’t match our normal design conventions and need to be updated to reflect how these same elements are displayed in other places. Likely this will involve putting together some “standard“ widgets, e.g., for displaying a “numeric obs“ consistently across apps.

Open

Open

Moreover there are numerous buttons that don’t do anything. These should either be fleshed-out into functional pieces or simply removed:

In addition to these more cosmetic changes, the Service Queues app relies on sending requests to the backend with some rather unwieldy custom representations like this one. While the custom representation functionality is great for a lot of things, for cases like this where we’re using them to grab large graphs of objects and individual properties from those objects, it’s usually going to be better to build out a specific REST endpoint to ensure that the data we load is the data we need. We did something fairly similar recently for another backend API that required very similar data to what we’re loading here. Ideally, we should build a custom endpoint that returns only the data we’re actually going to use.

This can either be done as one medium, full-stack project or two small projects, one focused on the frontend parts and one on the backend parts.