Gidsen 

Start with a form that shows how decisions are made

Keep client-reported facts separate from the operator's interpretation. A client can describe an earlier reaction or list a medicine; the review section records which instruction applies and whether the issue has been resolved. Do not ask clients to certify that they have “no contraindications” to a device they may never have used.

The following is a proposed field architecture to adapt and review. It is not an official form, a validated risk score or a complete set of screening questions.

Every screening question should have a purpose and a review route. If an answer would not change the proposed service decision, and no applicable governance requirement justifies collecting it, reconsider the field. The UK Information Commissioner's Office (ICO) describes data minimisation as collecting information that is adequate, relevant and limited to what is necessary. That is a UK example, not a global privacy certification for this structure. [3]

Separate cosmetic goals from requests for medical care

A useful opening question is: “What cosmetic change are you hoping for, and what would you like us to explain before you decide?” Record the answer faithfully. A request about appearance does not establish a diagnosis, and a client naming a disease does not give the operator permission to treat it.

Add an operator field for whether the request fits the proposed device's documented purpose and the operator's locally permitted work. If the client is seeking diagnosis, medication advice or care outside that scope, record the boundary and direct the question to an appropriately qualified healthcare professional. Do not relabel a medical request as “wellness” to make it fit the booking.

Expectation wording also matters. For US health-related marketing, the Federal Trade Commission (FTC) requires objective claims to have appropriate substantiation and considers both explicit and implied messages. A disclaimer does not fix a misleading health claim. Avoid building promises of guaranteed improvement or disease treatment into consultation text. [1]

Use observations without diagnosing

Distinguish “client reports a diagnosed condition,” “operator observed a visible change” and “diagnosis not established.” Record only observations relevant to the decision. A consultation record should not turn a visual observation into an unsupported disease label or prescribe treatment for it.

Match screening questions to the exact device instructions

Begin with the current IFU for the installed model, its intended use and the proposed mode and body area. Identify exclusions, warnings, precautions, required assessments and any instructions about professional review. A general light-therapy questionnaire cannot supply missing manufacturer instructions.

ARPANSA's Australian advisory addresses client assessment, training, equipment and radiation protection across laser, intense pulsed light (IPL) and LED services. It also notes that LED eye hazards depend on exposure intensity and time. The advisory provides context for careful assessment; it is not a universal LED protocol or a current licence to practise. Its historical regulatory discussion should not be used as today's local rules. [2]

Topics to consider, with a reason for each

• Conditions and light reactions: ask about the conditions and previous light-related reactions relevant to the IFU. Record what the client reports, what happened and what remains unclear. Do not convert a generic list into exclusions for every LED device.
• Medicines and relevant topical products: collect the information needed to evaluate the device warnings. Where it matters, record the name and enough detail for the appropriate reviewer. The operator should not tell the client to stop a prescription or calculate a medication washout period.
• Recent or planned procedures: ask which relevant procedure occurred, where and when, and whether associated instructions are available. Record a compatibility question for review rather than inventing a standard waiting period.
• Pregnancy, breastfeeding or implants: include questions where the device instructions or applicable governance make them relevant. Neither a missing warning nor a general claim that LED is gentle establishes permission.
• Eyes and protection: capture any information required by the device's eye-related warnings and whether its specified protection requirements can be met. A form cannot choose substitute eye protection.

These are question categories, not a statement that each category is a contraindication. The actual wording and action must come from the matched documents and an appropriately qualified review. If the service combines LED with another technology, assess that combination's documentation separately; pure LED questions do not establish suitability for electrical, thermal or other modes.

Create a question-to-instruction map

For each retained question, maintain an operator reference with these fields:

1. Purpose: what decision-relevant issue the question addresses.
2. Authority: exact device/model, IFU revision and section, or separately identified local governance requirement.
3. Answer route: who reviews a positive, uncertain, missing or conflicting answer.
4. Resolution: what evidence is needed and how the final decision is documented.

