บทความ

The core record: enough to reconstruct the visit

The following is an adaptable documentation framework, not an internationally required form. Use it alongside the instructions for use (IFU) for the exact device, your service scope and applicable local record requirements. Fields describe what actually occurred; their presence does not make a setting acceptable.

• Visit and people: client record reference, session identifier, date and time, operator identity and person entering the record.
• Device and setup: manufacturer/model, unit identifier, IFU version, selected program or mode, treatment area, positioning, accessories and protection actually used.
• Review and decision: consultation and consent references, relevant changes reported, unresolved checks, and whether the session proceeded, was deferred, was declined or never started.
• Session events: intended program, actual start/stop events, pauses, changes, early termination, display messages and faults.
• Response and next action: separately attributed observations and client reports, actions taken, linked incident record where needed, and responsibility for any follow-up.

Keep a session log connected to the consultation, device documents and incident records rather than copying everything into every entry. Review what each field is for: the UK Information Commissioner’s Office (ICO) describes data minimisation as holding enough relevant information for the stated purpose, without unnecessary data. That is a UK rule, not a universal salon template. [1]

Record the actual device and labeled setup

“Red light facial completed” cannot identify which unit or program was used. A shared equipment register can hold stable information; the session entry can link to its version and add the details that changed during the visit.

Separate a display setting from a measured output

A control reading, a specification in a manual and an instrument measurement are different kinds of information. Give each its source. If wavelength information is needed for traceability, identify it as the manufacturer’s labeled specification unless it was independently measured. A program name alone does not establish its spectrum.

If an output measurement exists, link its report, date, instrument, method and geometry. Do not describe it as today’s client exposure unless the record supports that match. If no measurement was made, write “not measured.” Do not calculate or insert an exposure value from an unverified intensity percentage or generic brochure value.

Preserve actual timing rather than the planned appointment length

Record the selected program separately from actual start, pause, restart and stop events. Identify whether elapsed exposure comes from a device event log, direct observation or an estimate. A booking duration includes activities other than light exposure. If an interruption makes the actual exposure uncertain, preserve that uncertainty instead of entering the planned duration as fact.

These fields support reconstruction. They do not instruct an operator to adjust duration, distance, intensity, pulse settings or frequency. Those decisions require the matched instructions and an appropriate suitability assessment.

Link suitability changes and service consent

Reference the consultation reviewed for that visit and record any relevant change since it was completed. “No relevant change reported when asked” identifies the client’s report; it does not establish that no change exists. Name the operator making the service decision and record its basis and any outstanding question.

Device warnings are specific. For example, the available Omnilux Contour safety document prohibits use during pregnancy or breastfeeding because those populations were not tested. This supports respecting that system’s warning; it neither proves universal harm nor supplies clearance for another LED device. [4]

When a device-specific suitability check needs medication information, retain the necessary details in an appropriately restricted record and link the decision in the session log. “Medication change reported; relevant IFU check unresolved; session deferred” is more informative than “client signed, therefore safe.” Do not advise a client to stop prescribed medicine or use a blog-derived waiting period to resolve the check.

For service consent, record the document/version, when the discussion occurred, relevant questions and whether the client agreed, declined or withdrew agreement. Do not auto-populate consent for a visit that was cancelled or for a changed procedure that was never discussed.

Consent to an LED service is separate from the legal basis for collecting health information. In the UK, processing special category data requires an Article 6 lawful basis and an Article 9 condition, with additional requirements where applicable. A service-consent signature does not automatically establish these. [3]

Document interruptions and reactions without inventing a diagnosis

Use a sequence of events: what was reported or observed, when it happened, what exposure was occurring, what the operator did and what happened next. Include an equipment message exactly as displayed where relevant. If the session stopped, say so; do not silently mark the planned program as completed.

These are writing examples, not actual client cases or instructions to continue a session.

If a clinical diagnosis is supplied through an appropriate source, attribute it accurately. Otherwise, describe the finding. Record onset and later reports separately, including when the salon learned of them. Timing alone cannot establish that LED caused a symptom.

