Contraindications and Warnings for LED Devices: A Risk-Management Checklist for Brands
A contraindication or warning needs a defensible basis in the product’s intended use, known hazards, evidence and applicable requirements. Copying a list from another device fails in two directions at once: it inherits omissions that do not apply to yours, and it adds restrictions you cannot justify. The governed alternative is a traceability table in which every published warning points to a hazard, a control and a residual risk[1].
This page describes a documentation process for brand and safety teams. It is not a diagnosis, and it does not tell any individual whether they should use a device.
Table of Contents
- 1. Start With the Hazard Inventory, Not a List of Conditions
- 2. Trace Every Warning to a Reason
- 3. A Warning Is Only One of Four Answers
- 4. Keep It Consistent, and Give Support a Route Out
- 5. Partner With Rainbow Technology for Custom LED Devices
- 6. References & External Links
1. Start With the Hazard Inventory, Not a List of Conditions
The obvious way to write a contraindications section is to look at three competitor pages and merge them. It produces a section quickly, and it fails in two directions that are rarely considered together. What you inherit is other products’ omissions — hazards your device has that theirs did not — and other products’ restrictions, which now appear in your instructions with nothing behind them.
The second failure is the one teams underestimate. An unjustified restriction is not free caution. It excludes customers you never needed to exclude, it creates a statement your risk file cannot support, and it tends to survive forever because nobody can prove it is unnecessary. Warnings have to be earned in both directions.
So begin with the finished product and what could go wrong with it. Eight domains cover most LED wearable devices, and the relevant subset differs by design and intended use — do not assume all eight apply to your model.
- The optical source. Output, spectrum, geometry and proximity to the eyes or to skin that is already compromised.
- The electrical system. Charging input, insulation, and what happens when a user supplies their own charger.
- Heat. Surface temperature over a full session, and behaviour in a warmer room than the one you tested in.
- Materials. Everything in prolonged skin contact, and how those materials behave after repeated cleaning.
- Cleaning. Which agents the product tolerates, and what a user is likely to reach for instead.
- Mechanical fit. Adjustment range, pressure points, and whether the device stays where the exposure assumes it is.
- Battery and charging configuration. Swelling, damage, storage and transport, and the instructions that go with each.
- Foreseeable misuse. Longer sessions, shared devices, use over topical products, use on broken skin, use while the unit is damaged.
2. Trace Every Warning to a Reason
The deliverable is a warning-to-risk traceability table, held under document control, in which no published sentence exists without a row behind it. Four columns are enough, and the fourth is what makes the table usable by a copywriter who has never read the risk file.
| Hazard or Use Condition | Evidence | Control Chosen and Residual Risk | Where It Appears |
|---|---|---|---|
| Eye exposure at close range | Photobiological assessment at a defined distance | Design spacing plus a shield. Residual: the user lifts or rotates the mask, so the instruction states fit and prohibits that position. | Instructions, label, FAQ |
| Skin-contact temperature | Full-session thermal record at a stated ambient temperature | Timer limit and material choice. Residual: use in a hot room, so the instruction states the ambient assumption rather than quoting a universal one. | Instructions, packaging |
| Skin that is already irritated or broken | Risk analysis plus general clinical context | Usage limit: do not apply to broken or irritated skin. Residual: a user with a condition they have not identified — hence the referral sentence. | Instructions, support script |
| Photosensitising medication | No product-specific evidence | Referral, not restriction: advise consulting a clinician before use. The absence of evidence is why it is a referral and not a contraindication. | Instructions, FAQ |
| Charging or battery fault | Electrical safety testing and fault injection | Protection circuit and approved charger. Residual: a third-party supply, so the instruction names the approved one and states the consequence of substituting. | Instructions, packaging |
| Cleaning with aggressive solvents | Material compatibility testing | Usage limit: name the permitted agents and the number of cycles tested. Residual: surface degradation the user cannot see. | Instructions |
| Sharing between users | No established evidence either way | Hygiene instruction only, with no medical claim attached to it in either direction. | FAQ, instructions |
| Wearing it longer than directed | Timer behaviour and thermal data | Design control: automatic shut-off. Residual: repeat sessions, so the instruction states a maximum per day rather than a recommended one. | Instructions, product page |
The rows above illustrate the pattern rather than prescribe content. Every entry in your own table has to come from your own file, for your own configuration — which is the whole difference between a traceability table and a tidier copy of somebody else’s list.
3. A Warning Is Only One of Four Answers
When a hazard turns up, the reflex is to write a warning about it. Four responses are available, in descending order of preference, and choosing the wrong one is how a device ends up relying on text to solve an engineering problem.
- A design control. Remove or reduce the hazard so the warning is no longer needed. A shield, a timer limit, a connector that only accepts the approved supply. The strongest option and always the first one to consider.
- A usage limit. State the boundary of what has been validated — the ambient temperature assumed, the maximum session per day, the cleaning agents tested. A limit is a fact about the evidence, not a preference.
- Additional validation. Sometimes the honest answer is that nobody knows yet. That is a test to commission, not a sentence to write.
- A referral. When the question is about a person rather than a product, the answer belongs with a clinician. A referral is the correct output for an individual medical question, and it is not an admission that the product is unsafe.
What none of these four licenses is declaring an entire population contraindicated without evidence. That move feels cautious and is not: it is an unsupported statement about a group of people, it will be repeated by distributors as fact, and it removes a product from customers on the strength of a guess. Where the evidence stops, the referral belongs — not a contraindication.
4. Keep It Consistent, and Give Support a Route Out
A warning is only as strong as its weakest copy. The manual, the packaging, the website FAQ, the distributor sheet and the support macros have to agree, because the version a customer screenshots is whichever one they happened to read[2].
- One controlled source, five derived channels. Packaging, page, FAQ, distributor copy and scripts are all outputs of the approved instruction set, not parallel drafts of it.
- A change trigger that reaches the risk file. A new safety signal, a complaint pattern or a component change should raise one question: does this affect the risk analysis, and therefore the instruction? If no one owns that question, the answer is always no.
- A documented escalation route. Support staff need a named path for complaints and possible adverse events, and permission to use it. Improvising a medical response in a chat window is the failure mode this prevents.
- A review date. Warning sets without a review trigger become permanent by default, including the ones written for a product you no longer make.
If you are buying rather than building, the same logic becomes a list of documents: the risk-management summary or traceability table, the applicable instructions and warnings, the relevant test reports, the change-control process and the complaint-handling procedure — each confirmed against the model you are actually considering[3]. A supplier who cannot produce the first item usually cannot produce the rest in a form you can use.
Reviewing a supplier’s risk file and warnings before launch? Visit our
Custom Light Therapy Manufacturing Page.
5. Partner With Rainbow Technology for Custom LED Devices
A traceability table is only useful if the manufacturer can populate it for the model you are buying. Rainbow Technology runs ODM and OEM programmes from our Shenzhen facility and supplies:
- A risk-management summary per model, with each control linked to the hazard it addresses and the record that verifies it.
- Approved warnings and instruction text as controlled documents, so every channel can quote rather than paraphrase.
- A distinction we will state plainly: where a question is a referral, we will not convert it into a contraindication to look thorough, and where a restriction has no basis, we will say so.
- Change-control and complaint-handling processes that show who decides when a new signal changes a warning, and what happens to the documents afterwards.
- Sample and small-batch production from 500 units, with a stated capacity of 100,000 units per month; both figures depend on model, configuration, packaging and schedule, and are confirmed in a formal quotation.
- Compliance documentation matched to the exact model for your target market. Where a model holds a 510(k) record we provide the K-number so you can check its scope in the FDA’s public database; clearance is not the same as FDA approval, and the scope differs from model to model.
6. References & External Links
[1] International Organization for Standardization.
ISO 14971:2019 Medical devices — Application of risk management to medical devices. Provides the process for identifying hazards, estimating and evaluating risk, controlling it, and monitoring the effectiveness of those controls — the structure a warning-to-risk traceability table follows.
[2] International Organization for Standardization.
ISO 20417:2026 Medical devices — Information to be supplied by the manufacturer. Second edition, published March 2026, replacing ISO 20417:2021; it sets the general requirements for labelling, packaging, marking and accompanying documentation, including warnings and instructions for use.
[3] International Organization for Standardization.
ISO 13485:2016 Medical devices — Quality management systems — Requirements for regulatory purposes. The document-control and change-control requirements that keep a warning set under management rather than in a shared drive; incorporated by reference in the FDA Quality Management System Regulation that took effect on 2 February 2026.
