August 2026
Referral management in New Zealand: an honest guide
Systemaize Health · Published 17 August 2026 · Reviewed 17 August 2026
New Zealand already has national rails for moving referrals — ERMS, HealthLink and CareConnect carry them between practices and hospitals every day. What the system has less of is the operations layer around those rails: the work of making a referral complete before it travels, checked against the pathway's criteria when it arrives, and visible to the person waiting afterwards.
What do the existing rails do?
The rails move referrals. An e-referral service carries a structured referral from a GP's practice management system to the receiving service, reliably and securely. That part of the system works, it is national, and nobody should replace it.
What the rails do not do is the operational work around the journey: they do not make an incomplete referral complete, they do not check it against the receiving pathway's own criteria before a person spends time on it, and they do not keep the patient informed about where things are up to. Those gaps are operational, not technological — and they are where referrals bounce, stall and go quiet.
What is an operations layer, and what is it not?
An operations layer sits on the rails rather than beside them. Referrals still travel the way they travel today; the layer works on what is in them and around them — completeness before sending, prepared review on arrival, criteria kept visible, and the wait made visible to the person in it. Systemaize Pathways is our operations layer, and it is clinician-governed: the system prepares, clinicians decide.
It is not another inbox, not a replacement e-referral service, and not a system anyone has to migrate to. An honest test for anything in this category: ask what happens to your existing rails. If the answer is 'replace them', it is not an operations layer.
How should you compare options honestly?
Ask the same questions of everyone, including us. Does it run on the rails you already use, or replace them? Who governs what the software does — by name? Where does the data live, and under whose law? What does the evaluation measure, and will it be published? And can the vendor show you the capability working, rather than describe it? Any answer that starts with a migration, an anonymous governance page, or an unpublishable evaluation tells you what you need to know.