Automating new patient intake at a Brisbane physiotherapy practice cut the admin gap between booking and first appointment from two working days to under twenty minutes — here is exactly what the workflow replaced and what it now does instead.
The problem with manual patient intake
A seven-practitioner physiotherapy clinic in Brisbane's inner north was growing steadily. New patient enquiries were landing through the website contact form, phone calls, and referral letters from GPs and specialists. The problem was not demand — it was what happened in the hours between a patient booking and arriving for their first session.
The clinic's two admin staff handled intake manually. A new patient would book, and then a chain of tasks would begin: send the intake form by email, wait for it to return, chase it if it did not, manually re-enter the information into the practice management system (Cliniko), check health fund details, prepare a file, confirm the appointment by SMS, and brief the practitioner before the session.
On a good day, with a cooperative patient, this took around ninety minutes of combined staff time per new patient. On a bad day — a late form return, a health fund query, a missed phone call — it stretched to two days or more, sometimes pushing prep work into the morning of the appointment itself.
The clinic was seeing around fifteen new patients a week. That translated to roughly twenty-two hours of intake-related admin across the team every week. The practice owner recognised this as the main bottleneck limiting capacity: both admin staff spent a substantial portion of their time on tasks that followed a fixed, predictable pattern.
That is exactly the kind of repetitive, rule-driven work that workflow automation is built to handle.
What the automation workflow included
FluxWork mapped the full intake process across five stages, then built automated workflows covering four of them. The fifth — clinical review of complex or high-risk cases before booking — remained with the treating practitioners.
Stage 1: Smart intake form delivery. When a new patient books (via Cliniko's online booking or a phone call logged by admin), an automated sequence fires immediately. The patient receives a branded email with a link to a dynamic intake form. The form is pre-populated with what is already known — name, contact details, appointment time — and adapts based on referral type. A GP referral triggers different questions than a self-referral, capturing the referring practitioner's details and any attached clinical notes.
Stage 2: Automated follow-up if the form is not returned. If the patient has not completed the form within four hours of booking, the workflow sends a follow-up SMS. At twelve hours, a second SMS follows. Both messages are plain and include a direct link. Admin only sees a task if the form is still outstanding after twenty-four hours, which happens with roughly one in twelve patients — usually older patients who prefer a phone call.
Stage 3: Data extraction and record entry. When the form is submitted, AI extracts the structured fields — presenting complaint, health fund provider and membership number, GP details, current medications, emergency contact — and writes them directly to the patient record in Cliniko. The extracted data is flagged for admin review on submission, but the review takes under two minutes because the fields are already populated. Admin is checking, not re-entering.
Stage 4: Health fund pre-check and appointment confirmation. The workflow queries the patient's health fund membership status via a lightweight integration and drafts the appointment confirmation message. The confirmation includes a personalised preparation note based on the presenting complaint — instructions about appropriate clothing for a lower-limb assessment, for example. Admin reviews and sends with one click, or the workflow sends automatically where the health fund check returns a clear result.
For a full picture of how custom automation builds are structured, see FluxWork's services.
How does automated intake handle patients who do not respond?
This is the question every practice asks first, because the non-responsive patient is the edge case admin staff worry about most.
The answer is escalation logic. Every automated step in the sequence has a defined timeout and a handoff rule. If a patient has not responded to the form request within twenty-four hours, a task appears in the admin queue with the patient's name, appointment time, and a note that intake is outstanding. Admin can call the patient directly from the queue. The automation does not replace the call — it removes the need to manually track which patients need one.
In practice, the clinic found that the overnight reminder SMS resolved most non-responses before the twenty-four hour escalation triggered. The morning-after message caught patients who had received the original form during work hours and had not found time to complete it.
Business.gov.au's guidance on record keeping notes that all businesses — including healthcare practices — must maintain accurate, retrievable client records. An automated intake workflow supports this by capturing information in a structured format from the start, rather than relying on email threads and manual re-entry that can introduce gaps or transcription errors.
The results after 60 days
The practice measured outcomes at the sixty-day mark across three metrics: admin time per new patient, form completion rate before appointment, and practitioner preparation quality.
Admin time per new patient dropped from an average of ninety-two minutes to fourteen minutes. The remaining fourteen minutes covers the health fund review, the occasional manual follow-up call, and the final confirmation send. For patients where the health fund check returns cleanly and the form is completed promptly, admin involvement falls below eight minutes.
Form completion rate before appointment rose from sixty-eight per cent to ninety-one per cent. The jump came almost entirely from the automated SMS reminders, which gave patients a low-friction path to complete the form on their phone rather than needing to open a laptop.
Practitioner preparation improved because intake data was already structured in Cliniko before the session. Practitioners described starting each first appointment with the presenting complaint, medication list, and referral context already reviewed — rather than reading through an email thread at their desk between patients.
Across fifteen new patients a week, the reduction in admin time freed approximately twenty hours per week — the equivalent of returning half an admin role to other tasks without reducing headcount.
Why it matters for Australian allied health practices
The intake bottleneck at this clinic is not unusual. Most allied health practices running practice management software like Cliniko, Power Diary, or Nookal have the same structure: a capable booking system at the front end, followed by a manual handoff for everything that happens between booking confirmation and first appointment.
The automation does not require replacing the practice management system or restructuring the team. It sits in the gap between booking and clinical appointment, handling the data-collection, data-entry, and follow-up steps that follow an identical pattern every time.
For a smaller practice — two practitioners, twenty new patients a month — the same workflow saves around six hours of admin time monthly. That is enough to meaningfully reduce admin load on a sole operator or a small team, without adding headcount. For a larger group practice, the savings scale accordingly.
The principles apply equally across allied health: occupational therapy, speech pathology, psychology, chiropractic, and podiatry practices all face the same intake pattern. Anywhere the process involves a structured form, a health fund check, and a manual handoff to a practice management system is a candidate for the same approach.
If intake administration is where your practice's time goes, a free workflow review takes ninety minutes and produces a clear, specific picture of what can be automated and what genuinely needs a human.
Frequently asked questions
How does patient intake automation connect to Cliniko or Power Diary?
Automation workflows connect to practice management systems via their published APIs or through integration platforms. When a booking is made, the workflow triggers automatically — the completed intake form's data is extracted and written to the patient record without manual re-entry. The practice management system stays the source of truth; the automation adds a structured data collection layer between the patient and the existing system.
Is patient data handled securely in a workflow automation setup?
Any workflow handling patient information should comply with the Australian Privacy Act 1988 and the Australian Privacy Principles covering health information. FluxWork builds automation workflows that process patient intake data within compliant cloud infrastructure, passing information only between systems the practice already uses. Practices should review their specific obligations with their professional association or a privacy adviser.
What happens if a patient does not complete the intake form before their appointment?
Automated follow-up sequences send timed reminders if the form is not completed within a set window — typically an email and two SMS messages spaced across the first twenty-four hours. If the form remains outstanding after the final reminder, the workflow creates a task in the admin queue with the patient's details and appointment time, so a staff member can follow up by phone. The automation handles the standard path and escalates exceptions cleanly.
How long does implementation take for a standard allied health practice?
For a practice using an established management system with a supported API — Cliniko, Power Diary, or Nookal — a standard intake automation workflow typically takes two to three weeks from scoping to go-live. This includes the intake form build, integration setup, follow-up sequence logic, and testing with real bookings before full deployment.
Can the intake workflow handle GP referrals and self-referrals differently?
Yes. The intake workflow uses conditional logic based on how the patient arrived. A patient with a GP referral is routed to a form variant that captures the referring practitioner's details and any clinical notes, while a self-referral triggers a simpler path. Both variants write structured data to the same fields in the patient record, so the practitioner sees the same information format regardless of how the patient was referred.