Halaxy Integration
Custom automations for Halaxy: built around how your practice runs
LUNA connects your AI receptionist and automations to Halaxy through its public API, built for your practice as part of setup: bookings land straight in your Halaxy calendar, participant and patient details reach the right record, and appointment changes flow back automatically.
What we build
Built around your practice, not a product
Halaxy's API covers most of what runs bookings, fees, and participant records day to day. LUNA turns that into automations built around how your practice actually works, not a fixed feature list.
AI receptionist bookings into Halaxy
When a caller books through LUNA's AI receptionist, the appointment is created directly in Halaxy against the right practitioner and appointment type, so nobody re-types it by hand.
Participant and patient intake
New participant or patient details captured over the phone or through an online form land in the correct Halaxy record, ready before their first appointment.
Fee awareness in confirmations
Halaxy's fee data feeds into booking confirmations and reminders, so clients and participants see the right amount before they arrive, not after.
Appointment change reconciliation
Reschedules and cancellations made in Halaxy flow back into your calendar and messaging, so the practice and the client are always looking at the same booking.
Recall and follow-up automations
Patients or participants overdue for a follow-up session get a prompt automatically, instead of relying on someone remembering to check the list.
AHPRA-safe review requests
For AHPRA-registered allied health practitioners, a review request goes out after a completed appointment, worded to stay inside AHPRA advertising guidelines: no testimonials, no outcome claims.
NDIS-aware participant communication
For NDIS providers, reminder and follow-up wording is checked against NDIS Quality and Safeguards Commission guidance instead of AHPRA, since most NDIS support work sits outside AHPRA's remit.
Something specific to your practice
If it touches Halaxy's API (appointments, fees, webhooks, participant records) we can likely build it. Tell us the problem, not the feature.
How it works
API-based and honestly explained
Built on Halaxy's FHIR-based API
Halaxy exposes a public API built on the FHIR standard through developers.halaxy.com: appointment creation and updates, fee retrieval, and more, all available for us to build against.
Webhooks, not just polling
Halaxy supports webhooks alongside its API, so changes can push through as they happen rather than waiting on a scheduled check, wherever the workflow calls for it.
Per-key access control
Access runs through Halaxy's API Key Manager, so an automation only ever has the permissions granted to the key it was set up with. Nobody gets more access than the practice allows.
Scoped to your practice, not a template
We start with a discovery call to understand what's actually slowing bookings or intake down, then scope the specific connection against what Halaxy's API exposes. You own the Halaxy account and any connected tools. We don't hold your setup hostage.
By practice type
What this looks like in practice
Allied health clinics
Physio, podiatry, and OT appointments booked by an AI receptionist land straight in Halaxy against the right practitioner, with fee information ready before the client arrives.
Therapy & counselling practices
New-client intake and consent details are captured before the first session and written straight into the Halaxy record, so nothing gets filled out twice in the waiting room.
NDIS providers
Participants and support coordinators can book, reschedule, or check appointment availability by phone, with every call answered and every booking landing in the right Halaxy record, without pulling your team off support work to manage the phone.
Learn more →Multi-practitioner allied health practices
A shared view of bookings and follow-ups across every practitioner, so the practice manager isn't chasing five different calendars to work out who's free.
Built for your practice, not sold off the shelf
LUNA builds your Halaxy connection as part of setup, using Halaxy's API, scoped to how your practice runs rather than sold as a boxed product. For AHPRA-registered allied health practitioners, anything patient-facing (reminders, review requests, follow-up wording) is checked against AHPRA advertising guidelines before it goes live. For NDIS providers, the same wording is checked against NDIS Quality and Safeguards Commission guidance instead, since most NDIS support work sits outside AHPRA's remit.
FAQ
Common Questions
What does the Halaxy API actually allow?▼
Halaxy's public API is built on the FHIR standard and covers appointment creation and updates, fee retrieval, and webhooks for real-time changes, all behind per-key access control through Halaxy's API Key Manager. If your practice runs bookings, fees, or participant records through Halaxy, there's usually a way to connect it.
Does LUNA replace Halaxy?▼
No. LUNA connects to Halaxy, it doesn't replace it. Your practice keeps running on Halaxy exactly as it does now. LUNA builds the automation layer on top, so bookings, participant details, and appointment changes move between Halaxy and your other systems, like an AI receptionist, without anyone re-typing them.
Is Halaxy natively integrated, or is this a custom build?▼
It's a custom build. LUNA builds the connection as part of your setup, using Halaxy's public API, scoped to what your practice actually needs rather than installed as a generic plug-in. That's a feature: the connection matches your practitioners, appointment types and intake flow from day one.
What happens if the Halaxy API is briefly unavailable?▼
Calls still get answered and messages still get captured either way, since LUNA's AI receptionist doesn't depend on Halaxy being reachable to pick up the phone. If the Halaxy API is briefly down, bookings queue and reconcile into the right record once it's back, instead of getting lost.
How is this different for NDIS providers versus AHPRA-registered practices?▼
NDIS providers sit under the NDIS Quality and Safeguards Commission, not AHPRA, so any participant-facing wording we build, like reminders and follow-ups, is checked against NDIS guidance instead. For AHPRA-registered allied health practitioners using Halaxy, we check the same wording against AHPRA's advertising guidelines. The right rules depend on who regulates your practice, not which software you run.
How long does setup take?▼
It depends on scope. A single connection, like AI receptionist bookings landing in Halaxy or participant intake, is typically a few weeks. Multi-automation builds, like bookings plus fee sync plus reconciliation, take longer. We scope it properly on a discovery call before quoting.
Have a Halaxy situation we haven't listed?
Tell us what your practice needs and we'll tell you honestly whether Halaxy's API can do it.
Questions? hello@lunasystems.com.au