Clinical Photos in General Practice: A Consent and Documentation Workflow That Holds Up

Almost every general practice takes clinical photos now, and almost none of them would pass an audit of how those photos are consented, stored and shared. The photos themselves are rarely the problem — it's that they live in camera rolls, personal phones and unlabelled folders, where neither privacy law nor good clinical follow-up can find them.

Why photos are the record's weak point

A clinical photograph identifies a patient as plainly as their name — faces, tattoos, hands, even the wound's location tell a story. Under Australian privacy law that makes the photo health information, subject to the same collection, storage, access and retention rules as the rest of the record. Yet in a typical practice the photo workflow is: take it on someone's phone, message it to the GP or the specialist, and let the original settle into the camera roll forever. Consent was probably verbal. Storage is whoever's handset. Retention is forever, by accident.

The capture checklist: 30 seconds at the bedside

Every clinical photo, captured with four things recorded:

1. Consent: the patient agreed to the photo for this purpose — documented at the time, with the scope (care, specialist sharing, teaching) stated.
2. Identity and context: patient, date, body site, and who took it. "IMG_4471" is not a clinical record.
3. Placement: the photo goes into (or is linked from) the patient's record — the same place any other observation lands.
4. The next photo: a review date. Wound series and lesion monitoring only work if the next capture is scheduled, not remembered.

Storage: encrypted, local, and linked

The storage test is simple: could you produce, on request, every photo of a given patient, prove where each one lives, and delete them on request? Photos scattered across personal phones fail all three. What passes is a single encrypted store, owned by the practice, linked to the record, with retention aligned to your health-records policy.

This is the gap Camog was built to close for Windows-based practices: photos are captured with consent recorded per shot, stored encrypted and offline on the practice's own machine — they never touch a phone's camera roll or a cloud album — and the review timeline keeps wound series and lesion checks on schedule. Side-by-side comparison makes the "is this healing?" conversation with a patient a thirty-second overlay instead of a scroll through a gallery. There's a 14-day free trial if you want to see the workflow on your own hardware.

Sharing: consent scope, secure channels

Most photos in general practice exist to be shared — with a dermatologist, a wound consultant, a district nursing service. Two rules keep sharing defensible. First, the patient's recorded consent must cover the transfer: what's being sent, to whom, and why. Second, the channel must be assessed for security — ordinary SMS and personal email aren't, and a photo "just this once" in a text message is exactly the photo that surfaces later. Where a specialist needs images, use your secure messaging or referral platform and keep the consent record with the photo.

What an audit (or a complaint) will ask for

If a complaint or a privacy review ever lands, the questions are predictable: Do you have a photography policy? Where are photos stored, and who holds the keys? Show me the consent record for this photo. How are photos retained and destroyed? Practices with the workflow above can answer all four from the system. Practices with the camera-roll workflow answer from memory — and memory is not evidence. For the systems thinking behind workflows like this, our piece on building reliable systems for GP decision-making covers the principles; the GPCCMP documentation workflow applies the same record-once discipline to plans.

This article is general information for Australian general practice teams, not legal or privacy advice. Confirm your photography, storage and consent procedures against the Privacy Act 1988, your state or territory health records legislation, AHPRA guidance and your own practice policies.

Frequently asked questions

Where should clinical photos be stored?

Clinical photos are health information, so they belong in encrypted storage that is linked to the patient record and covered by the practice's privacy and retention policy — not in the camera roll of a personal phone, not on a shared drive, and not in an email thread. Tools like Camog store photos encrypted and offline on the practice's own Windows machine, with each photo tied to its consent record.

How is consent for clinical photos documented?

At the point of capture: who consented, when, to what purpose, and whether the photo may be shared (for example with a specialist). The consent record should be attached to the photo itself so that any future use or transfer can be checked against what the patient actually agreed to — not reconstructed from memory.

Can we send clinical photos by SMS or email?

Ordinary SMS and email are not secure channels for identifiable clinical images, and neither is messaging a photo from a personal phone. The safer path is to store the photo in a secure system and share it by the channels your practice has assessed — for example a specialist referral platform or secure messaging — with the patient's consent scope covering the transfer.

Do patients have to consent in writing for clinical photos?

Consent for photography taken as part of care can be implied in limited circumstances, but the defensible practice standard is documented, specific consent — particularly for storage beyond the episode of care, any sharing, or teaching use. If the photo's use ever changes, consent needs to be re-checked against the record.