Skip to content
Skip to content

Healthcare AI for Adelaide Practices

We are based in Melbourne and we serve Adelaide remotely. Thirty minutes is not a timezone problem. The thing actually worth knowing is that South Australia has no privacy Act, and most vendors selling you health AI do not know that.

Book a Free Practice AssessmentView Healthcare Plans

No Adelaide Office, and Thirty Minutes Is Not a Problem

One real disclosure and one non-issue we could easily have dressed up as a commitment.

The disclosure: Yes AI is a Melbourne consultancy, Australian owned and operated. There is no Adelaide office, no Adelaide staff, and nobody who will walk into your practice for an assessment or a training session. Adelaide practices are served remotely. Search for healthcare AI in Adelaide and you will find pages promising a local implementation team; follow enough of them and the local team is a national team and the on-site visit appears later at a rate. We are not running that.

The non-issue: Adelaide is on ACST, thirty minutes behind Melbourne, and because South Australia observes daylight saving alongside Victoria the gap stays at thirty minutes all year round. Your 9am is our 9.30am. That is a rounding error, not a drawback. We could write four paragraphs here about how we heroically absorb the half hour, and it would be nonsense, the honest version is that if we were pitching you from Perth this would be the most important section on the page, and from Melbourne it is a footnote.

Which leaves the question of what a Melbourne provider can actually offer an Adelaide practice that is worth reading. The answer is on the rest of this page, and it starts with something genuinely strange about South Australia that we suspect your last three vendors did not mention.

South Australia Has No Privacy Act

Not a loophole, not an oversight anyone is about to fix for you, just a genuinely unusual position that changes where your obligations live.

New South Wales has the Health Records and Information Privacy Act 2002. Queensland has the Information Privacy Act 2009. Victoria, the ACT, Tasmania and the Northern Territory all have privacy legislation of their own. South Australia is the only mainland state without dedicated privacy legislation.

What the SA public sector runs on instead is an administrative instrument: Premier and Cabinet Circular PC012, which sets out Information Privacy Principles binding SA government agencies as a matter of government policy rather than statute. It is real, it is followed, and it is not an Act of Parliament. There is no South Australian equivalent of the HRIP Act for a vendor to gesture at.

For a private Adelaide practice, that mostly simplifies things: the federal Privacy Act 1988 (Cth) and the Australian Privacy Principles do essentially all the work, and health information is sensitive information under that Act, the most protected category it has, with a higher bar for collection, use and consent.

Where it stops being simple is SA Health-adjacent work. If you contract to SA Health or another SA agency, the substantive obligations arrive through the contract and the circular, not through a statute you could have looked up beforehand. Which means two SA contracts can impose materially different requirements on the same practice running the same system, and it means a vendor telling you they are “compliant” is telling you nothing. Compliant with what? We would rather read the agreement with you and map what it actually requires.

General information on how these obligations typically apply, not legal or clinical advice. We work alongside your practice’s legal and privacy advisers rather than around them.

What That Means for Your Build

When the floor is set by contract rather than statute, the contract is the design document.

The Contract Is the Instrument

With no state privacy Act to set the floor, SA Health-adjacent obligations arrive through the agreement. That makes the contract the document that governs your system, not a formality.

  • Data handling terms read before design, not after signing
  • Security expectations identified as requirements, not aspirations
  • Breach notification path agreed rather than improvised
  • Termination and data-return position settled up front

PC012 Instead of a Statute

The SA public sector runs on Premier and Cabinet Circular PC012, Information Privacy Principles binding agencies as government policy rather than legislation.

  • No SA analogue to the NSW HRIP Act to point at
  • Obligations reach a private practice via contract, not statute
  • Two SA contracts can require materially different things
  • “We are compliant” means nothing without naming with what

Federal Law Does the Heavy Lifting

For a private Adelaide practice, the Privacy Act 1988 (Cth) and the Australian Privacy Principles are effectively the whole floor, and health information sits in the most protected category the Act has.

  • Health information is sensitive information: a higher bar
  • APP 8 governs disclosure to an overseas model provider
  • Australian data residency where the use case allows it
  • The assessment recorded, not assumed

What We Will Not Tell You

An unverified efficacy claim about a health service is the most damaging sentence a page like this can carry, so it is not here.

  • No invented ROI figure for your practice
  • No no-show reduction percentage we have not measured
  • No practice counts or patient volumes we cannot verify
  • Build the number from your data, or do not act on one

AI Around Care, Never Inside It

A registered practitioner makes every clinical determination. This is a design boundary, not a disclaimer.

Legitimate and useful

  • Booking, rescheduling and cancellation handling
  • Appointment reminders and recall messages
  • Intake forms captured before the consult
  • Callback requests routed to the right person
  • Referral paperwork chased and acknowledged
  • After-hours enquiries captured for a human to answer

Never automated

  • Triaging a patient’s symptoms
  • Interpreting a result or a report
  • Telling a patient whether something is urgent
  • Reassurance that reads as clinical advice
  • Anything a registered practitioner must determine
  • Generating a testimonial about clinical care

The last one is a genuine legal constraint rather than a style preference. AHPRA’s advertising guidelines, made under the Health Practitioner Regulation National Law, prohibit testimonials in advertising a regulated health service, and a language model will write one into a friendly recall message unless the system stops it, on your registration rather than ours.

What Applies Instead

With no state Act, the federal layer is the layer.

Privacy Act 1988 (Cth) & the Australian Privacy Principles

Effectively the whole floor for a private Adelaide practice. Health information is sensitive information, the most protected category the Act has, with a higher bar for collection, use and consent.

