Ask Fellow Optoms

Optometrists are Risking Legal Consequences on Clinical WhatsApp Groups,Even without Participation

01
You open the group and see "what do you think of this OCT image?"
Potential Breach

Under GDPR Art. 9, even without a name, identifiable clinical images require a lawful basis and a secure, auditable channel. WhatsApp does not verify whether an image has been anonymised, so you may have a patient-identifiable image on your device. Even if anonymised and consented, WhatsApp has no mechanism to log that consent. WhatsApp does not provide authenticated, time‑limited clinical image links, consent logging, or automated checks for identifiable patient features, and it is not designed or documented as a healthcare‑grade platform.

How it affects you

The clinician who sends the image and colleagues who retain it on a personal device is accountable. The GOC's 2025 Standards explicitly require maintaining confidentiality when sharing patient images online and strengthened consent provisions when sharing patient data - both are breached here. This exposes clinicians to GOC fitness-to-practice proceedings. ICO enforcement action has followed from exactly this type of uncontrolled image sharing.

02
The image is saved to your camera roll
Potential Breach

Once an image leaves a controlled clinical environment and enters a consumer app, you lose organisational control over confidentiality, integrity, and availability, three core GDPR Art. 5 principles. A compliant clinical platform prevents device-saving entirely and blocks in-app screenshots. WhatsApp's auto-save option is not off by default, does not prevent screenshots, and does not remove images already stored.

How it affects you

The clinician on whose device the image is stored is responsible for personally possessing patient data. The GOC expects registrants to take personal responsibility for data on devices they use clinically.

03
You viewed the chat but never posted
Potential Breach

Passive access to patient data on a non-compliant channel is still access to patient data on a non-compliant channel. Under GOC Standard 3, if it shapes clinical decisions but never appears in the patient record, it creates an accountability gap that cannot be defended. A compliant system logs all access in an auditable way. WhatsApp does not provide an organisation‑level audit trail of who accessed which clinical images or discussions and when.

How it affects you

The clinician who reads and is influenced by the discussion is liable to proceedings. GOC Standard 3 places a positive duty on registrants to protect patient confidentiality - receiving and acting on information does not require you to have posted it. Under GDPR Art. 5(2), accountability applies to anyone who accesses the data, not only those who share it.

04
The image is forwarded for a second opinion
Potential Breach

Forwarding extends the breach. Patient data now reaches individuals outside any consent framework who may have no formal involvement in the patient's care. GDPR Art. 5(1)(b) requires data to be processed only for specified, lawful purposes. Forwarding a clinical image over WhatsApp fails that test entirely.

How it affects you

The clinician who forwards, and anyone who receives and retains the data without appropriate controls is accountable. Each person in the chain may face individual GOC fitness-to-practice scrutiny.

05
The chat is deleted
Potential Breach

Deletion on your end does not remove data from anyone else's device, cloud backups, or screenshots already taken. The breach existed the moment data was shared on a non-compliant channel. Deleting compounds the problem - it removes any possibility of demonstrating what was shared, by whom, and when. Under GDPR Art. 5(2), you must be able to demonstrate compliance (the accountability principle). Deletion actively undermines that.

How it affects you

The clinician who deletes is accountable, under the misapprehension that it resolves the breach. The practice if it has failed to train staff on information governance. This could be viewed as evidence destruction in a GOC or ICO investigation.

06
This becomes routine
Potential Breach

The problem is no longer individual messages - it is systemic. The practice cannot demonstrate that clinical communication is secure, auditable, or compliant. That is a significant red flag for GOC reviews, ICO investigations, and CQC inspections. NICE guidelines on safe information governance apply at a practice level, not just individually. Systemic failure carries far greater regulatory and reputational risk than any single incident.

How it affects you

Responsibility lies with individual clinicians for embedding a non-compliant workflow, and practice leadership for allowing a culture where patient data is routinely processed through an ungoverned consumer channel. Both the GOC and ICO can act against individuals and organisations simultaneously.

Here's how the Ask Fellow Optoms app reduces these risks and remains the most secure communication channel for eye care professionals...

COMPLIANCE COMPARISON
WhatsApp vs Ask Fellow Optoms
Not metBuilt-in & enforced
 WhatsApp
