Healthcare Eligible Data Breach Assessments: Use case and AI Confidentiality
A results email goes to the wrong person and the practice manager has to decide whether it is an eligible data breach under the Privacy Act. A medical practice that holds patient health information is covered by the notifiable data breaches scheme whatever its turnover. The manager writes an assessment that names the patient, describes the result that was disclosed, counts the 30 days and weighs the harm, then pastes it into ChatGPT or Claude to sharpen the reasoning. That puts a second disclosure of the same patient’s information on top of the first. This page marks every item in a routine assessment record and shows how the same record is drafted on Ermos inside the practice.
The eligible data breach assessment
Opened by the practice manager as soon as the practice is aware of reasonable grounds to suspect an eligible data breach, kept up to date during the assessment and closed with a decision on whether to notify.
Kestrel Lane Medical Practice
Suspected eligible data breach: assessment record · Ref KLMP-PRIV-2026-003 · Opened Wednesday 4 November 2026 · Updated Monday 9 November 2026
What happened. On Tuesday 3 November 2026 at 4.55pm a results email for Mr Barry Dunstan (DOB 2 May 1964) was sent to Ms Cecilia Dray, another patient, because the email program completed her address when the receptionist typed the first letters of the surname.1
What was disclosed. A pathology report attached as an ordinary PDF with no password: liver function tests, hepatitis B surface antigen positive and HbA1c 8.2%, with a line asking him to book a review with Dr Eze.2
How it came to light. Ms Dray rang Bec Marlow at 9.05am on Wednesday 4 November. She said she opened the attachment, saw it was someone else’s, and closed it. She has deleted the email, emptied her deleted items and confirmed in writing on 5 November that she has not forwarded or kept it.3
Awareness and deadline. The practice became aware of the event at 9.05am on 4 November 2026. The assessment is to be completed within 30 days, by Friday 4 December 2026.4
Steps taken. Bec Marlow took the call, asked Ms Dray to delete and confirm in writing, and logged the event. Carrow IT Services removed external auto-complete on all reception accounts on 5 November and confirmed that no copy remained on the mail server of the practice.5
Likelihood of serious harm. Kind of information: health information, including a positive hepatitis B result. Sensitivity: high. Protection: none on the file. Who has it: one patient known to the practice, no known link to Mr Dunstan or his employer, who deleted it and confirmed in writing. Nature of harm if it spread: embarrassment and discrimination at work or in insurance.6
Interim view (9 November). The disclosure was unauthorised. Because the recipient deleted it before it spread and confirmed in writing, a reasonable person may conclude that serious harm is not likely and that the remedial action means this is not an eligible data breach. Helen Tran and Dr Voss to decide by Friday 13 November.7
Telling the patient. Dr Eze rang Mr Dunstan on Thursday 5 November, apologised and explained what happened. Mr Dunstan was angry and has asked for a written account. He has not said he will complain.8
If the decision is to notify. Prepare a statement with the practice’s identity and contact details, a description of the breach, the kinds of information involved and recommendations for Mr Dunstan, give a copy to the Information Commissioner as soon as practicable and notify Mr Dunstan.9
Fixes. Password-protect every attachment sent outside the practice from 16 November. Retrain reception on checking the full address. Put the event on the agenda for the 17 November team meeting. Prepared by Helen Tran, Practice Manager.10
An invented assessment. The patient, the recipient and the IT contractor are fictional. Hover or tap any highlighted item for the analysis; the full list is below.
Breach assessment record organiser
An Agent+ that helps keep an eligible data breach assessment in order. It builds a timeline from the incident notes, emails and the practice's own response plan, lists what is known and unknown, and flags the questions still open. It drafts updates to the assessment record as facts come in.
What it does
- Reads the incident notes, emails and response plan
- Builds a dated timeline of what is known
- Lists open questions and facts still unconfirmed
What stays with your people. The practice manager, with the principal, decides whether the breach is eligible and whether to notify. The agent organises the record; it does not decide.
An Agent+ is built once and anyone in the practice can run it. It works from your own documents and runs on Ermos Dominion, the AI unit in your office, or on Ermos Edge, your own instance in an Australian data centre.
What leaves the practice
- 1The event and two patients
Names the affected patient with his date of birth, the person who received the email and what caused the mistake. Information about a person’s health is sensitive information, and the recipient’s name is personal information about someone who did nothing wrong. A practice that provides a health service and holds health information is not a small business operator (Privacy Act s 6D(4)(b)), so the Act covers it whatever its turnover. Privacy Act guide.
Frontier Models (ChatGPT, Claude) Two patients’ names and a health service’s mistake transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 2The result that was disclosed
A laboratory result with a hepatitis B finding against a named patient. It is health information under s 6FA and sensitive information under s 6(1). Repeating it in the assessment record, and then in an outside tool, discloses it again. Patient data guide.
Frontier Models (ChatGPT, Claude) Sensitive health information transmitted; on consumer tiers it can train future models Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 3The recipient’s account
What the recipient said she did and her written confirmation. It is the evidence the practice relies on, written by a patient of the practice who is not the person affected.
Frontier Models (ChatGPT, Claude) A patient’s account of what she did with another patient’s result transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 4The awareness date and the 30 days
Section 26WH(2) of the Privacy Act requires an entity that is aware of reasonable grounds to suspect an eligible data breach to carry out a reasonable and expeditious assessment and to take all reasonable steps to complete it within 30 days after becoming aware. The rule is public. The date ties it to this event. Privacy Act guide.
Frontier Models (ChatGPT, Claude) The 30 day rule is public; the date ties it to this event Ermos Edge Stays on your instance, but the practice must still count the days and check the deadline itself Ermos Dominion Stays on the unit, but the practice must still count the days and check the deadline itself Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 5Steps taken and a named contractor
Records the containment steps and the IT contractor that carried them out. APP 11.1 requires an entity that holds personal information to take reasonable steps to protect it from unauthorised access or disclosure, and APP 11.3 says those steps include technical and organisational measures. Privacy Act guide.
Frontier Models (ChatGPT, Claude) Security steps and a named contractor transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 6The likelihood of serious harm
Section 26WE(2) describes an eligible data breach as unauthorised access to or disclosure of information that a reasonable person would conclude would be likely to result in serious harm to any of the individuals. Section 26WG lists what to weigh: the kind and sensitivity of the information, whether security measures protected it, who has it or could obtain it, the nature of the harm and any other relevant matters. The weighing is a judgement the practice makes and records. Privacy Act guide.
Frontier Models (ChatGPT, Claude) The practice’s own harm analysis of a named patient’s result transmitted Ermos Edge Stays on your instance; a permitted excerpt may go to the named Australian provider, and the harm judgement is still the practice’s Ermos Dominion Stays on the unit, but the harm judgement is still the practice’s Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 7The interim view on remedial action
Section 26WF(1) says that if the entity takes action before the disclosure results in serious harm and, as a result, a reasonable person would conclude serious harm is not likely, the event is not an eligible data breach. Whether the facts meet that test is a decision for the practice, with legal advice where unsure. A draft conclusion is not the decision. Privacy Act guide.
Frontier Models (ChatGPT, Claude) A draft conclusion about a statutory decision; sending it does not make the decision for you Ermos Edge Not about where data goes: whether this is an eligible data breach is the practice’s decision Ermos Dominion Not about where data goes: whether this is an eligible data breach is the practice’s decision Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 8Telling the patient
Records a phone call to the affected patient, his reaction and a request for a written account. The patient’s feelings and the chance he will complain sit in the practice’s own record.
Frontier Models (ChatGPT, Claude) A patient’s reaction and the chance he will complain transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 9The statement and notification steps
Section 26WK(3) sets out what a statement must contain: the entity’s identity and contact details, a description of the breach, the kinds of information concerned and recommendations about the steps individuals should take. Section 26WK(2) requires the entity to give a copy to the Commissioner as soon as practicable, and s 26WL requires it to notify affected individuals as soon as practicable after preparing the statement. The steps are public, and sending them to an outside tool exposes nothing beyond the patient’s surname.
Frontier Models (ChatGPT, Claude) Describes the steps the law sets out; the wording is public, but it names the affected patient Ermos Edge Not about where data goes Ermos Dominion Not about where data goes Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case - 10The fixes and the author
Corrective steps with dates, and the manager who wrote the record. They show what the practice will change and who is accountable for it.
Frontier Models (ChatGPT, Claude) Corrective steps and an author; low risk alone Ermos Edge Not about where data goes Ermos Dominion Not about where data goes Use case Breach assessment record organiser. Organises the assessment record from the incident notes and emails, builds a timeline and flags open questions for the practice manager. See the use case
What happens in Frontier Models (ChatGPT, Claude)
- The whole document is transmitted to the provider’s servers. On personal plans the user cannot choose where it is stored or processed, and for the major providers that has generally meant outside Australia, under that country’s legal process. Some business plans offer storage in Australia, but the provider still receives the content.
- On consumer tiers, prompts can be retained and used to train future models.
- The provider’s staff and systems can reach the content under the provider’s own policies.
- Once sent, the practice no longer controls it. Retention and deletion happen on the provider’s terms.
The same document on Ermos
Ermos Dominion
The document is drafted on a unit in your office, from your own templates and the patient record. Every marked item stays on the unit, which keeps working with the internet switched off. Nothing in it is transmitted to an AI provider, so there is no disclosure to analyse: the confidentiality work is the same as for your file server.
Ermos Edge
Your documents, the index and your access boundaries stay on your own instance in an Australian data centre. When a staff member asks for this draft, only their question and the excerpts they are permitted to see go to a named Australian provider, who is contractually barred from keeping the content or training any model on it. Nothing is processed outside Australia.
| Frontier Models (ChatGPT, Claude) | Ermos Edge | Ermos Dominion | |
|---|---|---|---|
| Where the document is processed | Provider servers, generally offshore on personal plans | Your instance in an Australian data centre; answers generated in Australia | The unit in your office |
| Who can read it | Provider staff and systems, under policy | Your staff, within the boundaries you set. The named Australian provider processes only permitted excerpts, under contract, and keeps nothing | Your staff only |
| Is it kept | On the provider’s terms | Kept on your instance; the provider is barred from retaining it | Stays on the unit |
| Can it train a model | On consumer tiers, yes | No, by contract | Only your own unit learns from it, on your hardware |
Part of Use cases in healthcare practices. See how this works in practice: Practice policies and forms on Ermos.
Common questions
Do ChatGPT and Claude use the information in a data breach assessment?
Is it safe to paste a data breach assessment into ChatGPT or Claude?
Does deleting the chat remove a data breach assessment from ChatGPT or Claude?
How can a medical practice use AI for a data breach assessment without sending it to ChatGPT or Claude?
Does a GP practice have to notify data breaches?
How long does a practice have to assess a suspected data breach?
Is a breach involving My Health Record handled differently?
See Dominion answering from your own documents.
A demonstration takes 30 minutes, uses no client data, and comes with no obligation.
Book a demo