info@redvancetech.com +86 135 3679 1558 OEM / ODM Manufacturer · Shenzhen
 
Compliance / Technical Documentation

An evidence package proves what the device does — irradiance, spectrum, thermal behaviour. A technical file is what a regulator reviews before granting a registration. It contains the evidence, plus the structure around it: risk management, design controls, a quality management system, labelling, and post-market planning. As more buyers in this category pursue market registrations beyond general wellness positioning, the technical file is becoming part of what a serious OEM partner is expected to supply or support — and the gap between “we have test reports” and “we have a registration-ready file” is substantial.

RedVance manufactures red light therapy panels. This guide describes what a registration-ready technical file contains as an educational overview for buyers evaluating OEM capability — not a statement that RedVance holds any specific registration or ISO 13485 certification.

01

What goes in a technical file

ElementWhat it contains
Device descriptionWhat the device is, its intended use, how it works, its classification rationale
Risk management fileHazard identification, risk estimation, risk controls, residual risk assessment — per ISO 14971
Design and development recordsDesign inputs, outputs, reviews, verification and validation — the design history
Performance testingThe evidence package: irradiance, spectrum, uniformity, thermal, EMC, electrical safety
Manufacturing informationProcess descriptions, process validation, quality controls
LabellingDevice labels, instructions for use, packaging, reviewed against regulatory requirements
Post-market planningHow safety and performance will be monitored after market entry

Row four — performance testing — is the evidence documentation package covered in our evidence package hub. The other six rows are the difference between “we have test data” and “we have a file a regulator can review.”

02

ISO 13485: the quality system behind the file

ISO 13485 is the international standard for quality management systems specific to medical devices. It provides the organisational framework a technical file sits inside — design controls, document management, supplier qualification, corrective and preventive actions, traceability.

Without a quality management system behind it, a technical file is a collection of documents rather than evidence of a controlled process. The distinction matters because a regulator reviewing a technical file is not only assessing whether the documents exist but whether they were produced and maintained within a system that ensures their accuracy and currency.

A significant recent development: FDA’s Quality Management System Regulation (QMSR) has incorporated ISO 13485:2016 by reference into 21 CFR Part 820, which means the US market and international standards are now substantially aligned on what a quality system for medical devices should look like. For a manufacturer building a QMS for multi-market access, this alignment reduces the number of separate frameworks to satisfy.
03

ISO 14971: risk management as a core element

ISO 14971 is the standard for applying risk management to medical devices. It covers the full sequence: hazard identification, risk estimation, risk evaluation, risk control measures, and residual risk assessment. The risk management file it produces is not an optional appendix — it is a core element of the technical file, and ISO 13485 explicitly requires risk management to be integrated throughout product realisation.

For a red light device, risk management addresses questions such as:

  • What are the optical, electrical and thermal hazards, and how is each controlled?
  • What happens under foreseeable misuse — wrong distance, blocked ventilation, extended sessions?
  • What residual risks remain after controls, and are they acceptable?

These connect directly to the engineering content already on this site — thermal behaviour in our thermal drift guide, eye safety considerations in our face mask guide, and electrical safety in our EMF, flicker and heat guide. Risk management turns those engineering considerations into a formal, documented framework.

04

MDSAP: one audit, multiple markets

The Medical Device Single Audit Program allows a single quality system audit to satisfy the requirements of five regulatory authorities: TGA (Australia), ANVISA (Brazil), Health Canada, MHLW and PMDA (Japan), and FDA (United States). It uses ISO 13485 as its foundation, with country-specific requirements mapped on top.

For a manufacturer building a quality system with multi-market access in mind, MDSAP is the mechanism that makes “build once, register in several markets” practically achievable — rather than maintaining separate quality system certifications for each market. The technical file itself can be structured similarly: a core set of documentation serving multiple markets, with market-specific supplements where a jurisdiction has unique requirements.

Per-market regulatory requirements are indexed in our market-by-market compliance hub.

05

The supplier doesn’t need a registration — the brand does

A common confusion worth clearing up: the registration is typically held by the brand or its authorised representative in the target market, not by the manufacturing supplier. What the supplier needs to provide is the technical documentation that supports the brand’s submission — design records, risk management, test reports, manufacturing specifications — complete and accurate enough that a regulatory consultant can work from it.

A supplier who holds its own registration in a market has demonstrated that its documentation and quality system can survive regulatory review, which is a strong signal. But a supplier without one can still supply registration-ready documentation — the question is whether the file exists and is complete, not whose name is on the registration.

The clearance pathway implications are in our 510(k) predicate strategy guide, and the cleared-versus-registered distinction in our FDA 510(k) verification guide.

06

