Skip to main content
Resource Guide — Updated August 2026

Allied Health Cybersecurity Guide

Allied health providers across Australia face unique cybersecurity risks — BYOD devices, multi-site working arrangements, telehealth platforms, and highly sensitive patient records. This guide addresses every major threat facing your practice in 2026.

Who This Guide Covers

Australian allied health is a diverse sector spanning dozens of professions, each with slightly different technology environments and risk profiles. This guide specifically addresses the cybersecurity needs of:

Physiotherapy
Psychology
Dentistry
Optometry
Occupational Therapy
Speech Pathology
Podiatry
Chiropractic

While the specific practice management software and clinical workflows differ across these professions, the underlying cybersecurity risks are remarkably consistent: BYOD devices, sensitive patient records, Medicare and NDIS billing credentials, and staff working across multiple clinic locations. The Office of the Australian Information Commissioner (OAIC) classifies all health information held by allied health providers as sensitive information under the Privacy Act, requiring the highest standard of protection.

BYOD Security Risks Unique to Allied Health

Allied health practitioners frequently work across multiple clinic locations — a physiotherapist may see patients at three different practices across the week, carrying their personal iPad from site to site. This "multi-site BYOD" model creates a web of risk that is far more complex than a single fixed-site GP practice.

When a physiotherapist's personal tablet connects to Clinic A's Wi-Fi on Monday, then carries whatever it picked up to Clinic B on Wednesday, any malware acquired at one site can potentially spread to the next. Personal devices are rarely maintained to enterprise security standards: they may run outdated operating systems, lack encryption, have no passcode or biometric lock, and be used by family members at home who download unauthorised apps.

Psychology practices face an elevated version of this risk. Psychologists often see patients in private rooms with personal laptops, access clinical notes via personal cloud accounts, and may work from home between clinic sessions. Each transition point — home to clinic, clinic to clinic — is an opportunity for data to be exposed or for malware to travel.

The Core BYOD Problem

A personal device is not a clinical device. It exists outside your practice's security controls, is not subject to your patch management schedule, and may have no encryption, remote wipe capability, or access controls preventing non-authorised users from reading patient files stored on it. Without formalising BYOD arrangements, your practice is effectively outsourcing its security posture to whatever decisions your practitioners make with their personal phones and tablets.

Telehealth Security: Securing Video Consultations

Telehealth expanded dramatically in Australian allied health post-COVID. Psychology, occupational therapy, speech pathology, and physiotherapy all now commonly deliver services via video consultation. The Medicare Benefits Schedule (MBS) includes telehealth items for most allied health professions, driving widespread adoption. However, the security and compliance dimensions of telehealth are often poorly understood.

Platform selection matters. Coviu is an Australian-developed telehealth platform purpose-built for healthcare, with Australian data storage, ADHA alignment, and Healthcare Identifier Service integration. It uses end-to-end encryption for video sessions and has a published security architecture. Zoom, while widely used, is not purpose-built for healthcare — its default settings do not meet healthcare-grade privacy requirements, and session recordings may be stored on Zoom's US servers without additional configuration to enforce data residency.

Patient consent is a specific telehealth obligation. Before conducting a telehealth consultation, you must obtain the patient's informed consent for the telehealth modality, and that consent must be documented in the patient record. Consent records are health information and must be stored securely in your practice management system — not in a personal email inbox or a personal Google Docs folder.

Data Sovereignty for Telehealth

Under the Privacy Act, transferring patient health information to an overseas server without explicit patient consent may constitute a breach of APP 8. If your telehealth platform stores recordings or session data on servers outside Australia, you must obtain explicit consent from patients — and many patients will decline. Choose platforms that store all patient data within Australia, or obtain and document explicit cross-border disclosure consent.

For a detailed guide to telehealth security compliance, see our Telehealth Security & Compliance Guide.

Psychology Records: Extra-Sensitive Under the Privacy Act

Mental health information is explicitly classified as sensitive information under the Privacy Act. This means psychology records — including therapy notes, diagnosis records, assessment results, and clinical correspondence — attract the highest level of protection obligation under the Act.

The practical implications are significant. Psychology notes must not be stored on unencrypted devices. They must not be transmitted via unencrypted email (which is the equivalent of sending a postcard). They must not be stored in personal cloud accounts (personal Dropbox, personal Google Drive, or personal iCloud — see below). Access must be strictly controlled, and audit logs must record who accessed what and when.

A data breach involving psychology records — for example, an unencrypted laptop containing therapy session notes being stolen from a practitioner's car — carries a very high likelihood of causing serious harm to affected patients, triggering the OAIC notification obligation under the Notifiable Data Breaches scheme.

Dental Practice Security: Imaging Systems and Network Exposure

Dental practices face a specific technical risk that other allied health providers generally do not: diagnostic imaging equipment on the clinical network. Dental X-ray systems, OPG machines, and CBCT (Cone Beam Computed Tomography) scanners are networked devices running embedded software that is rarely updated and often runs on Windows 7 or earlier operating systems with no vendor patch support.

These imaging systems are frequently connected directly to the same network as the practice management system and internet-facing computers. An attacker who compromises an internet-facing workstation through a phishing email can, in a practice with poor network segmentation, move laterally within minutes to reach the clinical server hosting the patient database.

The solution is network segmentation: put imaging systems on an isolated network segment (VLAN) that cannot directly communicate with the practice management server or the internet-facing workstations. This limits the blast radius if one segment is compromised. Your IT provider can typically implement basic VLAN segmentation on a managed switch for minimal cost.

Allied Health Practice Management Systems

The most widely used practice management platforms in Australian allied health — Nookal, Cliniko, Power Diary, and Halaxy — are all cloud-based SaaS platforms. This shifts infrastructure security responsibility to the vendor, but preserves critical security obligations for your practice:

Cliniko

Enable MFA on every user account. Audit active users monthly. Restrict API integrations to essential services only. Review data export permissions — only designated administrators should be able to bulk-export patient records.

Nookal

Use individual login credentials for each practitioner — never share a single login across staff. Enable login notifications for new devices. Review the audit log for any unusual access patterns, particularly after staff departures.

Power Diary

Configure session timeout settings to automatically log out inactive users. Ensure that the email address linked to the admin account uses MFA. Review third-party integration permissions regularly.

Halaxy

Enable two-factor authentication and enforce it for all users with access to billing and patient records. Use Halaxy's built-in audit log to track record access, particularly if you have multiple practitioners sharing the platform.

Cloud Storage: What Is and Is Not Acceptable for Patient Records

❌ NOT Acceptable

  • • Personal Dropbox, personal Google Drive, or personal iCloud accounts for patient records
  • • Emailing patient files to personal email addresses
  • • Storing therapy notes in personal note-taking apps (Notion, Apple Notes) without encryption
  • • WhatsApp or iMessage for transmitting patient documents or images
  • • USB drives without encryption for transporting patient records between sites

✅ Acceptable (with correct configuration)

  • • Microsoft 365 OneDrive for Business (with Australian data residency configured, MFA enabled)
  • • Google Workspace (with Australian data residency, MFA enforced via admin console)
  • • Your practice management system's own cloud storage (Cliniko, Nookal, etc.) — with MFA
  • • Encrypted USB drives with hardware-level encryption (IronKey or similar) for physical transport

BYOD Policy: What Your Practice Must Require

Every allied health practice that allows practitioners to use personal devices to access patient records must have a formal, written BYOD policy. This is not optional — the OAIC expects it as part of your APP 11 security framework. Your BYOD policy must address:

Device Encryption: All personal devices used to access patient data must have full-device encryption enabled (BitLocker on Windows, FileVault on Mac, native encryption on iOS and Android). Practitioners must confirm this before being granted access.
Mobile Device Management (MDM): Enrol all permitted BYOD devices in your practice's MDM solution (Microsoft Intune, Jamf, or similar). MDM allows you to enforce security policies (password requirements, encryption, app restrictions) and remotely wipe the device if it is lost or stolen.
Remote Wipe Capability: Your MDM must have remote wipe configured and tested. When a practitioner leaves the practice or a device is reported lost, you must be able to remotely erase all practice data from the device within minutes.
Passcode/Biometric Lock: A minimum 6-digit PIN or biometric lock (Face ID/fingerprint) must be active on all BYOD devices. Auto-lock should engage after no more than 5 minutes of inactivity.
Separate Work Profile: Use MDM to create a managed work profile on BYOD devices (available on Android and Windows). This separates work apps and data from personal data, limiting the blast radius of a personal-side security issue.

Working From Home: VPN, Home Networks, and Printer Security

Allied health practitioners working from home between clinic sessions — reviewing notes, writing reports, completing telehealth consultations — introduce home network risks into the clinical environment. Home routers are typically consumer-grade devices with default passwords unchanged since installation, no firmware updates for years, and no network segmentation between work and IoT devices (smart TVs, baby monitors, and home assistants on the same network as your clinical laptop).

VPN requirement: All remote access to the practice management system or patient records must be conducted over a Virtual Private Network (VPN). A VPN encrypts the connection between the home computer and the practice network, preventing eavesdropping on unsecured home Wi-Fi. Microsoft Azure VPN Gateway or a simple business VPN service (NordLayer, Cisco AnyConnect) is adequate for most allied health practices.

Printer security: Home printers that receive patient documents are a frequently overlooked risk. Modern home printers store documents in internal memory that can be accessed if the printer is connected to the internet. Never print patient records on a home printer unless the printer is business-grade, firmware-patched, and not internet-facing. Most clinical printing should occur at the clinic, on managed, encrypted printers.

Medicare and NDIS Billing Security

Allied health providers billing under Medicare and the NDIS hold two sets of sensitive payment credentials: Medicare provider credentials (PRODA accounts) and NDIS portal access (myplace provider portal). Both are high-value targets for cybercriminals. A compromised NDIS provider account can be used to lodge fraudulent payment claims for services never delivered, resulting in financial loss and — if not caught quickly — a compliance investigation by the NDIS Quality and Safeguards Commission.

Multi-Person Approval for Large Claims

Implement a two-person rule for NDIS invoices above a threshold amount (e.g., $2,000). One person prepares the claim; a second person reviews and approves before submission. This control catches both fraudulent external manipulation and internal billing errors.

Individual PRODA Accounts

Every staff member who accesses Medicare Online or HPOS must use their own PRODA account with MFA enabled. Shared PRODA credentials are a compliance and security risk — they prevent audit trails and make fraud investigation impossible.

Reconcile Billing Monthly

Reconcile submitted claims against remittance advice monthly. Unexplained discrepancies — claims you don't recognise, amounts that don't match — warrant immediate investigation and notification to Services Australia.

Protect NDIS Portal Credentials

The myplace provider portal must use unique, strong passwords and MFA. Never store NDIS portal credentials in a browser or shared spreadsheet. Use a business password manager (1Password, Bitwarden) to store and manage credentials securely.

Related Resources

Protect Your Allied Health Practice

ShieldForce provides tailored cybersecurity for Australian allied health providers. Book a free assessment to understand your BYOD risk, NDIS billing exposure, and Privacy Act compliance gaps.

Book a Free Assessment

References

Author: ShieldForce Editorial Team

Published: August 2026 | Last Updated: August 2026

See our full author credentials