Australian Privacy Principle 8: cross-border disclosure

Sending patient data to a model provider hosted overseas is a disclosure to an overseas recipient. Not automatically prohibited, but not free either: you generally remain accountable for what that recipient does with it. Keep data in Australia where the use case allows; where it does not, know the vendor, the region and the terms.

Premier and Cabinet Circular PC012 (SA)

Information Privacy Principles binding the SA public sector as government policy rather than legislation. It reaches a private practice through contracted work for SA Health or another SA agency, which is why the agreement, not a statute, is the document that governs your system.

My Health Records Act 2012 (Cth)

Where your systems touch My Health Record, the limits on collection, use and disclosure are strict and backed by criminal penalties. Not a place for an integration that seemed convenient at the time.

Where to Next

Other states, other regimes, and the one city where we are actually in the building.

Healthcare AI Sydney

The opposite situation: NSW has a health privacy Act that reaches private practices, and procurement that will ask you about it.

Sydney

Healthcare AI Melbourne

Where we actually are: the one city where in person is a given rather than a line item.

Melbourne

Compliance Guide

The Privacy Act, the APPs, and where AI genuinely sits in an Australian practice.

Read the guide

Frequently Asked Questions

What Adelaide practices ask before engaging a provider in another state.

Do you have an Adelaide team?

No. Yes AI is a Melbourne business. There is no Adelaide office, no Adelaide staff, and nobody who will attend your practice for an assessment or training, Adelaide practices are served remotely from Melbourne. We are saying it here rather than in a footnote, because a page ranking for "healthcare AI Adelaide" that implies a local implementation team is making a promise it cannot keep, and the practice that repeats a vendor's claim is the one with its name on the door. The setup work (configuration, integration, training) is done on video, which is genuinely where that work lives. If you need someone physically in the building, hire an Adelaide provider and we will say so.

Is the time difference a problem?

No, and we are not going to inflate it into a talking point the way this page could. Adelaide runs on Australian Central Standard Time, thirty minutes behind Melbourne, and because South Australia observes daylight saving alongside Victoria the gap stays at thirty minutes all year. That is not a timezone problem, it is a rounding error. Your 9am is our 9.30am. Nobody has to take an early start, no overlap window needs rationing, and no support hours quietly shrink in summer. If we were serving you from Perth this section would be the most important one on the page. From Melbourne it is a footnote, and pretending otherwise would just be a different kind of dishonesty.

Does South Australia have a privacy Act?

No, and this genuinely surprises people, including people who work in SA health. South Australia is the only mainland state without dedicated privacy legislation. The SA public sector instead operates under an administrative instrument: Premier and Cabinet Circular PC012, which sets out Information Privacy Principles that bind SA government agencies as a matter of government policy rather than statute. So there is no SA equivalent of the NSW HRIP Act or the Queensland Information Privacy Act to point at. For a private Adelaide practice, the federal Privacy Act 1988 (Cth) and the Australian Privacy Principles do essentially all the work, and health information is sensitive information under that Act. The most protected category it has. Where PC012 becomes your problem is when you contract to SA Health or another SA agency: the obligations then reach you through the contract and the circular rather than through a statute you could have looked up. General information, not legal advice.

If the obligations sit in contract, what does that change practically?

It changes where you have to look, and it makes the contract the document that matters rather than a formality your practice manager signs. When a state has a health privacy Act, the floor is set by legislation and you can read it. In South Australia, for SA Health-adjacent work, the substantive requirements arrive through the agreement, data handling terms, security expectations, breach notification, what happens on termination, whether anything may be disclosed offshore. Two SA contracts can therefore impose materially different obligations on the same practice for the same system, which is exactly the situation where a vendor saying "we are compliant" is saying nothing at all. Compliant with what? We would rather read the contract with you and map what it actually requires than issue a compliance statement into the void.

Can the AI triage patients or discuss symptoms?

No. AI belongs around care, never inside it. It books, reschedules, reminds, recalls, captures an intake form, and routes a callback to a human. It does not triage symptoms, does not interpret results, does not tell a patient whether something is urgent, and does not offer reassurance that reads as clinical advice. Every clinical determination is made by a registered practitioner. The failure mode we design against is precise: an unwell patient gets a confident-sounding answer from a machine and does not call the practice. If a vendor is selling you AI triage, ask them who holds the registration when it is wrong.

Why does AHPRA advertising law constrain an appointment reminder?

Because AHPRA's advertising guidelines, made under the Health Practitioner Regulation National Law, prohibit using testimonials in advertising a regulated health service, and a language model does not know that. Ask a general-purpose model to write a warm recall message and it will produce "our patients love their results" unless the system stops it. That sentence is an advertising breach attached to your practitioner's registration, not the vendor's. It is a real design constraint, enforced in what the model is instructed to do and in what a human reviews before anything goes out, and most AI vendors selling into healthcare have never heard of it. General information, not legal advice.

What does it cost, and what will you not claim?

Plans start at $499 per month for a single-practitioner practice, with multi-practitioner and multi-location pricing above that. What we will not publish is a return-on-investment figure or a no-show reduction percentage for an Adelaide practice. We have no measured outcome data for your practice or your patient mix, and an invented efficacy number about a health service is the kind of claim that damages whoever repeats it. Build the number from your own data in the free assessment. If the case is thin, we would rather tell you than sell you something.

Thirty Minutes Away. Ask Us the Hard Question.

One free assessment, on video, essentially in your business hours. You will get a direct read on whether there is anything here worth doing for your practice, including, sometimes, that there is not.

Book a Free AssessmentView Healthcare Plans

Sources and further reading