Evaluating Self-Hosted Reporting for an NHS Pharmacy Team
Give a pharmacy colleague a report they already know and ask them to find and explain the figures on their own. Ask IT to show how it would restore the report after an outage. Both checks matter before the team relies on it.
- AGREE THE OUTCOME What Would Make the Evaluation Worthwhile?
- PLACE THE SERVICE Give IT a Deployment They Can Assess
- FOLLOW THE READER Try the View from a Colleague’s Account
- SHARE THE RESPONSIBILITY What Happens When the Report Author Is Away?
- MAKE THE DECISION Leave with Evidence Both Teams Can Use
What Would Make the Evaluation Worthwhile?
At a demonstration, a pharmacy colleague finds the weekly dispensing summary and compares two sites. Then they stop. They can’t tell which week they’re looking at. Someone from IT asks a second question: who would get the report working again if the application stopped?
Those are two things the evaluation needs to answer. Start with a report whose figures the pharmacy team can already check. Ask a reader to open it with their own account, find the right week and compare the sites. Ask IT and the source owner to explain how the report gets its data, who can see it and who would support it.
In this example, the team agrees what a successful trial would look like. The pharmacy colleague should find the approved weekly figures without asking the author for another copy. IT should be able to explain where the application runs and show how the team would recover it.
Give the trial an owner
Someone needs to bring the findings together and arrange the final decision. That person can coordinate the evaluation without owning every technical or pharmacy question.
Give IT a Deployment They Can Assess
Draw the route the weekly summary will take. Start with the approved pharmacy reporting source, add the server running IntelliFront BI and end with the colleague’s browser. IntelliFront BI runs on infrastructure the organisation controls. Ask IT to show how each part of the route would work in that environment.
Then name the accounts. The source owner can say which account is allowed to read the weekly data and which records it can read. IT can show how the pharmacy colleague signs in. If the plan includes remote access or an external service, put that on the drawing too.
With the drawing in front of them, IT can check the server, database and network requirements for the version it plans to use. Record any connection or account the team still needs to test.
Include what leaves the server
If the proposed workflow includes exports, emails or external integrations, discuss their destinations too. The hosting location describes only part of the information journey.
Try the View from a Colleague’s Account
Now return to the pharmacy colleague who wants the weekly summary. A demonstration from an administrator’s screen only shows part of that experience. A representative reader account reveals whether the colleague can sign in, find the assigned reporting and recognise the detail available to them.
Let the colleague describe what they are trying to learn from the summary. Can they reach the answer through the proposed view? Where do they pause or ask the author for help? Those moments tell the team what needs clearer wording, a better arrangement or a different reporting approach.
The source owner and reporting team can also explain how the records available to this account match the agreed scope. Opening the right dashboard and seeing the right set of records are separate parts of the same evaluation.
Keep a brief record of the outcome in the colleague’s own terms. “I could compare the sites, but I could not tell which period was selected” gives the team a concrete improvement to revisit. It is more useful than recording that the demonstration was well received.
Use a suitable trial dataset
Approved sample or de-identified data can help explore the reader experience. Record which conclusions still depend on testing the intended source and access arrangements.
What Happens When the Report Author Is Away?
Imagine the next weekly meeting arrives while the report author is on leave. A colleague notices an unexpected total. Who can explain the measure, who can investigate the source, and who can check that the reporting service is running?
Those questions may lead to different people. Giving each responsibility a home helps the team support the service without relying on the person who built the first view.
| Question | Responsibility to agree |
|---|---|
| Does this measure mean what pharmacy expects? | Pharmacy reporting owner |
| Have the expected source records arrived? | Source or data-service owner |
| Can colleagues reach the reporting application? | Application and infrastructure support |
| Does the issue need product help? | Named contact for ChristianSteven support |
The local roles may be combined or named differently. What matters is that the next person knows where to begin and what evidence to pass on.
IntelliFront BI includes a Client Service Status area for administrators, with service status and error logs. It can contribute to an investigation alongside checks on the source and local infrastructure. The evaluation should establish who can use those tools and when an issue needs escalation.
Updates, backups and recovery also need an owner. Agree what would be protected, how a recovery would be demonstrated and who would authorise a change. A successful installation is the beginning of those arrangements.
Support needs a useful handover
A concise issue description should include what the reader expected, what happened and when. Share logs or examples through the organisation’s approved support process, with sensitive content handled appropriately.
Leave with Evidence Both Teams Can Use
The analyst adds the selected week beside the figures. At the second demonstration, the pharmacy colleague compares the same two sites and tells the team which week the view covers. The source owner confirms that the colleague’s account shows the records they should be able to see.
The reader check passed. The recovery test is still open. Before making the dashboard part of the weekly meeting, the team asks IT to restore the service in a trial environment and show that the same approved report still opens. The decision note records both the reader’s successful second attempt and the test still due.
For your own evaluation, use a report your colleagues can check. When something goes wrong during the trial, record what happened, who will look at it and what result you need before you go further.
If you’re planning a trial with pharmacy and IT, use the self-hosted NHS pharmacy reporting evaluation to agree what each team needs to see.
Contributors:
Christian Ofori-Boateng
CEO, ChristianSteven Software