A pharmacy data breach response plan that guides action
Prepare a pharmacy data breach response: contain exposure, assess likely harm, decide required notifications and record lessons using current OAIC guidance.


In this article
A pharmacy data breach response plan should help the team act when information may have been lost, accessed or disclosed without authority.
The trigger might be a misdirected email, missing paperwork or unexpected access to a system. Begin with the facts available, rather than waiting for certainty about every affected record.
The Office of the Australian Information Commissioner (OAIC) June 2026 quick reference guide sets out containment, assessment, notification where required and review. These activities may overlap as new evidence arrives.
This article concerns response after discovery. For prevention and supplier assessment, see our pharmacy AI privacy guide.
Key facts
- OAIC guidance calls for prompt containment, assessment, required notification and review; preserve evidence while limiting further exposure.
- The assessment period is not permission to delay notification once an eligible breach is established.
- Check My Health Record obligations separately, coordinate providers and record who owns each outstanding action.
Who leads the pharmacy data breach response?
Name an incident lead and a backup before a breach occurs. Keep current contacts for technical support, privacy advice, management and relevant service providers in the approved response plan.
At discovery, record what was observed, when it became known and who reported it. Separate confirmed facts from working assumptions.
Use a restricted incident record. Do not spread exposed patient information through ordinary group messages while coordinating the response.
A fictional wrong-recipient email
A staff member discovers that an attachment containing patient information went to the wrong address. They have attempted recall but have not confirmed what the recipient received or opened.
The lead can separate the record into three parts:
- Known: Record the destination, information sent, discovery time and containment attempted. Preserve the relevant message and logs securely.
- Uncertain: Record whether access, onward disclosure or effective removal has been established. An unanswered request is still unanswered.
- Next decision: Assign the investigation and serious-harm assessment, including who will decide and carry out any required notification.
The OAIC quick reference guide requires prompt assessment where an eligible breach is suspected. The example cannot determine whether this fictional incident meets that test. Its purpose is to keep an attempted remedy from becoming an unsupported conclusion.
These suggested fields are not a regulator-prescribed form or a statutory “first hour” deadline.
How can you contain exposure and preserve evidence?
The OAIC’s health-service action plan recommends immediate containment and activating the response plan, with professional help where needed.
Containment depends on the incident. Retrieving paper records, stopping an incorrect disclosure or restricting unauthorised system access may require different people and different controls.
Ask the responsible technical or clinical staff to assess a proposed intervention. Abruptly disabling a service can affect ongoing pharmacy work, while deleting logs may remove evidence needed for assessment.
Preserve relevant evidence in an approved location and control access to it. Record the containment action, its timing and what it is believed to have achieved.
Clicking email recall is not evidence that a recipient no longer has the information. Verify the outcome as far as reasonably possible and document uncertainty.
Coordinate service continuity through the business continuity plan. Restoring operations and assessing information harm are connected tasks, but neither automatically completes the other.
How quickly must you assess likely harm?
The eligible-breach test under the Notifiable Data Breaches (NDB) scheme considers unauthorised access, disclosure or loss. It also considers likely serious harm and whether remedial action can prevent it.
Private-sector health service providers fall within the scheme’s coverage. Do not assume that a general small-business turnover exemption removes a pharmacy’s responsibilities.
The assessment should establish what information was involved, who may have obtained it, the affected people and the effectiveness of remediation.
Consider the sensitivity and circumstances of the information. Avoid deciding solely from the number of records involved or whether the incident was accidental.
The OAIC requires a reasonable and expeditious assessment. Its NDB guidance says to take all reasonable steps to complete the assessment within 30 calendar days after the day of the relevant awareness.
That awareness concerns grounds to suspect an eligible breach. The period is not permission to postpone action, and the OAIC expects shorter assessments where possible.
If reasonable grounds to believe an eligible breach occurred emerge during assessment, proceed with required notification. Do not wait for a final report merely to use the remaining days.
Make notification decisions explicit
Record the decision, evidence, advice obtained and who is responsible for the next step. Revisit it if new facts change the assessment.
| Question | Evidence to establish | Result to record |
|---|---|---|
| What happened? | Known access, disclosure or loss and affected information | Confirmed facts and remaining uncertainty |
| Is serious harm likely? | Information sensitivity, circumstances and affected people | Assessment and supporting reasons |
| Did remediation prevent likely serious harm? | Verified containment outcomes | What was prevented and what remains possible |
| Is notification required? | Eligible-breach test, exceptions and other obligations | Decision, recipients, owner and timing |
| What should people do? | Practical steps relevant to the incident | Clear advice and a contact route |
Ordinary NDB notification
For an eligible breach, notify individuals at risk of serious harm and provide a statement to the OAIC. Do this as soon as practicable, unless an exception applies. The OAIC guide explains both parts of the process; a message to patients alone does not complete it.
Use clear language and practical protective steps. Do not expose other people’s information in a notice or present uncertain facts as established.
My Health Record notification
My Health Record incidents have a separate reporting pathway. This concerns the My Health Record system, not every record held locally by a pharmacy.
A private registered healthcare provider organisation reports a notifiable My Health Record breach to both the OAIC and the Australian Digital Health Agency, as soon as practicable.
The Agency is the System Operator and handles statutory healthcare-recipient notices. The provider must request those notices where required. Check this pathway separately from the ordinary NDB serious-harm test.
Coordinate providers and close the remaining work
If a provider is involved, agree who supplies evidence, who assesses the impact and who handles required communication. Confirm those actions rather than assuming the vendor has covered them.
A request to the provider is not a completed assessment. Keep an action list with owners and review dates, and distinguish evidence received from evidence assessed. After the immediate response, review causes, controls and staff preparation, as the OAIC’s health-service action plan advises.
Use the incident review process to track corrective work and check whether it was effective. Keep sensitive breach evidence under appropriate access controls.
A useful closing record explains the assessment outcome, notifications, continuing support and outstanding improvements. It should show what was done and what remains open, without claiming that a checklist guarantees compliance.
Frequently asked questions
- What should a pharmacy do when it discovers a possible data breach?
- Activate its response plan, contain further exposure safely, preserve relevant evidence and appoint a lead to coordinate prompt assessment and required notifications.
- Does every pharmacy data breach require NDB notification?
- No. Assess the eligible-breach test and any exceptions, while separately checking other reporting obligations, including My Health Record requirements where relevant.
- Can a pharmacy wait 30 days before reporting an eligible breach?
- No. The assessment framework is not a notification grace period; notify as soon as practicable once there are reasonable grounds to believe an eligible breach occurred.
- Does using a software vendor remove the pharmacy's responsibility?
- No. Coordinate the response with relevant providers and clarify responsibility rather than assuming another organisation has completed the pharmacy's assessment or notification.
Preparation note
Prepared with AI-assisted drafting, separate Codex reader reviews and primary-source checks on 19 October 2026. Examples and generated images are illustrative; source scope and limitations are stated in the article.
Publisher: Krepko.
Sources
- Quick reference guide for responding to data breaches · OAIC · Retrieved
- Part 4: Notifiable Data Breach scheme · OAIC · Retrieved
- When to report a data breach · OAIC · Retrieved
- Data breach action plan for health service providers · OAIC · Retrieved
- Mandatory data breach notification in the My Health Record system · OAIC · Retrieved


