A GP clinic can have a modern practice management system and still expose sensitive patient information through a compromised email account, poorly controlled supplier access, an unencrypted laptop or an untested backup. Australian Privacy Principle 11 (APP 11) requires covered organisations to take reasonable steps to protect personal information. For healthcare practices, that means looking beyond software purchases to how people, systems and processes work together.
What does Australian Privacy Principle 11 require?
APP 11 is part of the Privacy Act 1988 framework for entities covered by the Australian Privacy Principles. Two aspects are particularly relevant to medical centres and allied health practices:
Take reasonable steps to protect personal information held against misuse, interference and loss, and against unauthorised access, modification or disclosure.
Take reasonable steps to destroy or de-identify personal information when it is no longer needed for a permitted purpose, subject to legal retention and other exceptions.
The OAIC also explains that reasonable steps include both technical and organisational measures. What is reasonable depends on the sensitivity and amount of information, potential harm, business circumstances and the practical implications of controls. See the official OAIC Chapter 11 guidance.
Why does APP 11 matter for GP clinics and allied health practices?
Patient information can include consultation notes, diagnoses, prescriptions, referrals, pathology results, contact details, Medicare identifiers and billing records. Unauthorised access may affect privacy, patient confidence and continuity of care.
Attackers may obtain referrals, invoices, attachments or account-reset messages.
Unprotected laptops and mobile devices may expose locally stored records.
Weak permissions or compromised supplier accounts can expose information remotely.
Poorly separated guest Wi-Fi or unsafe remote access can increase exposure.
Shared logins or access retained after departure can undermine accountability.
Untested or unprotected backups may leave a clinic unable to restore essential records.
What are reasonable cybersecurity steps under APP 11?
There is no universal security configuration that makes every practice compliant. A small allied health provider and a multi-site medical group may need different arrangements, but both should identify the information they hold, assess foreseeable threats and maintain appropriate safeguards.
Layered security for patient information
Effective protection combines people, process and technology rather than relying on a single tool.
Protect patient information throughout its lifecycle
Security decisions begin before information is collected and continue until it is lawfully disposed of. In healthcare, retention obligations may require keeping some records for specific periods, so disposal decisions should never be made without checking the applicable rules.
Patient information lifecycle
Seven practical security controls for healthcare practices
1. Unique accounts and multi-factor authentication
Use individual staff accounts, enable MFA for email, remote access and administrator accounts wherever available, and promptly revoke access when roles change. Review who can export patient information or administer clinical systems.
2. Secure and supported devices
Maintain an inventory of desktops, laptops, tablets and medical devices. Patch supported operating systems and applications, use endpoint protection and plan for unsupported equipment. Encrypt portable devices where appropriate.
3. Network and remote-access protection
Use managed firewall rules, protect remote access with strong authentication and isolate guest Wi-Fi from clinical systems. Review internet-facing services and avoid exposing management interfaces unnecessarily.
4. Protected, tested backups
Identify critical clinical and business data, protect backup copies from ransomware and accidental deletion, and record successful restore tests. Confirm what your clinical software provider backs up and how recovery would work.
5. Staff training and written procedures
Provide practical guidance on phishing, patient record handling, secure communication and reporting suspicious activity. Document procedures that staff can follow during busy clinical operations.
6. Supplier and cloud security
Know which IT providers, cloud vendors and software suppliers can access or store patient information. Check their access controls, support arrangements, breach notification processes and data recovery responsibilities.
7. Incident readiness and periodic review
Assign an incident coordinator, keep escalation contacts available offline and practise downtime arrangements. Reassess controls after significant changes, new suppliers or security incidents.
How can a practice demonstrate its security decisions?
Documenting security decisions helps managers understand whether controls are actually operating. Evidence does not automatically prove legal compliance, but it supports informed risk management and makes improvements measurable.
| Security area | Useful evidence | Review question |
|---|---|---|
| Account security | Access register, MFA configuration, leaver records | Who can access patient information today? |
| Device management | Asset inventory, patch reports, exceptions | Are any unsupported devices in use? |
| Backups | Backup reports, dated restoration tests | Can critical records be restored? |
| Network controls | Network diagram, firewall and Wi-Fi review | Is guest access isolated? |
| People and processes | Training logs, policies, incident contacts | Would staff know what to do? |
| Third parties | Supplier register, contracts, access review | Who else holds or accesses data? |
| Governance | Risk register, remediation owners and dates | Are identified gaps being addressed? |
Does outsourcing to a cloud provider remove APP 11 responsibilities?
Not necessarily. Under the Privacy Act, an organisation can still βholdβ personal information where it has possession or control of the record, including some arrangements where data is stored by another provider. Clinics should therefore understand what they remain responsible for, what the supplier does and where those responsibilities overlap.
What happens if patient information is exposed?
APP 11 security obligations are distinct from the Notifiable Data Breaches (NDB) scheme. Not every cybersecurity incident is automatically an eligible data breach. When a breach is suspected, promptly contain it, investigate the information affected, assess likely serious harm and determine which notification obligations apply.
Practical incident-response sequence
See the OAIC's NDB guidance. Practices participating in My Health Record or operating under state or territory health records legislation may have additional requirements.
APP 11 healthcare cybersecurity readiness checklist
Use these questions to identify areas that warrant further investigation. A βyesβ answer is not proof of compliance.
- Have we documented which systems and suppliers hold patient information?
- Do staff have unique accounts with appropriate access permissions?
- Is MFA enabled for key accounts and remote access?
- Are clinical computers, applications and network devices supported and updated?
- Is guest Wi-Fi separated from clinical systems?
- Are critical backups protected and regularly restoration-tested?
- Are portable devices and sensitive data appropriately protected?
- Do staff know how to report suspicious emails or privacy incidents?
- Have we reviewed cloud-provider and IT-supplier responsibilities?
- Do we maintain an incident response and clinical continuity plan?
- Do we understand applicable record-retention and secure-disposal requirements?
- Are security findings tracked with owners, deadlines and evidence of remediation?
Frequently asked questions
Does APP 11 apply to small GP clinics?
Private health service providers are generally covered by the Privacy Act even when their annual turnover is below the usual small-business threshold. Specific circumstances should be checked.
Does APP 11 require every clinic to implement the Essential Eight?
APP 11 does not itself mandate a particular Essential Eight maturity level for every clinic. The Essential Eight can be a useful cybersecurity baseline, but appropriate controls must be assessed in context.
Is using a cloud clinical system enough to meet APP 11?
No. Cloud hosting does not replace appropriate staff access controls, secure devices, supplier oversight, policies and incident readiness.
Can a cybersecurity assessment certify APP 11 compliance?
A scoped assessment can identify technical and governance gaps and provide supporting evidence. It is not, by itself, a legal compliance certification or guarantee against cyber incidents.
When should our clinic review its controls?
Review periodically and after major system changes, new suppliers, staff access changes or security incidents. Prioritise according to patient-information risk and operational impact.
Need help reviewing your healthcare cybersecurity controls?
Veytrix Cyber Security helps Australian GP clinics, medical centres and allied health practices assess cybersecurity risks, review practical safeguards and prioritise remediation. Onsite services are available in Sydney, with remote assessment options across Australia.
Request a cybersecurity assessment βOfficial guidance and further reading
- OAIC β Chapter 11: Security of personal information
- OAIC β Notifiable Data Breaches
- Australian Cyber Security Centre β Cybersecurity guidance
- Australian Digital Health Agency β Cyber security
Important: This article is general information, not legal advice, a technical audit, a regulatory certification or a guarantee against cyber incidents. The applicable obligations depend on your practice, information handling and jurisdiction. Verify current requirements and seek qualified advice where necessary.