Do not create a numerical score that “passes” a client: this structure has not been clinically validated. “Not sure,” a blank response and “prefer to discuss privately” must remain distinguishable from “no.” When required information is unresolved, leave the suitability review incomplete and defer the proposed service while the issue is clarified.

Record deferral and referral as specific decisions

A useful outcome record explains the reason, the responsible person and what information would allow reconsideration. “Doctor's note needed” is often too vague to show which question needs answering.

Where healthcare input is appropriate, frame a focused question about the relevant condition or medicine and the proposed device exposure. Provide the necessary device information through an authorised, privacy-appropriate route. A general statement that the client may have “light therapy” does not resolve a device-specific exclusion, a missing IFU or the operator's scope.

Example record wording

Proposed LED service deferred. The client reported information that requires review against the device instructions. The relevant question remains unresolved; no exposure was provided. The client was told what clarification is needed and who should review it. Reconsideration requires a documented review for the specified device and proposed service.

This is sample writing, not a patient account. In an actual record, add the necessary facts, document reference, operator, date and next action. Avoid unnecessary diagnostic detail, speculation or a promise that clarification will automatically lead to a session.

Keep a referral recommendation distinct from a completed referral, and advice received distinct from advice still pending. A client acknowledgement records what was discussed; it does not transfer responsibility or override instructions.

Collect less sensitive information, but enough to resolve the question

Under UK GDPR, health information is special category data. ICO guidance explains that lawful processing requires an Article 6 basis and an Article 9 condition, with associated requirements where applicable. Its guidance is currently flagged for review following the Data (Use and Access) Act. A signature consenting to a beauty service should not be assumed to satisfy these separate data-processing requirements. [4] [5]

For any jurisdiction, have the responsible person review the form's purpose, permitted collection, privacy information, access controls, storage, retention and sharing arrangements. This article does not prescribe a universal retention period or certify legal compliance.

• Explain why relevant questions are asked and provide a private discussion route.
• Collect only necessary details; do not request a complete medical file by default. UK ICO guidance specifically stresses minimisation for sensitive data. [3]
• Separate client statements from operator notes, with the reviewer's identity and date.
• Restrict access according to a person's role and the applicable governance arrangements.
• Keep optional marketing or public-image permissions distinct from the service record, and verify the rules for each intended use.

Common form mistakes to avoid

• “Everything marked no means safe.” Answers still need review for completeness, relevance and the proposed service.
• “One form covers every light-based service.” A shared identity section is useful; device and procedure questions require their own matched review.
• “A signed waiver clears the risk.” Documentation cannot resolve an unanswered suitability question.
• “More medical questions always make a better form.” Irrelevant collection adds sensitive data without supplying a decision basis.

Practical questions

What if the client declines to answer a relevant question?

Explain its purpose and offer a private discussion. Do not record refusal as “no.” If information needed for the proposed service cannot be established through an appropriate route, record the unresolved issue and defer. Collecting more unrelated information is not a solution.

Does every return visit require a new full questionnaire?

There is no universal interval established here. Design a dated change-review process under the relevant IFU and governance arrangements. It should identify changes in relevant history, the proposed device or service, and unresolved earlier issues. Carrying forward an old signature does not document what was reviewed today.

What happens when the IFU changes?

Review affected questions and decision routes before using the revised form. Give the form a version identifier and retain the applicable document reference with the consultation record, subject to retention governance. Do not silently rewrite what an earlier review was based on.

Can an online form automatically approve a booking?

Use it to collect and route answers, not to present this unvalidated structure as automated medical clearance. Ensure a responsible reviewer can see uncertainties and conflicting answers. Any automated decision process also needs its own applicable privacy and governance assessment.

Before the form enters service

Have the responsible service lead match each question to the installed device's current documents and confirm the operator's scope and local data handling. The finished record should make it clear what was reviewed, what remains unknown and why the proposed service was offered, declined or deferred.