An Australian healthcare company can build its mobile app with an offshore team and still keep patient data in Australia. To do it, separate two things most contracts blur: where data is stored and who can see it. Production systems, backups and logs stay in an Australian cloud region. Offshore engineers work only with source code and synthetic test data.
Production access stays with named people in Australia. 724SOFTWARE is a Vietnam software team that delivers mobile apps and works compliant with ISO 27001:2022. Every healthcare build has to settle what crosses the border, so that boundary belongs in the plan before the first sprint rather than after a security review flags it.
TL;DR
Data residency covers storage. Data access covers people. You need rules for both.
My Health Record data and backups must stay in Australia. Other health information falls under the Privacy Act 1988 and the 13 Australian Privacy Principles.
Offshore engineers can build and test a complete app on synthetic data without seeing a real patient record.
Side channels are easy to miss: crash reports, logs, analytics, support screenshots and AI prompts.
Healthcare app development cost depends on compliance and operations scope as much as on features.
About the Author: This guide comes from the delivery team at 724SOFTWARE. We are a Vietnam-based engineering company of 200+ professionals (58% senior-level), Digital Healthcare is one of our core domains, and we have delivery experience across 10+ countries.
What does "not sending patient data offshore" actually mean?
The central idea here, separating storage from access, starts with a definition. Keeping patient data onshore means no identifiable health information is stored, processed, copied or viewed outside Australia. That includes viewing by your own development team. Storage is the easy part. The harder part is the set of paths through which data leaves the main database without anyone deciding it should.
Data path | Typical offshore exposure | Onshore control
|
|---|---|---|
Backups and replicas | Default multi-region replication | Pin backups to the Australian region |
Application logs | Request bodies logged with patient fields | Redact fields before logging |
Crash reports and analytics | Third-party SDKs hosted overseas | Strip identifiers, or self-host in Australia |
Test data | Production copy "for realism" | Generated synthetic records |
Support tickets | Screenshots of patient screens | Masked UI in support builds |
Our opinion: treat offshore read access to production as a transfer, even when nothing is downloaded. A single rule like that is easier to audit than case-by-case judgement.
Which Australian laws decide where health data can go?
This distinction matters because Australian law treats categories of health data differently. Legal research belongs before feature design, because apps must comply with the privacy laws of the region they operate in.
What is already law:
Privacy Act health information: The Privacy Act 1988 governs health information. It allows overseas disclosure if the provider takes reasonable steps to ensure the recipient does not breach the APPs, and the provider generally remains accountable for how the recipient handles the information.
APP 11: The 13 Australian Privacy Principles apps must follow include APP 11. It requires reasonable steps to protect personal information from unauthorised access or loss. Health service providers are not exempt under the small business rule.
Notifiable Data Breaches scheme: Organisations must take reasonable steps to assess a suspected breach promptly. Once an eligible breach is confirmed, they must notify the OAIC and affected individuals as soon as practicable.
TGA: Apps intended to diagnose, prevent, monitor or treat a disease are regulated as Software as a Medical Device and generally need inclusion in the Australian Register of Therapeutic Goods unless an exemption applies. General wellness apps are excluded.
How do you build the app so offshore engineers never touch patient data?
Given those rules, the cleanest design puts the offshore team firmly on the code side of the line. Consider how a locksmith works. Every lock is designed and tested on a practice door in the workshop. It works on your house because the mechanism is identical, and the locksmith never needed your keys. Code behaves the same way on synthetic records as on real ones, so engineers can build and test it fully without seeing the real thing.
Host in an Australian region. Pin production, backups, logs and object storage to Australia, with cross-region replication disabled.
Separate environments by data. Dev and staging hold only synthetic records generated from your schema.
Ship through a pipeline. Offshore engineers merge code and CI/CD deploys it. Nobody needs a production console to release.
Keep production credentials onshore. Named Australian staff hold them, and any emergency access is logged.
Redact on the device. Logging and crash-reporting libraries strip patient fields before anything is sent.
Write AI tool rules. Coding assistants such as Claude Code work on code and synthetic data only. Real records never appear in prompts.
Where do these setups usually fail?
Even with that architecture in place, failures usually come from deadline shortcuts rather than from the design itself. Watch for:
A production snapshot copied into staging "just once" to reproduce a bug
Analytics or crash SDKs that ship enabled by default in a mobile template
Patient screenshots pasted into tickets or chat
Backup policies that quietly default to a second region
Rotating contractors, so nobody remembers the rules
The last point is why team stability matters as much as tooling. A rule set is only as reliable as the engineers who learned it in month one and are still on the team in month eighteen.
What drives healthcare app development cost in this model?
Building on that, healthcare app development cost depends as much on the compliance and operational work around the features as on screen count. An app that supports remote care, clinical workflows and data exchange, carries different obligations from a wellness tracker. Scope these categories:
Feature build (web and mobile)
Synthetic data generation and test environments
Australian hosting, backups and monitoring
Security and penetration testing
Privacy impact assessment and legal review
TGA work, if the app is a medical device
Ongoing operation, patching and incident response
An offshore team mostly changes the cost of the build, test environments and ongoing engineering. Australian hosting and legal review stay onshore. That is where the cost efficiency argument holds up honestly.
How should you evaluate an offshore team for healthcare mobile app development?
With the cost structure clear, the selection question becomes whether a vendor can work inside your data rules for years, well beyond the first security review. Ask for:
Named standards and the evidence behind them
Permanent employees in a real office, not a freelancer pool
Working-hours overlap with Australian business days and a stated incident response time
Billing based on actual hours, with visibility into team performance
A written policy on AI tool use
724SOFTWARE's answers to these questions are a Follow-the-Sun model with under-10-minute incident response and billing based on actual working hours. Our dedicated teams scale from 1 to 50+ pre-vetted engineers in 2-4 weeks.
Frequently Asked Questions
Can an offshore team build a healthcare app for Australia?
Yes, provided production data stays in Australia and offshore engineers work only with code and synthetic data.
Does the Privacy Act ban overseas storage of health information?
No. It allows overseas transfers if the provider ensures the recipient does not breach the APPs. My Health Record data is different: it must stay in Australia.
Does every health app need TGA inclusion?
No. Only apps intended to diagnose, prevent, monitor or treat a disease are regulated as medical devices.
Are small health businesses exempt from the APPs?
No. Health service providers are not exempt under the small business rule.
Can developers use AI coding tools on a healthcare app?
Yes, on code and synthetic data. Keep real patient records out of prompts entirely.
About 724SOFTWARE
724SOFTWARE is an offshore IT company in Vietnam with 200+ professionals, 58% of them senior-level. We deliver web and mobile applications through dedicated teams and embedded staff augmentation, and Digital Healthcare is one of our core domains. We are a selected Anthropic partner in Vietnam and train our engineers to use Claude Code in daily delivery. We are compliant with ISO 27001:2022 and ISO 9001 standards, are GDPR compliant, and hold a 95% client retention rate.
If you are planning a healthcare app and want to map which data stays onshore before the first sprint, talk to our team at https://724software.com.vn/.