What to ask a supplier about technical file readiness

  1. “Does a risk management file exist for this device, per ISO 14971?” Not a general statement about safety — a specific file.
  2. “Are design and development records maintained under a controlled process?” Design inputs, outputs, reviews, changes — documented and version-controlled.
  3. “Does your quality management system conform to ISO 13485, and is it certified?” Certification by an accredited body is the strongest signal; a documented system without certification is a weaker one.
  4. “Can the technical documentation support a submission in our target market, or would it need to be developed?” “Ready” versus “could be developed” are different timelines and costs.
  5. “Has this documentation supported a registration for any other brand or in any other market?” Prior use is evidence of completeness.
The answers to these questions separate three tiers of supplier: one with a certified QMS and documentation that has already supported a registration, one with documentation that exists but has not been tested by a regulator, and one that would need to build the documentation from scratch. The tier determines the timeline and cost for the brand’s registration project, not just the price of the hardware.
07

Version control: the detail that trips most people up

A technical file is not a set of documents written once. It is a living system that must track every change to the device — a different LED bin, a revised driver, a firmware update, a packaging change — and ensure the file reflects what is currently being manufactured, not what was manufactured when the file was first written.

  • Every document version-controlled with a change history.
  • Changes assessed for their impact on risk management and testing.
  • The file always describing current production, not the original design.

This is the operational discipline that distinguishes a quality management system from a collection of PDFs. It also connects directly to the dose table maintenance covered in our dose table guide — a change to a component can change what the device delivers, which means the dose table and the technical file both need updating.

08

The technical file checklist

  1. Device description and intended use clearly stated.
  2. Risk management file per ISO 14971 — hazards, controls, residual risk.
  3. Design and development records — inputs, outputs, reviews, verification, validation.
  4. Performance testing — the evidence documentation package.
  5. Manufacturing process documentation and quality controls.
  6. Labelling reviewed against target market requirements.
  7. Post-market surveillance plan.
  8. Quality management system documented and, ideally, certified to ISO 13485.
  9. Version control maintained so the file describes current production.
  10. Regulatory consultant engaged for each target market before submission.

This is the second of four beyond-hardware layers covered in our beyond hardware hub. Terms are defined in our glossary.

Where RedVance currently sits: we maintain technical documentation for our panel range. What that documentation currently covers and where gaps exist relative to a full registration-ready file for a specific market is something we can discuss specifically for your product and target market — rather than claiming readiness we haven’t demonstrated. Our OEM and ODM pages describe our current production and documentation scope.

Frequently asked questions

What is a technical file for a red light device?

A technical file is the structured documentation set that a regulatory authority reviews when assessing a device for market registration or clearance. It typically includes a device description, risk management documentation, design and development records, verification and validation testing, labelling, and evidence of a quality management system. It is the regulatory submission package, distinct from the performance evidence package that proves what the device physically delivers.

How is a technical file different from an evidence documentation package?

An evidence package contains performance data — irradiance, spectrum, uniformity, thermal behaviour — that proves what the device does. A technical file contains that data plus the surrounding structure a regulator requires: risk management, design controls, a quality management system, labelling review and post-market surveillance planning. The evidence package is one input to the technical file, not a substitute for it.

What is ISO 13485 and why does it matter for a technical file?

ISO 13485 is the international standard for quality management systems specific to medical devices. It provides the organisational framework — design controls, document management, supplier qualification, corrective actions — that a technical file sits inside. Without a quality management system behind it, a technical file is a collection of documents rather than evidence of a controlled process.

What is ISO 14971 and how does it relate to a technical file?

ISO 14971 is the standard for applying risk management to medical devices. It covers hazard identification, risk estimation, risk evaluation, risk control and residual risk assessment. The risk management file it produces is a core element of the technical file, and ISO 13485 explicitly requires risk management to be integrated throughout product realisation.

Does a supplier need its own device registration to supply a registration-ready technical file?

Not necessarily. The registration is typically held by the brand or its authorised representative in each market, not by the manufacturing supplier. What the supplier needs to provide is accurate, complete technical documentation — design records, risk management, test reports, manufacturing specifications — that a regulatory consultant can work from to support the brand’s submission.

Can one technical file support registration in multiple markets?

The core documentation — design records, risk management, testing — can be structured to serve multiple markets, with market-specific supplements added for each jurisdiction’s unique requirements. This is part of the value of building the file to recognised international standards rather than to one market’s format alone. The MDSAP audit programme, which uses ISO 13485 as its foundation, is specifically designed to allow one quality system audit to satisfy multiple regulators.

Ask what documentation exists today

Tell us your target market and intended regulatory position. We’ll tell you specifically what technical documentation we currently hold for the relevant product, what gaps exist, and where a regulatory consultant would need to start — rather than claiming a readiness we haven’t verified for your specific situation.

Discuss technical file readiness →
Educational content for B2B product planning. Not legal, regulatory or quality-system advice, and not a statement that RedVance holds ISO 13485 certification, MDSAP certification, or any specific market registration. Quality system standards, technical file requirements and registration procedures vary by market, device classification and intended use, and change over time. Engage a qualified regulatory consultant for your specific device, claims and target markets.

Leave a Reply

Your email address will not be published. Required fields are marked *