Industrial cameras in medical equipment: who owns compliance

A purchase order for a benchtop analyzer lands on your desk with one open line: a flammability certificate for the camera. The camera datasheet has no such line, and the vendor will not issue one. That is not an oversight. Industrial machine-vision cameras are qualified as components, their conformity assessment covers the delivered camera's electronics, and neither complete-camera flammability testing nor medical certification is part of it. If you build cameras into medical or laboratory instruments, the split below is yours to manage: who owns which standard, what evidence to collect from the camera vendor, and how to close the technical file without stalling the project.

What the camera's own paperwork covers

An industrial camera is delivered as electronic equipment, and its paperwork says exactly that: CE marking for electromagnetic compatibility and restricted substances on the EU market, FCC conformity on the US market. The paperwork never includes a flammability assessment of the complete camera, and no medical-device certification appears anywhere on it. No medical or laboratory standard has been applied to the camera, because at delivery it is a component, not an instrument.

Two boundaries follow. The declarations describe the camera as delivered: housing closed, firmware as supplied, I/O wired as the manual shows. Anything you add — a custom harness, modified firmware, a dismantled housing — falls outside the component assessment and becomes yours to document. Buy the camera as the component it is, and plan from day one for the assessment you will run yourself.

Why there is no camera-level flammability certificate

Fire-hazard work in the IEC 60695 series asks questions of materials and of finished equipment: whether an internal fault ignites the enclosure, whether the enclosure contains a fire, how much the materials inside contribute. Those questions have answers only for a finished instrument, with its own enclosure, cable entries and power supply. A camera vendor cannot certify your fire enclosure, because your enclosure is the one part they never build.

So the direct answer to the certificate request is no: complete-camera flammability certification is not part of the standard conformity assessment, and there is no standard document to issue. What a vendor can do is review a written request and provide the construction and material information available for the camera, for use inside your own assessment. Send that request through the contact page while parts are still swappable — the reply is most useful before the drawing freezes.

Who owns what

The principle behind the table is the one the standards encode: the manufacturer of the complete system answers for the finished product, and that answer covers every assembly inside it, cameras included. A component declaration is an input to your file. It is never the file.

Choose the product standard from intended use, not from the parts list. Imaging on or against the patient — a surgical site, procedure guidance — puts the instrument under IEC 60601-1. A bench-run analyzer with no patient connection falls under IEC 61010-1, the safety standard for measurement, control and laboratory equipment. The camera changes neither answer: in both cases its job is to deliver images and the documentation your assessment consumes.

If the split still feels abstract, the guide to what a machine vision system is and how to choose one draws the same boundary from the buying side: the camera is a part of a machine you specify, and the machine is what gets assessed.

Camera form factor and the enclosure you certify

Two camera forms sit inside an instrument enclosure, and they differ more in compliance work than in image quality.

A housed camera — the classic C-mount body across the area scan cameras range — arrives as a closed metal assembly. Metal rather than plastic is the convention for machine-vision housings, which reduces the fire load your enclosure has to manage; the assessment still belongs to you. Mount the camera, pass its cable through a gland or connector plate, and keep fire and ingress questions at the instrument boundary. This is the default for benchtop analyzers, and the camera finder filters it by sensor, resolution, interface and shutter.

A bare board camera has no housing at all, so the instrument enclosure is at once the fire enclosure, the EMC enclosure and the ingress enclosure. Such builds are routine in compact instruments: choose sensor and footprint in the board-level cameras category, then design fixing, spacing and cable exits as part of the enclosure, not as an afterthought. When that is your build, buy the board directly:

The board level camera selection for embedded vision machines guide walks sensor, mount and interface choices, and the board camera evaluation checklist for inspection systems turns a shortlist into a scored comparison.

For a standard housed build, these are the component cameras used in the examples below:

What the datasheet gives the technical file

A camera datasheet carries usable engineering numbers: sensor format, resolution, pixel size, shutter type, interface, frame rate. The LS-BCM-0056 board camera, for example, prints 1.6 μm × 1.6 μm pixels on a 1/2" format — exactly the kind of figure that anchors the optical budget in your integration file.

No datasheet carries safety data: the flame class of a plastic part, a leakage-current contribution, anything keyed to the finished instrument. Those numbers exist only in the assessment you run, which is why the certificate request belongs to your compliance process rather than to the camera catalog.

The printed rows for the camera in the worked example below:

As printed in the product data sheet.

Numbers you compute yourself belong in the file too, because the assessment covers cables and power alongside the camera. Take the stream budget of the LS-CMR-0166 USB3 camera as the analyzer's imaging component: 4000 × 3000 pixels at 30 frames per second. Assume an 8-bit monochrome stream; the arithmetic scales linearly with bit depth.

USB3 moves 5 Gbit/s nominally, so the stream uses 2.88 Gbit/s of the nominal 5 Gbit/s — 58 %, leaving room for protocol overhead. One frame costs 4000 px × 3000 px × 8 bit = 96 Mbit, and over GigE's 1 Gbit/s that is at most 10.4 frames per second before overhead. The catalog agrees: the LS-CMR-0053, the same IMX226 sensor on GigE, runs at 9 fps.

A procurement path that closes the file

1. Write the intended-use sentence — patient-connected or bench-run — and let it select IEC 60601-1 or IEC 61010-1.
2. List every assembly inside the fire enclosure: camera, lens, lights, cables, connectors, power supply.
3. Request, in writing, the construction and material information available for the chosen camera, and file the reply.
4. Keep the camera in its as-delivered configuration: closed housing, supplied firmware, I/O wired as the manual shows. For bare-board builds, buy a board-level product and route its wiring with the practice in the camera GPIO wiring guide.
5. Recompute the stream budget whenever frame rate or bit depth changes, and re-check interface and cable against it.

When the component answer is wrong

Private labelling. Resell the camera under your own name as a module or spare, and you have become the component manufacturer; its documentation burden moves to you.

Home use. IEC 60601-1-11 extends medical electrical requirements to equipment used in the home, where mains quality, temperature and cleaning are uncontrolled. A camera inside a home-care device inherits those requirements through your assessment, and the environment your documentation describes must be the home, not the hospital.

Standalone sale. Sell the camera-with-lens module as a device in its own right, and someone must hold device-level conformity for it. The component declaration will not stretch that far.

Checks before you order

• Intended-use sentence written, product standard chosen from it — every later request hangs on this one line.
• Fire-enclosure drawing with every assembly shown: camera, cable entry, lights, power supply — the assessment is only as complete as this list.
• Material and construction request sent for the chosen camera, reply filed — component documentation enters your file, not the other way round.
• Camera in as-delivered configuration, or a board-level product bought deliberately — the declarations must describe what is actually inside the enclosure.
• Stream budget computed for the chosen frame rate and bit depth, interface and cable chosen to fit — a bandwidth problem found late looks like an EMC problem.
• Declarations for camera, lens, lights and power supply collected in one place — the technical file is assembled, not written.

Shortlist the imaging component, send the documentation request while parts are still swappable, and let the enclosure design carry the safety argument. The configurator below walks camera, lens, light and controller in order, so the interface and bandwidth arithmetic above stays consistent across the chain.