--- title: MDR for Accessories: When Your Add-On Product Becomes a Regulated Device description: How EU MDR regulates medical device accessories. Definition, classification rules, and compliance requirements for startups building add-on products that work with medical devices. authors: Tibor Zechmeister, Felix Lenhard category: MDR Fundamentals & Regulatory Strategy primary_keyword: canonical_url: https://zechmeister-solutions.com/en/blog/mdr-accessories-add-on-product-regulated-device source: zechmeister-solutions.com license: All rights reserved. Content may be cited with attribution and a link to the canonical URL. --- # MDR for Accessories: When Your Add-On Product Becomes a Regulated Device *By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.* You build a product that works alongside a medical device. Maybe it is a charging station for a wearable monitor. A mounting bracket for a surgical display. A sensor adapter that connects to an existing diagnostic system. A software module that adds functionality to an existing medical device platform. The question every startup in this position asks: "Is my add-on product a medical device?" Under MDR, the answer may be yes — even if your product does not have a medical purpose of its own. ## The MDR Definition of Accessory MDR Article 2(2) defines an accessory for a medical device as an article which, while not being itself a medical device, is intended by its manufacturer to be used together with one or several particular medical device(s) to specifically enable the medical device(s) to be used in accordance with its/their intended purpose(s) or to specifically and directly assist the medical functionality of the medical device(s) in terms of its/their intended purpose(s). Breaking this down: **"Not being itself a medical device"** — the article does not independently have a medical intended purpose. It is not a device on its own. **"Intended by its manufacturer to be used together with"** — the manufacturer (you) designs and markets it for use with a specific medical device or devices. Intent is key. **"One or several particular medical device(s)"** — the connection is to specific devices, not to medical devices in general. **"Specifically enable the medical device to be used in accordance with its intended purpose"** — the accessory makes it possible for the medical device to function as intended. Without the accessory, the device cannot be used as intended. **"OR specifically and directly assist the medical functionality"** — the accessory does not just generally support the device; it directly assists its medical function. ## Why This Matters: Accessories Are Regulated as Devices Here is the critical regulatory consequence: MDR Article 2(2) continues by stating that accessories shall be considered as medical devices in their own right. This means that if your product meets the accessory definition, it is subject to the full MDR requirements — the same classification rules, the same conformity assessment procedures, the same technical documentation requirements, the same post-market obligations as any other medical device. Your charging station, mounting bracket, sensor adapter, or software module — if it is an accessory under this definition — needs a CE mark. ## Classification of Accessories MDR Annex VIII, Rule 22 provides specific guidance on accessory classification: accessories shall be classified in their own right, separate from the device with which they are used. The classification of an accessory is based on the accessory's own characteristics and intended use, not automatically on the classification of the device it accompanies. However, in practice, accessories for higher-risk devices tend to be classified at higher risk levels because their failure could affect the safety and performance of the associated device. Key points on accessory classification: - **Classify the accessory independently** using the Annex VIII rules based on what the accessory is and does - **Consider the risk to the patient** if the accessory fails — does failure affect the associated device's safety or performance? - **Software accessories** follow the software classification rules (Rule 11) ## Is Your Product an Accessory? The Decision Framework ### Question 1: Is it intended to be used with a specific medical device? If your product is a general-purpose item (a standard power supply, a generic monitor mount, a commodity network cable), it is probably not an accessory. Accessories are designed for and marketed for use with specific medical devices. If your product is specifically designed, marketed, or labeled for use with a particular medical device or class of medical devices, it may be an accessory. ### Question 2: Does it enable the device to be used for its intended purpose? If the medical device cannot function for its intended purpose without your product, your product likely "enables" the device's use and meets part of the accessory definition. Example: A proprietary electrode cable that connects a patient to a monitoring device. Without the cable, the monitor cannot be used for its intended purpose. The cable is almost certainly an accessory. ### Question 3: Does it directly assist the medical functionality? If your product enhances or directly supports the medical device's clinical function — not just its general usability or convenience — it likely "directly assists" the medical functionality. Example: A software module that provides additional diagnostic algorithms for an existing medical device platform. The module directly assists the device's medical functionality (diagnosis). Counter-example: A carrying case for a portable medical device. The case protects the device during transport but does not enable its medical function or directly assist its medical functionality. A carrying case is unlikely to be an accessory under MDR (though it may need to meet other requirements for packaging or transport). ### The Gray Zones Many products fall in gray zones: **Power supplies and chargers:** A standard power supply is probably not an accessory. A custom power supply designed specifically for a medical device, with specific safety features required by the device's design, might be. The question is whether it specifically enables the device's intended use. **Software platforms and integrations:** A general-purpose cloud infrastructure is not an accessory. A specific integration module that processes data from a medical device to enable its clinical function likely is. **Mounting and installation hardware:** A generic shelf bracket is not an accessory. A specifically designed mounting system that positions a surgical device at the correct angle for its intended clinical use might be. When in doubt, err on the side of treating the product as an accessory. The consequences of wrongly classifying an accessory as a non-medical product are far more severe than the consequences of over-compliance. Tibor's approach: "When a startup asks me whether their product is an accessory, I ask two questions: What specific medical device is it used with? And what happens to the patient if your product fails? If the answer to the second question involves any possibility of patient harm — because the associated device cannot function properly without your product — then we are almost certainly looking at an accessory." ## Practical Implications for Startups ### You Need a Full MDR Regulatory Path If your product is an accessory, you need: - Classification per Annex VIII - Conformity assessment per Article 52 (including Notified Body if Class IIa or higher) - Technical documentation per Annex II - QMS per Article 10(9) / ISO 13485 - Clinical evaluation per Article 61 - Post-market surveillance system - Vigilance reporting capability - EU Declaration of Conformity - CE marking - EUDAMED registration and UDI This is the full regulatory path, identical to any medical device of the same class. ### Your Technical Documentation Must Address the Interface Your technical documentation must specifically address how your accessory interacts with the associated medical device(s): - Define the interface specifications (physical, electrical, software) - Analyze risks arising from the interaction - Verify and validate the accessory's performance when used with the associated device - Address compatibility across device versions/variants ### Clinical Evidence for Accessories The clinical evaluation for an accessory must demonstrate that the accessory does not adversely affect the safety and performance of the associated medical device. This may require: - Verification testing demonstrating compatibility and safety - Literature review addressing the type of accessory and its potential risks - If the accessory introduces new risks, clinical evidence addressing those risks ### Coordination with the Device Manufacturer If you are building an accessory for another company's medical device, coordination matters: - You are the manufacturer of the accessory and bear full regulatory responsibility for it - The associated device manufacturer has their own regulatory obligations - You may need technical information about the device to properly assess compatibility and risk - Changes to the associated device may affect your accessory's compliance This creates a business relationship consideration. If the device manufacturer changes their product, your accessory may need updating. If the device manufacturer withdraws their product from the market, your accessory loses its associated device. ## Common Startup Scenarios ### Scenario 1: Software Add-On to an Existing Medical Device Platform You build a software module that adds AI-powered analysis capability to an existing diagnostic imaging system. The module runs on the same platform and accesses the same patient data. **Analysis:** This is likely either an accessory (if it directly assists the medical functionality of the platform) or a standalone medical device in its own right (if it independently provides diagnostic information). Either way, it is regulated under MDR. Classification follows Rule 11. ### Scenario 2: Hardware Adapter Connecting Two Medical Devices You build a physical adapter that allows a sensor from manufacturer A to work with a monitoring system from manufacturer B. **Analysis:** This is likely an accessory if it enables the sensor or the monitor (or both) to be used for their intended purpose. The adapter's failure could affect patient monitoring, so the risk assessment must consider this. ### Scenario 3: Specialized Consumable for a Medical Device You manufacture a specialized reagent or test strip designed for use with a specific diagnostic device. **Analysis:** This may be an accessory or an independent medical device (or IVD), depending on whether it has its own diagnostic intended purpose. If it is a reagent for an in vitro diagnostic device, IVDR may apply instead of MDR. ### Scenario 4: Cleaning or Reprocessing Equipment You build an automated cleaning system specifically designed for reprocessing reusable surgical instruments from a specific manufacturer. **Analysis:** This could be an accessory if it specifically enables the reusable instruments to be used in accordance with their intended purpose (safe reuse requires proper reprocessing). Classification and regulatory requirements would follow from the accessory analysis. ## Avoiding the Accessory Trap Some startups discover mid-development that their product is an accessory and must comply with MDR — when they had planned and budgeted for a non-regulated product. To avoid this: 1. **Assess the regulatory status early.** Before you start development, analyze whether your product could be an accessory under MDR. This analysis should be one of your first regulatory activities. 2. **Consider your intended purpose carefully.** Your marketing claims and labeling determine intent. If you market your product specifically for use with medical devices and make claims about enabling or assisting medical functionality, you are building the case for accessory status. 3. **Consult early if uncertain.** A regulatory assessment from an expert costs a few thousand euros. Discovering the accessory issue at month 18 of development costs far more. ## The Bottom Line Accessories under MDR are medical devices. If your product specifically enables or directly assists the medical functionality of a medical device, it is subject to the full MDR regulatory framework — classification, conformity assessment, technical documentation, clinical evaluation, and everything else. For startups building products that work alongside medical devices, the accessory question is among the first regulatory questions to answer. Get it right early, and you can plan your development, budget, and timeline accordingly. Get it wrong, and you face the painful choice between complying late (expensive and slow) or withdrawing a non-compliant product from the market. The rule is simple: when in doubt, assess. The cost of an early regulatory assessment is always less than the cost of a late-stage discovery. --- *This post is part of the [MDR Fundamentals & Regulatory Strategy](https://zechmeister-solutions.com/en/blog/category/mdr-fundamentals) cluster in the [Subtract to Ship: MDR Blog](https://zechmeister-solutions.com/en/blog). For EU MDR certification consulting, see [zechmeister-solutions.com](https://zechmeister-solutions.com).*