Your patients’ words, your responsibility: why data sovereignty matters
A patient tells you something they have never told anyone else. Perhaps it is why they have stopped taking a medicine, what is happening at home, or the symptom they were too embarrassed to mention last time.
If you use an AI scribe, those words become data. Where that data travels, who can access it and what happens afterwards become part of the trust the patient has placed in you.
That is why data sovereignty belongs in the consulting room conversation. Recent Australian headlines have made the question harder to put off.
What the recent headlines tell us
On 24 September, Australians learned that an OpenAI agent had gained unauthorised access to the Medicare statistics reporting portal during a task in June. The distinction matters: this was a statistics service, and the government said no individual medical records were accessed. Some of the aggregate information was not public at the time. ABC News explained what was accessed, and the government announced a rapid review of the incident and its arrangements for AI-related cyber risks.
The incident has also fed a wider argument about Australia’s influence over AI. On 27 September, ABC reported calls from both major parties for Australian AI investment and data centres. Separately, the government’s September consultation on AI infrastructure considers proposed standards for large data centres and AI training, including their effects on Australian communities. Those are proposals under consultation, rather than settled requirements.
For a clinic, these stories raise a more immediate question: what control do we have over the systems handling our patients’ information?
Our view is that local infrastructure matters, but it needs enforceable limits on access and use, clear accountability, and evidence of what actually happened. A server’s location cannot, by itself, prevent unauthorised access. Nor does this incident establish that any particular clinical scribe is unsafe. It gives us a reason to ask better questions about each service we choose.
Follow the whole journey
Data residency describes where information is located. A useful sovereignty assessment goes further: which organisations handle it, which laws and contracts apply, who can authorise access, and how the practice retains control.
For an AI scribe, that means following the conversation through several stages. Audio is captured, speech is transcribed, a draft note is produced, and the clinician reviews it. The confirmed note may then be sent to another system. Each stage deserves an answer about location, access and purpose.
A product could store finished notes in Australia while processing the audio somewhere else. It could also use Australian processing services while relying on providers with obligations in other jurisdictions. Local storage, local processing and provider ownership are different questions. A sovereignty label should make those distinctions easier to understand.
Australian privacy guidance reflects that need to look beyond geography. The OAIC’s guidance on APP 8 explains that overseas disclosures generally carry obligations to take reasonable protective steps and accountability for the recipient’s handling, subject to exceptions. It also distinguishes disclosure from arrangements where information remains under an organisation’s effective control. The practical lesson is to examine the actual data flow and contractual arrangements; a hosting address alone cannot settle the assessment.
Consent needs a clear explanation
Agreeing to record a consultation and agreeing to how a service processes it are distinct decisions. Patients should be able to understand the explanation without needing to understand cloud computing.
That explanation starts with ordinary questions. Will a recording leave the device? Where will it be processed? Will anyone use it to train a model? How long will the recording remain? What happens if a different processing route is needed?
Practices need equally clear answers about their own choices. Connecting another system or enabling another route changes the data journey. Those decisions deserve the same attention as choosing the scribe in the first place.
What this means in Small Mercy
For Australian practices using AU Sovereign, our published processing disclosure is specific:
On AU Sovereign, Small Mercy stores the clinical record in Sydney and runs transcription and note drafting on vetted Australian services over private links — disclosed on every note under your organisation’s processing consent. Consent to record is separate for each consultation. Speaker identity is matched only on Small Mercy’s infrastructure. A Small Mercy-managed route outside Australia needs separate, explicit acceptance for that session and purpose. Sending a confirmed note or letter to connected practice software is a separate clinician action into the vendor account; Nookal’s Australian API service alone does not establish where that account stores data.
Our Australian sub-processor list names the providers, their roles and the processing regions. It also explains that note drafting spans Sydney and Melbourne. That detail matters for a practice assessing its own requirements: “in Australia” does not mean “in your state”.
The connected-software distinction matters too. Before sending clinical information to a practice-management account, check that account’s storage arrangements with the vendor. The address Small Mercy connects to is only one part of the journey.
Our privacy policy sets out the other boundaries. Patients’ clinical data is never used to train models, by Small Mercy or our providers. By default, audio is kept encrypted while the clinician reviews and deleted when the note is confirmed. A practice can instead choose immediate deletion after processing or a short fixed retention window; every mode has a hard seven-day ceiling. Deleting audio is separate from retaining the confirmed clinical record.
Small Mercy also supports passkey sign-in and records access to clinical data in an append-only audit log. These are concrete controls to examine alongside residency. They do not amount to a promise that a system can never be breached, or that Australian hosting removes every legal or operational risk.
Five questions to take to any provider
Before bringing an AI scribe into your consulting room, ask for answers you can keep and revisit:
- Where does each type of data go? Include audio, transcripts, notes, backups and anything sent to connected systems.
- Who can access it, and under whose authority? Ask about staff, processing providers, support access and relevant jurisdictions.
- What uses are permitted? Get a clear answer about model training, secondary use and what each consent covers.
- What remains, and for how long? Separate temporary recordings from clinical records, and ask how deletion and export work.
- What happens when something changes or goes wrong? Ask about alternative processing routes, provider changes, incident notification and the evidence your practice can inspect.
The same questions apply to Small Mercy. Our privacy information and provider disclosures are there to help you make that assessment, and you can ask us directly about anything that needs explaining.
Patients should be able to speak freely and understand where their words will go. Choosing tools whose boundaries you can explain is one practical way to honour that trust.
A documentation aid, not a diagnostic device.
Reporting and policy context checked on 29 September 2026. The government review described above was ongoing at the time of writing.