Clinic Apps and the Intake Form

Comparisons of Australian practice management software are almost always written about bookings and billing. Both matter, and both are largely solved — every serious system in this market handles an online booking and a claim.

The thing that actually eats a clinic’s day is the intake form, and it is where these systems differ most.

Why the intake form is the axis

Consider what a new patient costs you before they are seen.

Someone emails a form or hands over a clipboard. The patient fills it in, sometimes at home, more often in the waiting room in a hurry. Reception transcribes it into the system, or scans it and attaches an image nobody can search. The practitioner reads it for the first time as the patient sits down.

Every step there is either staff time or clinical time, and the failure modes are specific: illegible handwriting, blank fields nobody chased, a medication list typed in wrong, a consent that was signed on paper and now lives in a filing cabinet.

A properly implemented digital intake changes the shape of that entirely. The patient completes it before arriving, on their own phone, and the answers land in their record as structured data rather than as an attachment.

That is the difference worth comparing on.

What the main systems do

The Australian allied health and clinical market is dominated by a handful of systems, and they differ less in whether they have intake forms than in what happens to the answers.

Cliniko is the most direct about this. Its own documentation describes customised intake forms, questionnaires and surveys, sent to a patient to complete before they arrive, with the submitted form added automatically to the patient’s record. That last part is the whole point — the answers are in the record, not in an inbox.

Halaxy is the other system with a large share of the same market, with Medicare integration and a strong presence in allied health.

Power Diary, Nookal and coreplus all support digital forms to varying depths, with the differences sitting in customisation, conditional logic, and how much of the answer set becomes structured data rather than stored text.

Several of these also support a practice-branded patient portal, where booking, form completion and shared documents sit in one place under the clinic’s own name rather than the vendor’s.

Two honest caveats on the above. First, we have verified Cliniko’s description against its own feature documentation; the depth of the others’ form capabilities is harder to compare from the outside, and vendor comparison pages in this market are mostly written by competitors. Second, these products change often. Ask each vendor the specific questions below rather than relying on any comparison table, including this one.

The four questions that separate them

If you are evaluating, these are the questions that actually distinguish the products, in order of how much time they save.

1. Does a completed form land in the patient record as structured fields, or as an attachment? This is the single biggest difference. Structured answers can be searched, reported on, and pre-filled next visit. An attached PDF is a filing cabinet with extra steps.
2. Can the form branch? If the answer to “are you currently taking any medication” is no, a good form does not then ask six follow-up questions. Conditional logic is the difference between a form patients finish and one they abandon.
3. Is it actually usable on a phone? Most patients will complete this on a phone, in a car park, with one hand. A form designed for a desktop screen is a form that gets half-completed.
4. What happens to the consent? Consent collected digitally needs to be retrievable and attributable later. Ask what the system stores — the answer, the timestamp, the version of the wording they agreed to — because “we have their consent” is only useful if you can produce it.

★ Insight ------------------------------------- Question four is the one clinics skip and the one that matters most later. A consent is a claim about something that happened at a moment in time, so it needs the wording that was on screen stored alongside the agreement — not just a tick. If the consent text is edited later and the system only stored “agreed: yes”, every historical consent now refers to wording nobody agreed to. This is the same class of problem as a signed record that does not say what it signed. -------------------------------------------------

When a clinic should build instead

The default answer is do not. A practice management system carries Medicare integration, clinical note templates, appointment reminders and a compliance posture that would take years to reproduce, and it is maintained by people who do nothing else.

Three situations change that.

Your intake is a clinical instrument, not a form. If what you collect is a scored assessment, a standardised questionnaire, or something with a calculation and a threshold behind it, a generic form builder will get you the questions and not the result. The scoring ends up on paper or in a spreadsheet beside the system, which is the worst of both.

The patient’s experience continues between visits. Exercise programmes, symptom tracking, adherence check-ins — anything where the patient is meant to interact with you between appointments. Practice management systems are built around the appointment. If your model is continuous, the app is the model.

You are multi-site and the intake is your differentiator. If consistency of intake across locations is part of what you sell — to a referrer, an insurer or a corporate client — then the form is an asset and it should be yours.

Outside those, the right move is to pick the system whose forms answer the four questions above, and spend the build budget on the website that gets patients to the booking page.

Where the data lives, and why a clinic should ask

One question that sits underneath all four, and belongs in the evaluation rather than after it: where is the information stored, and who can get it out.

For a clinic this is not an abstract concern. Patient records carry obligations that outlast the software — retention periods measured in years, a right for the patient to access what you hold, and a duty to notify if the information is exposed. Those obligations are yours regardless of which vendor holds the file.

Three questions worth asking every vendor on the shortlist, in writing:

• Where is the data physically stored? Onshore storage is not a legal requirement in every case, but it is a question a patient may ask you, and “I don’t know” is a poor answer.
• What exactly can you export, and in what format? Not “can we export” — every vendor says yes. Ask whether the export includes intake responses as structured data, clinical notes, attachments and the consent records, or only a subset.
• What happens to your data if you leave? How long is it retained, how is deletion confirmed, and what does it cost to get a full copy.

A practice that cannot answer these about its own system has outsourced a responsibility it cannot actually delegate, and the moment it matters is the moment it is hardest to resolve.

The check worth running

Book yourself into your own clinic as a new patient, on your phone, and complete your own intake form.

Time it. Note where you would give up. Note whether what you typed appears in the record as fields or as a picture of a form.

Most clinics have never done this, and it is the only evaluation that tells you what you are actually asking of people before they have even met you.

Vendor capabilities checked against publicly available documentation, September 2026. This is general information about software, not clinical or compliance advice.

---

Awesome Apps is an app developer in Sydney building custom iOS and Android apps for Australian businesses. Clinic websites and booking pages come from Cosmos Web Tech, IT and cloud from Cloud Geeks, and we are part of Ganda Tech Services.