LEARN BUSINESS INTELLIGENCE

Designing a Pharmacy Dashboard for Daily Review

A useful pharmacy dashboard shows which patients need review, why they appear and the detail needed to investigate. Build it around the pharmacy team’s review process so the worklist reflects how people actually work.

Here’s how to bring that information into a ward view, keep the counts clear and follow a prescription change through the list.

  
START WITH THE WORK

Choose the Review Question Before the Visuals

Picture a pharmacist opening the ward worklist at the start of a shift. They need to see who is awaiting an initial review and whose prescriptions have changed since a review was recorded. A reporting lead may also want the overall workload, but the person using the list needs a reason to open each record.

We’ll follow a fictional hospital pharmacy team that wants those two types of work in one view. Its readers use the dashboard to find records, then open the prescribing system to investigate and record their review. The pharmacy team determines clinical priority through its agreed process.

For that task, the useful information is the current admission, ward, prescription changes and review history. Medication stock holdings answer a different question about supplies and belong in a separate view.

Keeping the question this focused helps you choose what to show. A column explaining why a patient appears will help the reader act; a chart that adds no useful context can wait.

Ask a reader to walk you through it

“What do you need to see before you open the prescribing record?” is a useful starting question.

The answer will often tell you more about the layout than a list of requested charts.

  
DEFINE THE INFORMATION

Agree What Each Row and Status Means

The worklist depends on how the prescribing system records activity. An Electronic Prescribing and Medicines Administration system, often shortened to EPMA, records prescribing and medicine administration electronically. Its available fields and review processes vary with the system and local configuration.

A pharmacy subject specialist and the reporting owner can map those fields to the worklist. For our example, the key questions are:

  • Current admission: which record identifies this hospital stay, and when does it leave the list?
  • Ward: does the field show the patient’s current location or their location when an event occurred?
  • Review: which event records completion of the intended pharmacy review, and which prescription items does it cover?
  • Later changes: which changes require another review under the team’s process, and how are they recorded?

Keep medicines reconciliation separate from prescription review. Reconciliation compares an accurate list of current medicines with the list in use and resolves discrepancies. To establish that the intended prescription review is complete, use an event that records that review and its scope; a reconciliation status alone is insufficient.

Our summary has one row per patient’s current admission, with prescription items available as supporting detail. This lets the reader find a patient once, then inspect the items behind the review reason.

If review information is missing, show “Review status unavailable.” That gives readers a reason to check the source instead of mistaking a blank for completed work.

Use labels people recognize

Check labels such as “reviewed,” “verified” and “screened” with the pharmacy team. They may refer to different steps.

Use the agreed term consistently in the source mapping, dashboard and help text.

  
WORK THROUGH AN EXAMPLE

Follow a Patient Through the Review Worklist

Consider DEMO-101, an invented admission on Ward A. At 08:00, two prescription items await an initial pharmacy review. In this fictional team’s workflow, both items leave the worklist once their review is recorded.

Another fictional patient, DEMO-102, remains on Ward A with one item awaiting review throughout this example.

At 08:20, that review is completed. At 08:35, one prescription changes in a way that requires another review under the team’s rules. Here’s what the worklist should show as each source update reaches the dashboard.

Fictional DEMO-101 review sequence; times refer to source events
TimeSource eventWorklist resultItems awaiting review
08:00Initial review outstandingIncluded: initial review needed2
08:20Review recorded for both itemsRemoved: no outstanding review work0
08:35One prescription changes after reviewIncluded again: later change needs review1

The reason beside DEMO-101 now explains what brought the patient back. The reader can look at the changed prescription and its review history rather than repeat the search through every item.

At the 08:00 snapshot, the list contains two patients and three outstanding items. Once the 08:20 review is reflected, it contains one patient and one item. After the 08:35 change appears, it contains two patients and two items.

Those are different measures. Calculate patient totals from distinct current-admission references, and item totals from the relevant prescription items. If a patient meets more than one inclusion rule, count them once overall and show the reasons together.

Try a ward transfer

After the 08:35 change appears, move DEMO-101 to Ward B in the test data.

For a view grouped by current ward, expect one patient and one outstanding item on each ward. The overall total should stay at two patients and two items.

  
DESIGN THE READER VIEW

Build a Worklist People Can Investigate

The example suggests a useful starting layout: a patient total, a ward selector and a worklist with the admission reference, review reason and supporting prescription information. Readers can see the size of the worklist, focus on their ward and find the record they need.

Keep the reason for inclusion visible beside each patient. “Initial review needed” and “Later change needs review” lead the reader to different parts of the prescribing record. Text labels also preserve the meaning when color is difficult to distinguish.

The pharmacy team can choose an order that fits its daily work, such as ward followed by an agreed review category. Where locally approved clinical flags help that decision, show them alongside the reason. The number of outstanding items describes workload; it does not establish clinical urgency.

Your prescribing system may already provide a suitable list. If readers can find the right records and it meets their definitions and update needs, those controls may be enough. A separate dashboard becomes useful when you need to bring reporting information together or give several teams a consistent view.

When a shared reporting portal helps

IntelliFront BI is self-hosted business intelligence software from ChristianSteven Software. It provides a browser-based place to build and share dashboards, with the software running on infrastructure your organization controls and reporting data kept within your environment.

For our ward view, its grid visuals can present the worklist. A Combo Box visual can filter other dashboard items, allowing readers to select a ward. The dashboard filter setup guide explains that configuration.

Build the view from a dataset containing the mapped admission, prescription and review fields, with access to the required source data. In this design, readers continue to record their clinical review in the prescribing system.

A filter is a viewing choice

A ward selector helps readers focus the display. It does not establish which patient information they are authorized to access.

Have the administrator configure and test access separately, using representative reader accounts.

  
CHECK IT WITH THE TEAM

Test the Worklist Against the Source

Try the first version on one ward with a pharmacy subject specialist and a representative reader. Compare a few records with the prescribing system, using approved test data for changes and following your organization’s rules for patient information.

Follow DEMO-101’s sequence: outstanding work appears, a recorded review clears it, and a qualifying later change brings it back. Check that the supporting items explain the patient total at each stage. The ward-transfer example adds a check that the work moves without being duplicated.

Include a discharge and a record with unavailable review information in your checks. The discharged patient should leave the current-admission worklist. The record with missing review information should remain identifiable as needing investigation. Changing the ward filter should keep the summary and detail on the same selected population.

The time between a source event and its appearance matters too. Measure that delay against the team’s agreed needs, and label the information age clearly. “Source extract produced at 08:40” describes a different event from “Screen updated at 08:45.” Readers need to know what the timestamp represents and who to contact if updates fall behind.

Let the reader use the list without a running explanation. Where do they hesitate? A clearer label or a different column order may help more than another chart. Keep the field definitions and expected results with the dashboard so its owner can revisit them when the workflow changes.

Start with that one ward and a handful of records you can account for. Once readers can find the work, explain why it appears and follow it back to the source, you have a useful basis for extending the view. If a shared reporting portal is part of that plan, you can explore dashboards for daily pharmacy work using the same example.

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software