MDR Rule 16: Two Products, Two Hazard Tests, One Rule

EU MDR Annex VIII, Chapter III, Rule 16 reads to most teams as a single line item: “disinfecting devices, Class IIa or IIb.” It is not one rule with one outcome. It is one rule governing two distinct product categories, each with its own default class and its own exception — and the two branches get confused often enough that it is worth separating them before a Notified Body does it for you.

One rule, two product categories

Rule 16 is built around intended purpose, the same way most of Annex VIII's special rules are. It covers devices intended specifically for disinfecting, cleaning, rinsing, or hydrating contact lenses, and — in a separate branch — devices intended specifically for disinfecting or sterilising other medical devices. Nothing about the chemistry ties the two branches together. A hydrogen peroxide system sold to disinfect contact lenses and a hydrogen peroxide system sold to disinfect a reusable surgical instrument are evaluated against different branches of the same rule, with different outcomes.

The contact lens branch: Class IIb, no exceptions

Any product intended specifically to disinfect, clean, rinse, or hydrate contact lenses defaults to Class IIb. Rule 16 does not carve out a lower class for a single-step rinsing solution, a lens case with a stated disinfecting function, or a one-bottle multipurpose system — the branch does not distinguish by mechanism of action, number of steps, or how the product is packaged. The common misread is to assume a “simpler” lens-care product, one that only rinses rather than disinfects, lands in a lower class by default. If the labeled purpose includes disinfecting, cleaning, rinsing, or hydrating a contact lens, the branch applies and the floor is Class IIb.

The device-disinfectant branch: IIa, until it is the last step before an invasive device

Products intended specifically for disinfecting or sterilising other medical devices default to Class IIa. Rule 16 moves that default to Class IIb only when the product is specifically intended for disinfecting invasive devices as the final step in their processing before use — a washer-disinfector cycle that closes out an endoscope's reprocessing path, for example, or a chemical sterilant positioned as the terminal step for a reusable invasive instrument. A disinfectant used earlier in a multi-step reprocessing workflow, or one intended for non-invasive reusable devices, stays in Class IIa.

The two branches do not share an exception. A fact that upgrades a device-disinfectant product to IIb — being the terminal step before an invasive device — has no equivalent downgrade on the contact lens side, and a lens-care argument has no bearing on a reprocessing chemistry file. Why the two branches have to be assessed separately

Where this goes wrong

• Borrowing a lens-care classification for a reprocessing product. A multipurpose contact lens solution's Class IIb file is sometimes used as a template for an unrelated device-disinfectant product, when the device-disinfectant branch's own IIa default — and its separate invasive-device exception — never gets evaluated.
• Missing the invasive-device endpoint question. A washer-disinfector or chemical sterilant positioned generically, without confirming whether it is specifically intended as the terminal step for an invasive device, can carry an IIa file that should be IIb.
• Carrying forward an MDD-era file unexamined. A classification self-declared under the old directive's numbering and never re-opened against MDR Annex VIII's current branch split is a gap-assessment finding waiting to surface, not a settled question.
• Treating the rule as chemistry-driven. Rule 16 classifies on intended purpose. A general surface or hand disinfectant with no device-specific intended use falls outside MDR altogether and is typically a Biocidal Products Regulation matter, not a Rule 16 one.

What this means for the sterility assurance and ophthalmic device teams carrying both

Manufacturers who sit across both branches — a combination ophthalmic and surgical-reprocessing portfolio, or a contract manufacturer producing both lens-care chemistry and device disinfectants — are the ones most likely to let one branch's logic bleed into the other. The fix is procedural, not technical: treat Rule 16 in your EU MDR classification gap assessment as two separate rules that happen to share a number, run the invasive-device endpoint question explicitly for every device-disinfectant SKU, and keep the lens-care branch's IIb floor from drifting into reprocessing-chemistry files where it does not belong. The same discipline that keeps sterile and single-use device files defensible under Annex I applies here: the classification argument has to survive a Notified Body reading the intended purpose statement cold, not the manufacturer's internal shorthand for what the product does — the same branch-by-branch reading that Rule 20's inhalation-device split rewards over a single-number shortcut.