How to name clinical photo files

The phone names photos like IMG_4821 or 20261029_101455. For a vacation photo, that works. For the clinical photo of a patient who returns in six months, it works poorly: nobody knows which is before and which is after, whose it is, which view, which session. When the team grows and the volume increases, the lack of a standard turns into comparison errors or, worse, a photo filed under the wrong patient.

The solution is a naming standard that is simple, repeatable and does not reveal who the patient is to someone who only sees the file list.

Why not put the patient's name in the file?

The file name travels with the file. It appears in the gallery list, in an email preview, in a message notification, in the cloud backup and in any system that indexes files. A name like "maria-silva-before-lips.jpg" reveals identity, type of treatment and stage to anyone who sees the list, including people who should not.

A patient's facial photo is sensitive data, handled with extra care under the LGPD (Brazil's General Data Protection Law). The minimization rule also applies to the file name: only what is needed to organize should be in it. Identity stays in the patient chart, which links the code to the patient, and the code alone says nothing to someone who sees only the folder.

What name structure works?

A structure with few fields, always in the same order, is easier to follow than an elaborate one. A suggestion:

Put together: P0123_2026-10-29_before_frontal_01.jpg. The underscore separates fields, and the hyphen appears inside the date. Do not use accents, spaces or special characters, which cause problems in some systems and when sharing.

How do you define the patient code?

The code must be unique, stable and meaningless outside the clinic. Avoid initials, birth dates, phone numbers or pieces of the CPF: any of them lets someone identify the patient with a bit of effort. Prefer a sequential number with a letter, assigned at registration.

The link between code and name stays in the chart or the clinic's system, with restricted access. If the file ever leaks, whoever finds it sees a photo and a code, not the identity. This does not cancel the risk, because the face is identifiable on its own, but it reduces the amount of information exposed.

How do you indicate stage and view in the name?

Standardize a short vocabulary. It prevents the "before2", "after-final" and "new" that nobody understands a year later. An example list:

• before: initial photo, before any procedure in the series.
• d0: photo immediately afterward, when the day is recorded.
• d15, d30, d90: follow-ups in days after the procedure, according to your follow-up protocol.
• touchup: photo before a touch-up.
• complication: record of an adverse event, with more restricted access.

Use the same convention for the view: frontal, profile-r and profile-l when they exist, and specific names for dynamic photos or photos of one area. For adverse-event records, see complication photo: how to record it. To decide the date of each follow-up, see when to take the follow-up photo.

What about folder organization?

The file name and the folder structure complement each other. A simple tree: one folder per patient code, and inside it one subfolder per visit date. That way, even if a file name is changed by mistake, the folder preserves the context.

Avoid folders by general clinic date, which mix patients, and folders with people's names. Also avoid piling up photos in the phone gallery without organization, the subject of phone gallery and patient photos. When the photo moves from the device to the clinic's system, rename it at the time of transfer, while the patient is still fresh in memory.

What do you do with old photos that follow no standard?

You do not need to rename everything at once. Apply the standard from a cutoff date and, when you open an older patient's record, rename what you use. If the volume is large, a batch-renaming tool helps, but check a sample before applying it to all files: a batch error spreads the problem.

If the old photos carry the patient's name, rename them first, because they expose the most. And do not delete the originals before you have a safe copy, as described in backing up clinical photos.

Metadata and name: two sides of the same care

A good file name does not remove what is inside the file. Date, location and device model remain stored in the metadata, the subject of metadata and location in patient photos. Think of the two together: a neutral name outside, controlled metadata inside.

What about Harmy?

In Harmy, the professional enters the patient's name in the projection and the name search in the history organizes sessions by patient. That solves organization inside the app. The photos you use outside it, such as the chart, consent forms and backups, still call for your own naming standard. The app's sharing image is an illustrative simulation with the clinic's header and should be named and stored in a way that is not confused with a record of results.

For the app flow, read standardized frontal photo and the overview in standardized clinical photography.

Summary for the routine

Define a short structure, use a code instead of a name, put the date in computer order and save in folders by patient. The result is an archive the team understands and that exposes little, even if a file list escapes. Always check the requirements of your professional council and Brazilian medical-record legislation.