A healthcare app is not an ordinary app with a privacy policy added at the end. The rules that apply depend on what the app does with health information, who it connects to, and whether it makes or supports decisions about care. Those answers change the scope in discovery long before they change the invoice.
This guide covers five areas that commonly shape a healthcare build in Australia: the Privacy Act and the Australian Privacy Principles, connecting to My Health Record, the Therapeutic Goods Administration’s rules for software, clinical data standards such as FHIR, and the automated decision-making transparency rules that start on 10 December 2026. It draws on three products our Sydney app developers have worked on: Clinic 1, HealthMate and AI Medic.
We are software developers, not lawyers. Treat this as general information, and confirm anything specific to your app with a privacy lawyer, and with the Australian Digital Health Agency (ADHA) or the TGA where national systems or a medical device question is involved. If you are still deciding what to build, product planning is where these questions get answered first, and our healthcare app development page shows the kinds of products we build.
In short
- Which rules apply depends on what your app does and what it connects to, so map them before you ask for a quote.
- Health information is sensitive information under the Privacy Act. From 10 December 2026, privacy policies must also describe certain uses of automated programs.
- Connecting to My Health Record has its own registration, testing and conformance steps set by ADHA.
- A symptom checker, triage or risk score may be regulated by the TGA as a medical device, depending on its intended use.
Which Australian rules affect a healthcare app build?
| Area | Applies when | Who to ask |
|---|---|---|
| Privacy Act 1988 and the Australian Privacy Principles | You collect or hold health information | A privacy lawyer; the OAIC |
| Automated decision-making transparency (APP 1.7 to 1.9) | A program makes, or substantially helps make, a decision that could significantly affect someone, using personal information. From 10 December 2026 | A privacy lawyer; OAIC guidance |
| My Health Record connection | Your app reads from or writes to My Health Record | ADHA |
| TGA rules for software | Your software is intended to diagnose, screen, monitor or recommend treatment | The TGA or a regulatory adviser |
| Clinical data standards (FHIR and others) | You exchange clinical data with other systems | Each system’s vendor |
The five areas that commonly shape a healthcare app build in Australia (checked October 2026)
HIPAA, the United States health privacy law, is the framework many overseas guides start from. It is not the main framework for an Australian app, which is why a quote built on a HIPAA checklist can miss the layers above.
What does the Privacy Act require for health information in an app?
Health information is sensitive information, so the Privacy Act sets a higher bar for collecting it. APP 3.3 requires consent to collect sensitive information unless an exception applies, such as certain permitted health situations. The OAIC says consent can be express or implied, but that you should generally seek express consent because of the greater privacy impact.
Two more principles shape the build:
- Security. APP 11 requires reasonable steps to protect personal information from misuse, interference and loss. What is reasonable scales with how sensitive the information is and how much harm a breach could cause, so health data sits at the demanding end.
- Retention. APP 11 also requires reasonable steps to destroy or de-identify information you no longer need, which affects how long the app keeps records.
The Notifiable Data Breaches scheme is a separate set of rules about what to do after an eligible breach. The OAIC explains it.
In practice this turns into design work. Consent screens that ask for each purpose separately, a clear record of what a person agreed to and when, and a retention rule for every data type are decisions made in UX and UI design, not only in the privacy policy. Our Privacy Act 2026 guide covers the wider changes for app builders.
What changes on 10 December 2026 for apps that use automated decisions?
According to law firm Allens’ summary of the OAIC’s final guidance, released on 30 September 2026, the policy must describe the kinds of personal information used, the kinds of decisions made solely by the program, and the kinds of decisions where the program does a related step. The same summary says this is a transparency rule only. It does not require human review, and it does not give people a new right to challenge a decision. Advisory output can still count.
The obligation sits with the organisation using the tool, not with the developer who built it. For a developer, that means giving clients a plain description of what each feature does with data, so their lawyer can write the policy wording.
Health is one of the interests the OAIC lists, so many clinical features are worth classifying. Likely is not the same as certain. Each feature needs its own assessment.
| Feature | Question to ask |
|---|---|
| Symptom checker or triage | Does its output decide, or strongly shape, how urgently someone is seen? |
| Practitioner or service matching | Does the match change who gets access to care? |
| Risk scores and scoring tools | Does a score decide or shape a care pathway? |
| Scheduling or queue prioritisation | Does it change waiting times for some people and not others? |
| Medication or interaction checks | Is a person expected to act on the result without independent review? |
| AI generated notes or summaries | Do they feed a later decision about the patient? |
Features worth classifying before 10 December 2026
If your app is already live, the same logic applies to your existing privacy policy. A practical order of work is to list every feature that uses health data to make or assist a decision, classify each one, have your privacy lawyer settle the policy wording, and check the published policy before 10 December. Adding in-app explanations or a way to ask for human review is good practice, not a requirement of these rules, so treat it as a product decision.
What does connecting to My Health Record involve?
Four points are worth planning for:
- Consent and presentation rules. ADHA publishes guidelines covering operations, consent, security and app presentation. Mandatory requirements are written as “shall” and “shall not”.
- Production access can be deferred. ADHA says the System Operator may defer or reject production access if the app’s design does not meet the requirements.
- Security conformance. ADHA’s page on its Security Conformance Profile says existing software must reach conformance within 12 months from 23 February 2026, and new software must show conformance before it is granted production access.
- Where records are held. The My Health Records Act 2012 includes a section headed “Requirement not to hold or take records outside Australia”. Whether it binds your app depends on your role, so confirm it with ADHA and your lawyer before choosing hosting.
ADHA does not publish a fixed timeframe for the steps above, so start early and ask ADHA how long each stage is taking. A connection also touches your systems integration plan, because test environments and sign-offs sit outside your own team.
Does your app count as a medical device?
That makes any symptom checker, triage or risk scoring feature a question for the TGA or a regulatory adviser before design is locked. The wording of your app store listing, your marketing and your in-app text all form part of the intended use, so they matter as much as the code. The rules changed in 2021, so check the TGA’s current guidance rather than older articles. Our AI development work follows the same order: decide what the feature is for, then build it.
Do you need FHIR or another clinical data standard?
You need FHIR if you exchange clinical data with systems that use it, and the My Health Record FHIR gateway is one example. FHIR is an international standard for exchanging health data. HL7 Australia publishes AU Core, an implementation guide with the minimum expectations for FHIR resources in an Australian context, which is why a build based only on United States profiles can miss local requirements.
Many clinical systems have their own integration routes, and not all of them use FHIR. The practical step is to list every system your app must talk to, then ask each vendor which interface it supports, what access it requires, and what testing it expects. The answers set the integration scope far more than the standard does.
What drives the scope and cost of a healthcare app?
Healthcare scope is driven by what the app collects, what it connects to, and what its features decide. The rules above add work in discovery, design, build and testing, and some of that work sits with lawyers and regulators outside the development team. Because the drivers differ so much between products, we scope them first and quote a fixed price after discovery.
| Driver | Why it changes the work |
|---|---|
| Collecting health information | Consent design, retention rules, security review |
| Connecting to My Health Record | ADHA registration, testing, conformance and demonstration steps |
| Features that support clinical decisions | TGA question, privacy policy disclosure, clinician override design |
| Number of systems you exchange data with | Integration build and test environments for each |
| Platforms (iOS, Android, web) | Build and device testing |
| Payments and claiming | Provider integration and reconciliation |
| Reviews by lawyers and regulators | Elapsed time outside the development team |
What changes scope in a healthcare app build
Our planning phase is priced at AUD 5,000 to 30,000 over one to four weeks, and it is where these drivers get mapped. For build timelines, our app development timelines guide treats compliance work as adding roughly two to four weeks to a typical build, and connections to national systems need to be scoped separately. See the true cost of building an app in Australia for what quotes often leave out, and fixed price versus time and materials for how the contract shape affects risk.
What did Clinic 1, HealthMate and AI Medic involve?
These are the three healthcare products on our case study page. The descriptions below come from those pages, and each section notes what the project meant for scope.
Clinic 1: practice management for allied health clinics
Clinic 1 is an AI-powered practice management platform for allied health clinics, built for web, iOS and Android. It covers AI clinical documentation (transcription, note generation and treatment-plan automation), scheduling, patient workflows, invoicing and reporting, and it integrates with My Health Record and Medicare services. Our React Native and Node.js team built it on AWS. For scope, the My Health Record and Medicare connections set an integration workload from day one, and AI generated notes raise the classification question described above.
HealthMate: a telehealth platform
HealthMate connects Australians with GPs, specialists, nurses, physiotherapists and dietitians through video consultations, home and clinic visits, and wearable monitoring. It checks practitioner credentials against the Australian Medical Council and AHPRA, uses Tyro Health for invoicing, payments and healthcare claiming, and Stripe for card payments, and it integrates with My Health Record. For scope, credential checks, claiming and payments are each separate integrations with their own testing.
AI Medic: telemedicine with an AI symptom checker
AI Medic is a web application and admin panel for video consultations, with an AI symptom checker designed by doctors, appointment booking, e-prescriptions, consultation notes and Stripe payments. It uses role-based access and multi-factor authentication. For scope, a symptom checker is the feature that raises both the TGA question and the automated decision-making question, so those need an answer before design is final.
H2: How can you tell if a developer has healthcare experience?
Ask for specifics, because a studio meeting these rules for the first time will find them on your budget and timeline. Five questions separate experienced teams from general ones:
- Which of these five areas applied to your last healthcare build, and how did you scope each?
- Have you connected an app to My Health Record, and who handled the ADHA registration and testing steps?
- How do you decide whether a feature may be regulated by the TGA, and who do you ask?
- How do you classify features for the automated decision-making disclosure, and what do you hand to our lawyer?
- Can I see the App Store privacy details for a health app you have shipped?
For the wider checklist, see our 10 questions to ask a Sydney app developer and our guide to finding a trustworthy app developer in Australia. Testing is part of the answer too: our software testing covers consent flows, security checks and behaviour across devices, although it cannot certify that you meet the Privacy Act.
Healthcare app development in Sydney: frequently asked questions
Does HIPAA apply to an Australian healthcare app?
Not as the main framework. HIPAA is a United States law. Australian apps are shaped by the Privacy Act and the other areas in this guide. If you serve patients in the United States, get separate advice on the rules there.
What does the Privacy Act require for health information in an app?
Health information is sensitive information. You need consent to collect it unless an exception applies, you must take reasonable steps to keep it secure, and you must take reasonable steps to destroy or de-identify it when you no longer need it. The OAIC advises seeking express consent where you can.
What changes on 10 December 2026?
Privacy policies of organisations covered by the Act must describe certain uses of automated programs that make, or substantially help make, decisions that could significantly affect people. Many clinical features are worth classifying. Your privacy lawyer should confirm the wording.
Does my app need to connect to My Health Record?
Only if it reads from or writes to that record. If it does, ADHA’s process applies: test environment access, registration, testing, a self-assessment and a demonstration, plus security conformance.
Is my symptom checker or triage feature a medical device?
It depends on its intended use and the risk involved. Software meant to diagnose, screen or recommend treatment may be regulated by the TGA. Ask the TGA or a regulatory adviser to classify it before design is locked.
Do I need FHIR?
Only if you exchange clinical data with systems that use it. List the systems you must connect to and ask each vendor which interface it supports. The My Health Record gateway for mobile apps uses FHIR.
Does health data have to be stored in Australia?
The My Health Records Act restricts holding My Health Record data outside Australia, and whether that binds your app depends on your role. For other health data, disclosure of personal information overseas has its own rule under APP 8. Confirm hosting decisions with your lawyer.
How much does a healthcare app cost in Sydney?
It depends on the drivers in the table above, so we scope first and quote a fixed price after discovery. Our planning phase costs AUD 5,000 to 30,000 and takes one to four weeks. Talk to our team about your product.
Planning a healthcare app?
Bring your feature list and the systems you need to connect to. We will map which of these areas apply before you commit to a build quote. See our healthcare app development page, start with product planning, or get in touch.