NHS PHARMACY · LEARN

How Current Is the Information on Your Pharmacy Dashboard?

A dashboard can open at 09:00 and still show pharmacy records only through 08:00. Look for the latest time the data covers before you rely on it for a ward review.

  
READ THE TIME

How Recent Are the Source Records?

It’s 09:00. A pharmacist opens the ward dashboard and looks for a change entered at 08:40. The analyst checks the file used to update the dashboard. It includes changes through 08:00, so the pharmacist opens the prescribing system to see the newer entry.

For this example, the pharmacy team has agreed that it can use the dashboard to scan the ward’s workload while the data is no more than an hour old. At 09:00 it is right at that limit. The pharmacist can use it to see the overall workload and check the newer entry in the prescribing system.

That’s the distinction worth keeping in mind. Ask how old the data can be for the job you’re doing. If you’re looking for a particular change, check whether the latest update was able to pick it up.

Say which records the time applies to

If prescriptions and stock figures arrive separately, give each its own label. The latest time on one chart may tell you little about the data in the next one.

  
FOLLOW ONE UPDATE

Which time tells you how current the data is?

When the analyst looks into the missing entry, four times come up. They’re all from the same morning. Each tells the analyst something different about where the update got to.

One update, four different times
Time Event
08:00 Latest changes included in the file
08:12 File finished loading
08:15 Dashboard read the loaded data
09:00 Pharmacist opened the dashboard

At 09:00, the file had finished loading 48 minutes earlier and the dashboard had read it 45 minutes earlier. The file covered changes only through 08:00, an hour before the pharmacist opened the dashboard. If a label only said “Updated 08:15”, the pharmacist could easily think it included the change made at 08:40.

Refreshing the page can make the dashboard read the same stored copy again. The missing entry will appear only when a later file includes it and the dashboard reads that newer data.

Check the clocks once

When source, server and browser times differ, record the time zone and date for each stage before comparing them. Around clock changes, an explicit UTC offset can resolve an ambiguous local time.

  
MAKE DELAYS VISIBLE

When the Next Update Is Late

The next file should include changes through 09:00. Its 09:10 load fails, leaving the dashboard on the 08:00 data. At 09:20, the dashboard still shows records only through 08:00, 80 minutes earlier. That’s past the team’s one-hour limit, so the pharmacist uses the prescribing system for the review.

A clear message would give the pharmacist both pieces of news: “Records through 08:00 today. Next update delayed.” If the dashboard cannot show any figures, say they’re unavailable. A blank screen or a zero could otherwise look like there are no items to review.

Sometimes the analyst can see when the dashboard last asked for data but can’t tell which records it received. In that case, say what you know: “Dashboard checked for data at 08:15. Latest records included: unknown.” Give readers a contact if they need to check when the dashboard will be usable again.

An unchanged count can be current

After a successful update, additions and removals may balance out. Check a known changed record and the update evidence rather than judging freshness from the headline count alone.

  
MATCH THE PURPOSE

Choose an Update Arrangement That Fits

The pharmacist scanning the morning queue needs to know how far the dashboard is behind. A colleague reviewing yesterday’s totals needs the whole day’s activity, including any corrections the team has agreed to count. A faster update won’t help if those records haven’t arrived yet.

Match the update to the task
Task What the reader needs
Daily activity audit A complete named reporting day, with the extraction date and an explanation of later corrections.
Prescriptions awaiting review A clear label showing the latest records included, and an agreed point at which to use the prescribing system instead.

Start with the reports you already use. A clearer time label may be enough if the reporting team can already tell which changes each update includes.

If you need a shared dashboard, IntelliFront BI runs on infrastructure your organisation controls. It can update its stored copy of the reporting data on a schedule. For the ward view in this example, the analyst would schedule that update around the arrival of the pharmacy file and check when the dashboard can show what’s in it.

Label the day as well as the time

If yesterday’s data can still appear this morning, a label like “Records through 08:00” can be misleading. Include the date and tell readers which time zone is used when it matters.

  
GIVE READERS A CLEAR ANSWER

Make Freshness Easy to Explain

At 09:32, the analyst loads the delayed file. It includes changes through 09:00, including the entry made at 08:40. The dashboard reads the new file at 09:35. The pharmacist finds the entry and checks it against the prescribing system.

At 09:35, the dashboard says “Records through 09:00 today”. The 35-minute gap is within the team’s one-hour limit. The pharmacist can go back to using the dashboard for the ward review.

Try this with one of your own dashboards. Pick a change you can recognise, note when it was entered and see when it first appears. Then ask a colleague to read the time label. If they can tell whether the change should be there, the label is doing its job.

If you’re choosing a reporting setup, use the self-hosted NHS pharmacy reporting evaluation to put data freshness on the list of things pharmacy and IT test together.

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software