Device identity matters in safety follow-up: the TGA’s historical Neutrogena red/blue acne-mask recall concerned that named home-use system and potential eye damage in susceptible people. It is not a finding about every current salon LED system. [5]

Keep amendments and follow-up traceable

Complete entries as close to the event as practicable. Label a later entry with both the event date/time and the entry date/time, its author and the source of any reconstructed detail. For a correction, preserve the original through a readable amendment or system history, then state what changed and why. Never backfill a guessed setting as an observation.

Where follow-up is needed, identify the action, responsible person, status and linked communication or incident reference. Record reporting decisions under the applicable manufacturer and jurisdictional process. A session note does not replace a required incident report.

Define access, privacy and retention before routine use

Do not select a retention period by copying another salon’s form. In the UK, the ICO says UK GDPR does not specify fixed time limits for different record types: the period must be justified by the purpose, with review and erasure or anonymisation when information is no longer needed. Check applicable local legal duties and any claim-preservation needs before settling the policy. [2]

For local service requirements, GOV.UK directs businesses to their council; Redbridge expressly lists LED among licensed light treatments. That local example does not establish a national LED record format or retention period. [6] [7]

The ICO pages cited here flag guidance review following the Data (Use and Access) Act. Recheck the current requirements for the actual business. Other countries require their own assessment.

A practical privacy review for the record system

The following are design questions, not a declaration that a particular system complies with law:

• Purpose: Why is each field needed, and does it belong in the session log or a restricted supporting record?
• Access: Which staff need session details, which need sensitive consultation information, and who can amend or export either?
• Storage: Who manages paper files, digital accounts, backups and any service provider holding the records?
• Transparency: What has the client been told about data use, storage and access? Is that separate from the service discussion?
• Retention: What purpose and applicable requirement justify each record category’s period, when is it reviewed, and how are deletion and valid preservation needs handled?
• Sharing: What necessary information would be shared with a clinician, manufacturer, insurer or authority, and through what approved process?

A client code reduces repeated identifiers but does not make a record anonymous when the salon can reconnect it to a person. Likewise, separating health details into another file does not remove the need for a valid processing basis.

Common mistakes that weaken the log

• “The default program was probably used.” Preserve an unknown as unknown. A default is not evidence of what happened.
• “No complaint means no reaction.” Distinguish “client reported no discomfort,” “none observed,” “not asked” and “no later follow-up available.”
• “A signed form clears every session.” Document changed circumstances, device requirements and the actual decision separately.
• “More health details always make a better record.” Collect relevant information for a defined purpose rather than copying an entire medical history into routine notes.
• “Client improvement proves the treatment works.” An individual report can be recorded with attribution. It does not establish efficacy. US FTC guidance requires appropriate substantiation for underlying health claims made through testimonials. [9]

Practical questions

Should a cancelled or deferred visit have a record?

For traceability, distinguish a booking cancellation from a visit where a suitability issue was identified. Record the relevant decision and any necessary follow-up, using proportionate detail. Make it explicit that no exposure occurred rather than creating a completed-session entry.

Do I need a photograph for every session?

A photograph is not necessary merely because a session log exists. If photography has a defined purpose, assess the required permission, access and retention arrangements and link the image record. Agreement to a service does not automatically authorise promotional use.

Can the device’s automatic history replace the operator note?

It can support the record, but check which fields it actually captures. It may not identify the client, actual positioning, protection, reported symptoms or reason for stopping. Link the export to the visit and retain its provenance; describe any clock discrepancy or missing event.

What if the entry cannot be completed accurately?

Use distinct states: “unknown” when information is unavailable, “not measured” when no measurement occurred, and “not applicable” when the field genuinely does not apply. Explain material gaps and refer them for review. Empty fields must not silently mean “no problem.”

A useful final check

Before closing the entry, ask whether another authorised person could identify the actual unit, follow the event sequence, distinguish evidence from inference and see what still needs attention. If the answer depends on a guessed setting, unexplained abbreviation or missing linked record, improve the documentation without inventing the detail.