The platform you pick decides more about your website than any design choice. It decides whether patients book on a page that looks like yours or inside an embed that doesn't, whether prescribing and My Health Record happen in one place or three, and how much custom engineering you pay for. We have integrated all three of these for telehealth clinics: some of our clients run on Halaxy, some on Cliniko, and most on MediRecords. This read is our honest comparison, written from the integration side. It is not sponsored by anyone, and the right answer depends on your budget and how custom you need the patient journey to be.
The short answer
| MediRecords | Cliniko | Halaxy | |
|---|---|---|---|
| Our rank for a custom patient journey | 1 | 2 | 3 |
| Our rank for a fast, low-budget launch | 3 | 2 | 1 |
| Booking on your website | Fully custom through the API | Custom through the API, or an embed | Embed (iframe) for telehealth bookings |
| API | Detailed, with good guides; whole journey possible | Clean and easy to build against; strong support | Available, but complex in our experience, and it didn't support telehealth appointments when we last built on it |
| E-prescribing | Built in | Through a connected app (we've used Parchment) | Check current integrations |
| My Health Record | Built in | Not connected | Check with Halaxy |
| Video consults | Separate platform (we connect Coviu) | Built-in telehealth feature | Built-in telehealth |
| Cost model | Licence, with the API (Connect) as a paid add-on | Per practice, banded by practitioner count, in US dollars | Free to start, paid credits for add-ons |
The rest of this read explains each row.
MediRecords: our first choice for custom builds
MediRecords is the platform we reach for when a clinic wants its own branded patient journey from first click to repeat script. Three reasons.
The APIs cover the whole journey. MediRecords sells API access as a product called Connect, which includes its own REST API and a FHIR API, each with its own token. With it we can build booking, intake, patient records and follow-ups in the clinic's own interface, and the documentation is good enough that we spend our time building rather than guessing.
Prescribing and My Health Record are already there. Practitioners can issue electronic prescriptions without leaving the platform, and My Health Record is connected under the hood. That matters more every year, with the government planning to make online prescribers share medicine information with My Health Record by default from 2027.
One system of record. Fewer moving parts means fewer places for data to go wrong.
The trade-offs:
- Video is separate. MediRecords doesn't include video consults in the way the other two do, so we connect a separate plan, usually Coviu.
- API access costs extra and isn't publicly priced. Connect is bought separately and priced through MediRecords, so get a quote early.
- Read the API terms. They limit how a developer engaged by one clinic can reuse an integration for other customers. That shapes how we scope and hand over each build.
Our full build notes are in MediRecords API integration.
Cliniko: the friendliest API, with two gaps
If price isn't the main constraint and you're choosing between Cliniko and Halaxy for a custom journey, choose Cliniko. Its API is clean, well documented and easy to implement, its support team is good on integration questions, and there's a strong developer community around it. You can embed its booking page or build a fully custom booking flow and patient portal on the API.
The two gaps for telehealth:
- Prescribing isn't native. You connect an e-prescribing app. We've used Parchment, which adds its own cost.
- No My Health Record connection. If that becomes a requirement for online prescribers, Cliniko clinics will need another route.
On cost, Cliniko charges per practice in bands by practitioner count, not per user, and quotes in US dollars: US$45 a month for one practitioner, up to US$395 for 26 to 200, with unlimited admin and reception users and SMS at 10 cents a message. Add your prescribing app and messages on top.
Our build notes are in Cliniko API integration.
Halaxy: the quickest start, the hardest custom build
Halaxy is where we point clinics that want to launch quickly on a small budget, often clinics with physical rooms adding telehealth. You set things up in Halaxy's admin, embed its booking page on your website, and you're taking bookings. It's free to start, with paid credits for add-ons such as white-labelled emails and SMS, and it includes a telehealth module.
The catch is the patient experience when you rely on the embed, which most Halaxy clinics do because building custom on its API is hard:
- The embed isn't fully mobile responsive, and on a phone it can feel like a second website sitting inside yours.
- The journey is long. In our testing, patients can spend five to ten minutes booking inside the embed.
- Branding is limited, so the experience doesn't feel like your clinic.
- The API is complex, and when we last built on it, it didn't support telehealth appointments, so a fully custom telehealth booking flow wasn't possible.
We handle a lot of edge cases to make Halaxy embeds work well. The details are in Halaxy online booking on your website.
Which one should you choose?
Start from the patient journey you want, then your budget.
- "We want to launch in weeks, budget is tight, an embedded booking page is fine." Halaxy. Plan to improve the experience later.
- "We want a branded booking flow and patient portal, and we're happy to add a prescribing app." Cliniko.
- "We want the whole journey custom, prescribing in one place and My Health Record ready." MediRecords, plus a video platform.
- "Our workflow is unusual enough that none of these fit." Talk to us before building custom practice software; it's rarely the cheapest answer. See our custom software service.
What about privacy and patient data?
Whichever platform you choose, patient data should live in it, not in email inboxes or website form tools. Check where each platform stores data, what it shares overseas and what it decides automatically on your behalf, because all three feed your privacy policy. From 10 December 2026, automated decisions that significantly affect patients also need disclosing.
Sources
All checked 21 Nov 2026.
- MediRecords Connect: a simple introduction to APIs and integration, MediRecords
- Cliniko developer API, Cliniko
- Cliniko pricing, Cliniko
- Enable online bookings, Halaxy
Finished this read?
- OpenedToday
- FinishedNot yet
Written by
Kevin MatthewsHead of Development
Kevin leads engineering at SingletonTec and has spent 10+ years building production-grade websites, apps and systems for businesses.
