Industries/ Healthcare/ Connected patient reporting
Clinic reporting from one controlled source, not exported spreadsheets
Bookings, attendance, billing and insurer claims flow into one reporting layer, with one identity for each patient and names kept out of the analysis. Managers see activity, capacity and income without anyone exporting a spreadsheet full of patient details.

- Used by
- Practice managers, owners, site leads and the finance team
- Takes the place of
- Monthly exports matched by name on someone's laptop
- Connects to
- Your practice system, billing, accounts and booking tools
- Built with
- Our connecting systems service
Where it hurts today
A normal week, before it exists
On the first working day of the month, the practice manager exports appointments from the practice system, invoices from billing and remittances from three insurers. Then the matching starts. J. Smith in one file, John Smith in another, a date of birth typed two different ways. By lunchtime there is a spreadsheet with hundreds of patient names in it, sitting in a downloads folder and attached to an email to the directors.
The figures never quite agree. The director's count of last month's new patients differs from the practice manager's, because one counted bookings and the other counted attendances. Nobody can say which site has the most unfilled sessions, or how many new patients came from consultant referrals rather than the website, without another afternoon of exporting, matching by hand and hoping nothing was missed.
Insurer debt is the quiet one. Claims sit unpaid for weeks because nobody can see them grouped by insurer and age, only invoice by invoice. And every month the most sensitive data the practice holds is copied onto a laptop, emailed and forgotten, which is exactly what the data protection policy says should never happen to patient information, and what nobody has had time to stop.
What it does
Connected patient reporting, feature by feature
A reporting layer built for the questions managers actually ask, with patient privacy designed in from the start rather than added later.
- 01
One patient identity across systems
The same patient in the practice system, billing and the booking tool is matched under rules you agree, using record numbers, dates of birth and contact details. Clear matches link automatically, borderline ones go to a named person, and reports use a single reference instead of a name.
- 02
Pseudonymised data for analysis
The reporting layer holds what the reports need and little else: a pseudonymous reference, an age band, a postcode district, the appointment type and what happened to the booking. Names, addresses and clinical notes stay in the source systems, where access is already controlled.
- 03
Clinic capacity and utilisation by site
Booked hours against available hours, unfilled sessions, late cancellations and patients who did not attend, by site, appointment type, day and clinician. New and returning patients are counted the same way every month, using definitions agreed with you and written down.
- 04
Income, insurer claims and aged debt
Invoiced, paid and outstanding, split between self-pay and insured, with insurer claims grouped by insurer and by age. The totals are reconciled against your accounting software each month, and any difference is explained rather than quietly absorbed into a rounding line.
- 05
Referral source reporting
Referral sources as recorded at booking, such as a GP, a consultant, an insurer, the website or a returning patient's recommendation, followed through to a first appointment. It shows which routes bring patients who actually attend, not just enquiries.
- 06
Data quality checks on every load
Every overnight load is checked for freshness, completeness and totals against the source. If a feed fails or a figure looks wrong, the report is marked provisional and someone is told before the directors open it. Every figure can be traced back to the record it came from.
A day with it
How the day runs instead
A month in a three-site group, with every report drawing on one controlled source.
- Monday 8.10amPractice manager
The morning data check shows every load completed except billing, which arrived late. The income report is marked provisional, with the reason shown. By ten the feed has caught up, the mark disappears, and nobody has had to explain a wrong number in a meeting.
- TuesdaySite lead
She opens the capacity view for her own site, the only one she can see. Saturday podiatry sessions have been unfilled three weeks in a row, so she proposes moving one to Thursday evening, where the waiting list is longest.
- WednesdayFinance manager
He opens the insurer claims older than sixty days, grouped by insurer. One insurer holds most of them. He needs the patient behind one claim to check a reference, so he looks it up through the controlled lookup, which records his name and his reason.
- Month endClinic owner
The board pack draws on the same source as everyone else's reports, so activity, new patients by referral source and income agree between the owner, finance and the practice manager. The discussion is about what to do next, not whose spreadsheet is right.
- Each quarterData protection officer
She reviews the log of identity lookups and report access, checks that leavers no longer appear, and confirms that no new field has been added to the reporting layer without the agreement written down at the start.
What it connects to
Works with what you already run
Each feed pulls only what the reports need, on a schedule, and says so loudly when it fails.
Practice management system
Appointments, appointment types, attendance, cancellations and referral sources, pulled overnight with only the changes since the last load. Patient identity is replaced by a pseudonymous reference on the way in, and clinical notes are never part of the feed.
Billing and insurer claims
Invoices, payments, claim submissions and remittances, matched to the same patient reference, so outstanding claims can be grouped by insurer and age without names appearing in the report.
Accounting software
Monthly totals reconciled against your accounting software, where it offers an API or a reliable export, so income in the reports agrees with income in the accounts your accountant signs off.
Online booking and enquiry tools
Enquiries and online bookings, so referral sources and the route from first contact to first appointment can be followed. Marketing consent is carried across and respected, never inferred.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- Overnight feeds from the practice system and the billing system
- One patient reference across both, with borderline matches checked by a person
- An activity and capacity report for each site
- An aged list of unpaid insurer claims, grouped by insurer
- Freshness and completeness checks, with an alert when a load fails
Once it is in use
- Referral source reporting from first enquiry through to first appointment
- Clinician-level capacity views, once their use is agreed with clinical leads
- Monthly reconciliation of income against your accounting software
- Site lead reports limited to each lead's own site
Buyer's guide
Before you commission one
Four decisions worth making before you commission connected reporting for a practice or care group.
- 01
Built-in reports, a BI tool or a data layer
Start with the reports in your practice system: for one site on one system they may answer most questions. A business intelligence tool connected to that one system is the next step. A custom data layer earns its place when the questions cross systems, such as income per appointment type including insurer payments, or when sites run different software and nobody can compare them.
- 02
What to gather first
Write down the five questions owners and managers ask most and cannot answer quickly. List every system holding patient, booking or billing data, who supplies it and whether it offers an API or a scheduled export. Then agree definitions: what counts as a new patient, an attendance, a late cancellation. Those definitions matter more than the software.
- 03
Who should own it
A senior manager, often the practice manager or finance lead, should own the definitions and decide what each report means. Your data protection lead owns the list of fields allowed into the reporting layer and the lookup permissions. Someone technical, inside or outside the business, owns the feeds and responds to the alerts when one fails.
- 04
How you will know it is working
The clearest sign is that nobody exports patient data to a spreadsheet any more, and that the owner, finance and the practice manager quote the same figure in the same meeting. Watch how often loads are marked provisional, how long a new question takes to answer, and whether site leads use their own views without asking for help.
Terms worth knowing
The words you will meet
- Pseudonymisation
- Replacing names and other direct identifiers with a reference, while the key that links the reference back to a person is kept separately and protected. Under UK and EU GDPR, pseudonymised data can still be linked to someone with that extra information, so it remains personal data. It reduces risk without removing obligations.
- HIPAA de-identification
- In the US, the HIPAA Privacy Rule sets two routes to de-identify health information: removing 18 listed categories of identifiers, known as safe harbor, or a documented expert determination that the risk of re-identification is very small. Which route you use shapes how widely a report can be shared.
- Master patient index
- A single list that links each patient's records across systems, so the same person in the practice system, billing and the booking tool shares one reference. It is what makes cross-system reporting possible without matching names by hand, and its matching rules decide how often two different people are wrongly merged.
Handled with care
The details that matter here
Reporting is where patient data is most likely to spread, so most of the design work goes into keeping it contained.
Clinical detail stays out
The reporting layer is for activity, capacity and income. We agree a written list of fields with your data protection lead before any feed is built, keep diagnoses and clinical notes out of it entirely, and treat any later request for a new field as a decision for them.
Re-identification is controlled
Sometimes a manager needs to know which patient sits behind a figure. We build that as a separate lookup, available only to named roles, which asks for a reason and records who looked up whom and when. The reports themselves never show names.
Small numbers handled carefully
A report showing one patient in an age band at a small site can identify that person as surely as a name. We agree a minimum group size with your data protection lead and hide or combine counts below it in any report shared beyond the people who need the detail.
Clinician figures used fairly
Capacity and attendance by clinician can be useful, and can be misread. We agree with your clinical leads which clinician-level views exist, who sees them and what context sits beside each figure, before they are built rather than after someone is upset by one.
Guides
Worth reading first
Questions
What buyers ask first
Do we have to stop using our practice software's own reports?
No. Keep using them for what they do well inside that one system. This layer is for questions that cross systems, such as income per appointment type including insurer payments, or new patients by referral source who actually attended. Your practice system, billing and booking tools keep working exactly as they do now, and the feeds only read from them.
Can we see which patient is behind a number in a report?
Yes, for the people who need to, through a controlled lookup. Named roles, such as finance chasing a specific claim, can see the patient behind a reference after giving a reason, and every lookup is logged. Everyone else sees counts and references only. Your data protection lead decides who holds that permission and reviews the log.
What if our clinic's data is messy?
Probably less of a problem than you fear, but we find out before promising anything. We start by profiling what is in your systems: duplicate patients, blank referral sources, appointment types renamed halfway through a year. You get a plain report of what we find, including where the sensible answer is to report only from a certain date forward rather than pretend older data is comparable.
Is pseudonymised patient data still personal data?
Under UK and EU GDPR, yes. Pseudonymised data can be linked back to a person using the key kept separately, so it is still personal data, and health data is special category data with extra conditions on its use. It is still worth doing, because it limits who can identify anyone. In the US, HIPAA has its own de-identification tests, and your compliance lead decides which apply to you.
Where does clinic reporting data live?
In a database and reporting tool in your own cloud account, in the region your obligations require, with access tied to your staff sign-in. In the UAE, for example, Federal Law No. 2 of 2019 on technology in health care is part of that picture. The code that builds the feeds sits in your repository with a runbook, and we use synthetic data during the build.
Tell us the question your spreadsheets cannot answer
Describe the report someone rebuilds by hand every month and the systems it comes from. We reply within 48 hours and will tell you which feeds would answer it, and what shape your data is likely to be in.
More for healthcare
What else we build for healthcare
Patient portals
Booking and rescheduling against your real diary, forms completed before the visit, invoices paid online, and results or letters released only when a clinician chooses, with identity verified properly and every access recorded.
Booking and reminder apps
An app or mobile-friendly booking flow with reminders, one-tap rescheduling, waiting lists that offer a cancelled slot to the next patient, and deposits taken up front, so fewer appointments go to waste.
Clinic operations tools
Rotas, training and registration expiries, equipment checks, room bookings and incident logs in one place, with automatic reminders and per-site permissions, so inspection evidence builds up as the work happens rather than in a rush beforehand.
Front desk assistants
An assistant on your website and messaging channels that handles booking, opening hours, prices and preparation questions using your real calendar, with firm rules: no advice, no diagnosis, and a quick handover to a person.
Referral and intake reading
Referral letters, insurer forms and scanned documents read on arrival, key details extracted and matched to the right patient, and anything uncertain queued for a person to check, rather than typed in by hand at the end of the day.


