Why Your Practice Management System Isn't Enough for Referral Tracking

Your practice management system runs appointments, billing and the clinical record. It almost certainly has a referral field somewhere too. So the question practice managers keep asking is a fair one: if the PMS already stores referrals, why would you run a second system?

The answer is not that the PMS is bad software. It is that a PMS is organised around the appointment. A referral becomes real to it at the moment someone books. Everything that happens before that booking (the letter arriving, the triage decision, the repeated attempts to reach the patient) is the part where referrals go missing, and it is the part the PMS was never designed to hold.

You can see this in how the vendors describe their own products. Zedmed presents its Referrals module as the place to write a referral out to another provider; Bp Premier describes inbound documents landing in an inbox to be actioned. Both descriptions are accurate and both are useful. Writing a letter out and actioning an inbox are their own jobs, both different from holding a queue open for weeks while a patient decides whether to call back.

What a queue needs that a record does not

A record answers what happened to this patient. A queue answers what is stuck, and who has it. Those are different data shapes, and it shows up in five places.

Position, not just presence. A referral field tells you a referral exists. It cannot tell you the letter arrived on Tuesday, was triaged Wednesday, and has been sitting in “waiting on patient” ever since. That is the difference between a stored document and a tracked referral.

Intake without retyping. GP letters arrive as scanned faxes, PDFs and email attachments. Somebody keys each one in by hand, which is slow and drops characters. AI Intake reads the document instead and pre-fills the referral. Here’s how that extraction works, including what it does with a bad scan.

Contact that leaves a trail. Acknowledging the referral, confirming the appointment, chasing the patient who never replied: all of it is done from the referral itself, and each message is logged against it, so the next person on reception can see what was already tried rather than repeating it.

Ownership that survives a day off. A referral in a queue has a stage and a person attached to it. A referral in an inbox has whoever happened to open the email, which is why the referrals that go quiet are so often the ones handled by someone who then took annual leave. That is the mechanism behind most patients who never get scheduled.

Referral-shaped numbers. Your PMS reports on utilisation and billing. A referral tracker reports on conversion, time from letter to first appointment, and which referrers send you work that turns into visits: the metrics a practice manager is actually asked for.

The gap is not theoretical. A systematic review in the Journal of General Internal Medicine found only 35% of specialty referrals result in a documented visit. Not all of that is administrative. But the administrative share is the part sitting in your left-hand column, and it is the part you control. The referral leakage calculator puts a number on what it costs your practice.

Does your practice actually need one?

Plenty of practices do not. If reception can already answer every question below without opening anything, the PMS is doing the job and you should spend the money elsewhere.

If your answers all sit on the comfortable side, keep your PMS and stop reading. If two or three landed on the right, that is the pattern behind five reasons practices lose referrals, and the reason a spreadsheet only holds for so long.

Running both, sensibly

A referral tracker is not a PMS replacement, and any vendor telling you it is should worry you. The sequence is simple: the referral arrives and enters the board; your team triages it, contacts the patient and works it through to a booking. From the booking onward, the patient belongs to the PMS: calendar, notes, claims, recalls. Two systems, one handover point, no overlap to argue about.

That handover is also the honest boundary of what a tool like ours does. We work the inbound queue and nothing else.

Where SimpleRef fits

Every arriving referral sits on a board through triage, patient contact and booking, so “waiting on forms” and “gone quiet” are columns you can see rather than folders someone has to remember. Tell us how your practice triages and we build those stages into your board. You are not handed a template designer to work out yourself. Each specialist also gets their own referral inbox, so doctors action their queue without working through the whole system. The full feature list is here.

Pricing is published: $299/month for up to four doctors, $499/month for up to ten with priority support, both including GST, with a 14-day free trial. Email is included on every plan; SMS is a paid add-on. Seats are not sold individually. When the practice outgrows a plan, you upgrade it.

On data, precisely: patient records are hosted in Australia. Billing is processed by Stripe, which operates offshore. AI Intake is part of every plan, and when someone uploads a document it is sent to Google’s AI service for extraction, which is not hosted in Australia. Nothing goes to Google unless a document is uploaded. Full detail on the security page.

For how this sits against secure messaging networks and referral platforms (different categories again, often bought alongside a PMS), see the Australian referral software landscape.

The useful next step is a conversation, not a signup. Ask for a twenty-minute walkthrough and we’ll put your kind of referrals on the board, or start a 14-day free trial and look around first.