AI for the medical industry
If you work in healthcare and enter patient information into Claude, processing may happen overseas. Without the required safeguards, that could put your organisation in breach of Australian privacy law.
Keep your AI processing in Australia with MedAI AU. We configure an approved Claude setup with AI processing restricted to Sydney or Melbourne.
For information sent to Claude’s AI through your approved setup. Storage and connected services are assessed separately.
AUFor organisations across the medical industry that require Australian-only AI processing.
Recognise what you are sharing
If you put information identifying a patient into Claude, where is it processed?
You can use Claude’s official website or app from Australia and still have information processed overseas. Being here does not mean the processing stays here.
For commercial services such as Claude Enterprise and its API, Anthropic says default traffic may be routed to the US, Europe, Asia and Australia, unless a different arrangement or routing instruction applies.
Controls vary by product and agreement. Check the terms and configuration of the service your team actually uses.
Read Anthropic’s processing guidanceFor personal Claude plans, Anthropic’s privacy policy provides for international transfers. Installing the official app or using an Australian account does not, by itself, establish Australian-only processing.
If your organisation needs that restriction, it needs to be part of the approved setup.
Read Anthropic’s privacy policyWhy this matters for health information
Your organisation remains responsible for how it uses and discloses patient information. The OAIC explains that overseas disclosure generally requires reasonable steps to protect that information under the Australian Privacy Principles. You may also remain accountable if the overseas recipient mishandles it. Exceptions apply.
Where your organisation requires Claude’s AI processing to stay in Australia, MedAI AU addresses that requirement through configuration, restrictions on overseas processing and ongoing checks. Other privacy responsibilities still apply; Australian law does not impose a blanket ban on every overseas disclosure.
OAIC: using or disclosing health informationSource guidance checked 8 September 2026. Requirements depend on your organisation, information and circumstances.
Check your current setup
Start with what your team shares, what has been approved and where it is processed.
This is a requirements check, not a compliance assessment. Your answers stay on this page.
Select an answer to each question to see your next step.
Discuss your Claude setupHow MedAI AU addresses it
We configure the supported Claude setup, test the restrictions and explain what your team can use. Claude Desktop connects to a dedicated environment your organisation owns, with approved AI processing restricted to Sydney or Melbourne and overseas routes blocked.
We review how your team uses Claude, the features you need and your Australian-processing requirement. You receive a clear scope and price before committing.
We explain which features and connections the setup can support.We prepare the dedicated environment and Claude settings. Your administrator approves access and installs the settings using our illustrated guide.
Your organisation keeps account ownership, billing and staff access decisions.We test the agreed functions and processing controls in your environment before go-live, using synthetic information.
Ongoing checks and reporting start once the setup is in use.The restriction covers where Claude’s AI processes information through the approved setup. It does not automatically cover storage, backups, web search or other connected services. We identify those boundaries and agree the supported features before you commit.
Ongoing management
We maintain the agreed Australian-processing controls and review changes that could affect your setup. Your proposal sets out the checks, reporting and support included, how often they happen and how issues are handled.
Clear responsibilities
The dedicated environment, Australian-only AI processing settings, administrator guide and checks before go-live.
Account ownership, vendor billing and approval of the permissions your staff need.
The checks, reporting, investigation of exceptions and updates agreed in your management scope.
Your administrator grants access, installs the approved settings and manages joiners, leavers and everyday IT support.
Your account and data remain yours when our service ends. We hand over the agreed configuration and records, then remove our management access. You can keep the environment and arrange its future management under the agreed exit terms.
Claude’s AI processes the information submitted through your approved Claude Desktop setup only in Sydney or Melbourne. Storage, backups, Microsoft 365, other connections and use of other AI apps have their own data-handling arrangements. We make that boundary clear in your scope.
It addresses the specific requirement for Claude’s AI processing to remain in Australia through the approved setup. It does not establish compliance with every obligation. Your organisation remains responsible for appropriate use, consent where required, access, retention and its broader privacy and clinical governance arrangements.
Only for uses your organisation has assessed and authorised. The processing controls do not replace decisions about consent, purpose, access or accuracy. We use synthetic information for implementation tests. AI outputs still need appropriate human review.
Yes, through Claude Desktop connected to your dedicated environment. We agree and test the chat, file and other functions your team needs. This is a configured setup: existing history, web and mobile access, and every subscription feature do not automatically carry over. We explain the differences before you decide.
We prepare the configuration and illustrated instructions. Your administrator handles Microsoft consent, staff identity, group membership and deployment to managed devices. Routine walkthrough meetings are not required; setup details and exceptions can be handled in writing. The exact steps depend on your environment.
The setup fee covers your agreed shared environment, with a separate fee for ongoing management. Adding staff to existing approved profiles does not, by itself, add another setup or management fee. Cloud usage and vendor charges remain separate and are billed to your organisation. Additional environments or substantial changes are quoted first. Your proposal sets out the scope, fees and payment terms.
We notify your nominated contact and investigate the controls within our scope. If a processing route is suspect, we can restrict the affected access while investigating. We do not switch processing overseas to keep the service running. Any device or Microsoft actions are given to your administrator in writing. Your agreement sets out response arrangements; this is not a 24-hour helpdesk.
They may be able to. Our service provides the implementation and ongoing responsibility for the agreed processing controls, checks and reports. Your IT provider continues managing your staff, devices and Microsoft environment.
We review relevant releases and introduce approved changes after verification. New features requiring extra permissions may need your administrator’s approval. You retain account ownership throughout. Your agreement sets out notice, handover and removal of our management access at the end of the service.
Tell us what you need
Tell us how your team uses Claude. We’ll explain whether our Australian-processing setup fits, what it covers and what it would cost. Please do not send patient information.
Enquiry sent
We’ll reply to to discuss your requirements and the next steps.
We use analytics cookies to understand how our website is used. We don’t send your form details to Google. Privacy notice
