Most Australian allied health practices running Halaxy have already solved the hard scheduling and billing problem. Bookings sync, Medicare and DVA claims go through, invoices get issued, and the calendar mostly runs itself. What Halaxy was never built to do is the surrounding admin: the recall messages, the referral letter drafts, the overdue invoice follow ups, and the intake triage that still land in a practice manager's inbox every week. That's the gap Claude sits in, working alongside Halaxy rather than replacing it.
What Halaxy already handles well
Halaxy is a solid system of record for a clinic. It's worth being clear about what it already does well, because the goal here isn't to duplicate it.
Online booking, calendar sync, and automated SMS or email appointment reminders.
Medicare, DVA, and private health fund claiming and rebate processing.
Invoicing, receipts, and basic practice financial reporting.
Clinical note templates and a patient record store that meets Australian health record standards.
The admin Halaxy doesn't touch
Ask a practice manager in Sydney or Melbourne where their week actually goes and the answer is rarely booking appointments. It's chasing three week old invoices with a tone that's polite but firm. It's turning a clinician's session shorthand into a referral letter a GP can actually use. It's noticing that a patient has cancelled twice in a row and deciding whether to call or let the recall sequence handle it. None of that lives inside Halaxy's workflow, so it either gets done manually after hours or it doesn't get done at all.
Where Claude fits alongside Halaxy
We don't connect Claude to clinical notes or Medicare data directly. The useful work sits one layer up, on the admin tasks a practice manager already owns.
Drafting recall and reminder messages in the clinic's own tone, ready for a human to send.
Turning a clinician's dictated or typed session shorthand into a first draft referral letter for review.
Flagging patients with repeated cancellations or no-shows so front desk staff can follow up directly.
Drafting overdue invoice reminders, matched to how many times a patient has already been chased.
Triaging new patient intake forms against a clinic's referral criteria before they hit the booking queue.
In every case, Claude produces a draft. A staff member reads it, edits it if needed, and sends it. Nothing goes to a patient automatically, and nothing clinical gets summarised without a clinician checking the output first.
Privacy and the Australian Privacy Principles
Health information is sensitive information under the Privacy Act, which means a higher bar applies before any of it touches a third party tool. Our starting position for an Australian allied health client is straightforward. Clinical notes and Medicare item numbers stay inside Halaxy and the clinic's own systems. Claude works from de-identified summaries or administrative fields only, such as appointment counts, invoice status, or a clinician's own draft text with identifying details removed. A short data handling agreement sets out exactly what does and doesn't leave the practice, and every draft is reviewed by a person before it's used.
A week in the life
Take a Melbourne physiotherapy clinic with six practitioners. Monday morning, the front desk exports Friday's cancellation list from Halaxy. Claude drafts three tailored recall messages, one per patient, referencing their last visit type rather than sending a generic "we missed you" line. Wednesday, a clinician dictates notes for a workers compensation referral and Claude turns the shorthand into a structured draft letter, ready for the clinician to check facts and sign off. Friday, the invoice list flags four accounts more than 30 days overdue, and Claude drafts a firmer follow up for the two that have been chased once already, and a gentler one for the two being contacted for the first time. None of this touches the clinical record. All of it used to be written from scratch by whoever had a spare twenty minutes.
What a pilot looks like
A typical setup for a five to eight clinician practice runs as a fixed fee project, usually around $3,500, and covers one or two admin workflows end to end. Recall messaging and overdue invoice follow ups are the two most common starting points, because the time saved is easy to measure. Practices we've scoped this for estimate roughly five to seven hours of admin time back each week once drafts stop needing to be written from a blank page, worth well over $20,000 a year in reclaimed practice manager time for a mid-sized clinic. Clinics in Brisbane and regional Queensland have asked for the same setup once they hear the numbers from a Sydney peer.
If admin overflow is what's slowing your practice down rather than the booking system itself, it's worth a short conversation. Book a brainstorm and we'll map the workflows worth automating first.