Ask Fellow Optoms
ACCESS & IDENTITY
Target audienceAnyone with a phone number can be addedGOC registration number required; status self-asserted and confirmed as an active eye care professional
Identity verified on every sessionNo session-level verificationFirebase Auth tokens validated on every request; sessions expire automatically
App integrity checks (blocks fake scripts)No client attestationApp Attest (iOS) and Play Integrity (Android) - only the official app can communicate with the backend
Role-based access controlsNo access hierarchy; all members see everythingStrict Firestore security rules; admin privileges enforced via secure Google Custom Claims, not stored in the client
ENCRYPTION & INFRASTRUCTURE
Encryption in transitEnd-to-end between devicesTLS 1.3 enforced on all data in transit across all platforms
Encryption at restConsumer‑grade encryption; no healthcare‑specific guarantees or documentation on encryption at rest.AES-256 encryption at rest via Google Cloud infrastructure
Healthcare-grade cloud infrastructureConsumer infrastructure; no healthcare-specific compliance layerBuilt on Google Cloud / Firebase - infrastructure trusted by thousands of healthcare and enterprise organisations
Data stored within EEANo guarantee of UK/EEA data residencyAll data processed and stored in European Firebase data centres; no transfer outside EEA without appropriate mechanisms
CLINICAL IMAGE HANDLING
Images never publicly accessibleImages delivered openly to all group members with no access restrictionsAll images stored with granular security rules; never publicly accessible under any condition
Time-limited, authenticated image linksImages accessible indefinitely once receivedShort-lived signed GCS URLs (10-minute expiry); once closed, the image cannot be retrieved, forwarded, or viewed without re-authentication
Computer vision blocks identifiable imagesAny image can be shared with no content checksAutomated detection blocks upload of images containing identifiable patient features; images with visible text go through internal review before becoming accessible
Images cannot be saved to deviceMedia typically saves to gallery/camera roll by default unless users change settings; often synced to iCloud / Google Photos.Platform-level controls prevent saving to device, including screenshots
Screenshot blockingScreenshots unrestrictedScreenshots blocked within the app as a platform-level control
Automated metadata removalEXIF metadata (location, device, timestamp) may be retained in shared imagesAutomated metadata stripping applied to uploaded content to reduce re-identification risk
CONSENT & GOVERNANCE
Documented patient consent workflowNo consent mechanism; no record of patient agreementUsers must confirm patient has been informed, right to object explained, and consent obtained before any image is attached to a case
Lawful basis for data sharingNo mechanism to establish or document a lawful basis under GDPR Article 9Platform is structured around lawful, documented data sharing; DPA and Privacy Policy set out responsibilities for users acting as Data Controllers
GDPR / UK DPA 2018 compliant by designConsumer product; not designed for special-category health dataData protection principles (lawfulness, fairness, minimisation, security by design) applied throughout; DPIAs conducted where required; ICO-registered
Full audit trail of data accessNo clinical audit trail; no reliable record of who accessed which image or when at an organisational level.Cloud Logging active for all sensitive operations; audit logs retained for regulatory compliance
Breach notification within 48 hoursNo healthcare Data Processing Agreement or contractual breach‑notification commitment for clinical use.Committed to notifying Data Controllers within 48 hours of confirmed health-affecting patient data breach (DPA Section 16.7)
Immutable records (deletion doesn’t erase evidence)Deleting a chat removes your copy but data persists on other devices and backupsGoverned audit logs cannot be removed by users; accountability for access is maintained independently of message deletion
Data Processing Agreement in placeNo DPA available for clinical useFull DPA published (Section 16 of Terms); sub-processors (Google Cloud, SendGrid) documented and bound by equivalent agreement
PROFESSIONAL STANDARDS
GOC standards alignmentNo alignment with GOC information governance expectationsPlatform designed with GOC guidance in mind; users required to adhere to GOC rules as a condition of use
Content moderation & reportingNo clinical content moderator; any content can be sharedFacilitated and risk-based moderation; users can report content; platform can remove, restrict, or escalate where needed
CPD evidence loggingNo engagement tracking or CPD evidence≥ 35 minutes of logged engagement = 0.5 CPD points; evidence downloadable for GOC submission
Force-update mechanismNo controlled update enforcementFirestore-driven force-update prompt ensures all users run the latest, security-patched version
Download the Ask Fellow Optoms app below
Download on the App StoreDownload on Android