Six tabs and a sticky note
A patient phones to move an appointment and asks about an invoice while they are on. The receptionist has the diary open in one window, the patient record in another, the accounts package in a third, the SMS tool in a fourth, the shared inbox in a fifth, and a spreadsheet of insurance details in a sixth. They find the invoice, realise the address on it is out of date, update it in the accounts package, and make a note to update the patient record later.
Later does not happen. Next month a letter goes to the old address. The patient is annoyed. Somebody fixes it in one system and not the others.
How a clinic ends up with so many systems
Nobody sets out to build a patchwork. The clinic starts with a practice management system. Then it adds an online booking tool because the built-in one was weak, an SMS service for reminders, an accounts package the accountant prefers, a forms tool for intake, a survey tool, a separate system for one service line. Each decision made sense at the time.
The trouble is that each tool keeps its own copy of the patient. Name, date of birth, phone number, address, insurer. When one copy changes, the others do not. Staff become the integration layer, copying and checking by hand, and every copy is a chance for a mismatch.
Replacing everything with one system is sometimes the answer, but often it is not. Specialist tools are usually there because they do something the main system cannot, and a full migration is a large, risky project.
What the juggling costs
| Cost | What it looks like |
|---|---|
| Duplicate entry | The same details typed into several systems |
| Mismatched records | An address or phone number right in one place and wrong in another |
| Slower calls | Staff clicking between windows while the patient waits |
| Training | New starters need to learn every system and how they relate |
| Mistakes | Messages sent to old numbers, invoices to old addresses, notes in the wrong place |
There is also a cost in attention. Staff who are constantly switching and cross-checking are more tired and more likely to miss things, and the patient on the phone can hear it.
How we connect what you already have
- We map every system in use, what data each holds, and which fields are copied by hand between them. This is usually the most revealing part of the work.
- We agree a source of truth for each piece of data, for example contact details owned by the practice management system and billing details owned by the accounts package.
- We build integrations through each system's API, or through tools such as Make or n8n where a lightweight connection is enough, so a change in the source updates the copies.
- Conflicts, where two systems disagree, go to a short review queue rather than being overwritten silently.
- Where it helps, we build a single patient view for admin staff: upcoming appointments, recent messages, outstanding invoices and contact details on one screen, read from the underlying systems.
- Access to that view follows your roles, so reception sees what reception needs and nothing clinical that they should not.
If the mapping shows that one of your tools duplicates something your main system does well enough, we will say so. Removing a system is often cheaper than connecting it.
What the day feels like after
Contact details change once and follow everywhere. Staff handling a call can see the whole admin picture without switching windows. New starters learn one screen for most tasks, not six. And the mistakes that come from stale copies, the letter to the old address or the text to the old number, stop appearing.
The underlying systems are still there, still doing what they are good at. They just stop relying on people to keep them in step.
Does your clinic have this problem?
- Reception has four or more systems open to handle one call
- The same patient details are typed into more than one system
- Letters or texts go to out-of-date contact details
- Training a new receptionist takes weeks because of the number of tools
- Nobody is sure which system holds the correct version of a record