From JAC and CareFlow Data to a Pharmacy Reporting Workspace
Start with a pharmacy report your team already trusts. Before you build a new dashboard with JAC or CareFlow data, agree how you’ll get the records, what each row counts and who will look after the report.
- IDENTIFY THE ENVIRONMENT Which JAC or CareFlow System Are You Reporting From?
- ESTABLISH THE SOURCE Agree What the Reporting Team Can Use
- DEFINE THE HANDOVER Describe the Data Before Building the Dashboard
- CONNECT THE REPORTING Where IntelliFront BI Fits
- PLAN FOR CHANGE Give the Reporting a Named Owner
Which JAC or CareFlow System Are You Reporting From?
A pharmacy analyst has a weekly dispensing report that everyone knows. The pharmacy team wants an easier way to compare wards, so the analyst takes that report to the people who run the medicines system. First they need to agree which records the new view can use and how they’ll check the totals.
If colleagues call the system JAC, keep that name handy when looking up support records. System C acquired WellSky International, formerly JAC. Ask which product and version are installed. A dispensing report from CareFlow Pharmacy and a report from an electronic prescribing and medicines administration system can cover different work.
Bring the weekly report along. The pharmacy specialist can show what a completed item means in that report, while the system owner checks which supported route can supply those records.
A product name is a starting point
“We use JAC” helps orient the conversation.
The installed modules and available reporting establish what can be included in the project.
Agree What the Reporting Team Can Use
The analyst asks the system owner how to get the same information each week. The existing report might be enough. The supplier or system owner can also tell the team whether an approved export or a supported database connection is available for that installation.
If the team chooses an export, agree when and where the file will arrive. If they use a database connection, agree which account can read which records. Write down whom to call if a file is late or a column changes. That short note saves the next analyst from having to start the conversation again.
The pharmacy team at University Hospitals Sussex described using existing reports and SQL as starting points, then using SQL and Excel data for its seven-day project. The mix depended on the information it needed. Ask your own system owner what’s available for the report you’ve brought.
One useful supplier question
“Which supported reporting route supplies the information in this report for our installed version?”
A familiar report makes that question easier to answer precisely.
Describe the Data Before Building the Dashboard
Next, the pharmacist explains what the weekly report counts. In our example, the agreed unit is one completed dispensing item, allocated to the ward recorded at completion. The analyst uses that definition before choosing the grouping or totals.
| Agreement | What it resolves |
|---|---|
| Meaning of one record | Whether a row represents an item, an event or another level of detail |
| Activity date and ward | Which week and ward receive the recorded activity |
| Inclusions and exclusions | How cancellations, corrections and incomplete records are treated |
| Source availability | When the supplied information can be used and who supports it |
For a small fictional sample, the analyst receives six rows. Four describe completed dispensing items, one describes a cancelled item and one repeats an already delivered completed-item row. The source owner confirms the repeat is a delivery duplicate, not a separate event. Applying the agreed definition leaves four completed items, matching the source report.
Count all six rows and the result is too high. Set aside the cancellation and the confirmed duplicate, then check the ward and completion date for each of the four items against the source report. If the source report still differs, compare periods, events and exclusions before deciding which calculation to change.
Repeated item references deserve the same care. They could be duplicate deliveries, separate events or legitimate detail. Their meaning determines whether the analyst keeps, combines or excludes them.
This agreement gives the dashboard author an understandable dataset: the selected records and fields the reporting will use. It also leaves a clear account of how that dataset relates to the source.
Keep the exceptions in view
A record without a ward needs an agreed treatment, such as a visible “Ward not recorded” category.
Silently excluding it can make the new report harder to reconcile with the source.
Where IntelliFront BI Fits
If the existing weekly report answers the question, the team can continue using it. If colleagues also need interactive ward comparisons and a shared reporting home, the next decision is where to build those views. IntelliFront BI is self-hosted business intelligence software from ChristianSteven Software, running on infrastructure your organisation controls.
In this project, a connection would follow the approved reporting route. A dataset would supply the records and prepared measures needed for the dispensing view. The dashboard would present that information to its intended readers.
These are separate parts of the work. Configuring access to a source does not, by itself, define a completed dispensing item or decide which ward receives the activity. The pharmacy agreement guides the data preparation and reporting author.
For the fictional sample, the first dashboard should still show four completed items. The analyst can then compare wards and check that the ward totals add back to four. Interactive presentation becomes useful once the prepared data and its meaning agree.
Leave enough detail for the next analyst
Record where the dashboard gets its numbers and keep the four-item check beside it. If next week’s total looks wrong, the analyst can check whether the issue started in the file or in the calculation.
Give the Reporting a Named Owner
At the end of the week, the analyst can explain why six rows became four completed items. One row was cancelled and another repeated an item already counted. The new view agrees with the report the pharmacy team brought to the first meeting. Keep that small example so the next person can run the same check.
Agree whom to call if the numbers change. The pharmacy owner explains the dispensing rules, the reporting owner checks the calculation, and the system team checks what arrived. One colleague may cover more than one of those jobs.
If an upgrade changes a status or a field, rerun the four-item example before using the revised view more widely. A familiar result gives the team somewhere to start if the figures come out differently.
If pharmacy and IT are ready to build a shared ward view, see how JAC and CareFlow pharmacy dashboards can use the reporting data your teams have agreed to make available.
Contributors:
Christian Ofori-Boateng
CEO, ChristianSteven Software