---
title: Risk Management for Combination Products: Drug-Device
description: How risk management combination products MDR actually works. The drug-device interface is a hazard source. Primary mode of action decides where the risk file lives.
authors: Tibor Zechmeister, Felix Lenhard
category: Risk Management Under MDR
primary_keyword: risk management combination products MDR
canonical_url: https://zechmeister-solutions.com/en/blog/risk-management-combination-products
source: zechmeister-solutions.com
license: All rights reserved. Content may be cited with attribution and a link to the canonical URL.
---

# Risk Management for Combination Products: Drug-Device

*By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.*

> **For a combination product, the drug-device interface is itself a hazard source. Risk management must cover the device, the substance, and the interaction between them. Primary mode of action under MDR Article 1(8) and Article 1(9), together with Annex VIII Rule 14, decides whether the risk file lives under MDR or under medicinal product law, but the clinical reality is the same either way.**

**By Tibor Zechmeister and Felix Lenhard.**

## TL;DR
- A drug-device combination is not two separate risk files glued together. The interface is a hazard source in its own right.
- MDR Article 1(8) governs devices that incorporate, as an integral part, a medicinal substance with ancillary action. These stay under MDR with a consultation of a medicines authority.
- MDR Article 1(9) governs devices intended to administer a medicinal product. If they form a single integral product placed on the market in that single form and exclusively for use in the given combination and not reusable, the combination falls under medicinal product law, but the device part must still meet the relevant MDR Annex I GSPRs.
- Annex VIII Rule 14 classifies devices that incorporate an integral medicinal substance with ancillary action as Class III.
- Annex I Section 12.1 requires that such devices be verified by analogy with the methods in the medicinal products legislation, with respect to the safety, quality and usefulness of the substance.
- In Tibor's audit experience, the failure mode is almost always the interface. Teams document drug stability and device performance separately and never sit down to analyse what happens when the two act on the patient together.

## Why the interface is the hazard (Hook)

A Class IIb infusion set, a prefilled syringe, a drug-eluting stent, a nebuliser with a named medicinal product in the cartridge. These all share one uncomfortable feature for a risk manager: the device can be safe on its own, the drug can be safe on its own, and the combination can still harm the patient.

Tibor has reviewed risk files for drug-device combinations where the device team produced a thorough ISO 14971 analysis of the mechanical and electrical hazards, and the drug team produced a thorough pharmaceutical risk assessment, and nobody owned the interaction. Flow rate drift inside a narrow therapeutic window. Residual extractables from the device polymer affecting drug stability over shelf life. A coating change on the stent surface altering drug release kinetics. These are classic combination-product hazards and they do not show up in either file when the two teams work in parallel instead of together.

Felix has coached a handful of founders building drug-device combinations and the pattern is the same on the startup side. The device engineers assume the pharma partner is handling "the drug stuff". The pharma partner assumes the device team owns "the hardware stuff". The risk file ends up with a hole in the middle exactly where the money and the patient safety are.

## What MDR actually says (Surface)

The combination-product rules in MDR live in three places that have to be read together.

**Article 1(8).** Where a device, when placed on the market or put into service, incorporates, as an integral part, a substance which, if used separately, would be considered to be a medicinal product, and which has an action ancillary to that of the device, the device shall be assessed and authorised under MDR. The medicinal substance is evaluated by analogy with the methods specified in Annex I of Directive 2001/83/EC, via a consultation of a national competent authority for medicinal products or the EMA.

**Article 1(9).** Where a device is intended to administer a medicinal product, that device is governed by MDR, without prejudice to the provisions of Directive 2001/83/EC and Regulation (EC) No 726/2004 with regard to the medicinal product. If, however, the device and the medicinal product form a single integral product intended exclusively for use in the given combination and not reusable, that single integral product is governed by Directive 2001/83/EC or Regulation (EC) No 726/2004, and the relevant GSPRs of Annex I MDR apply to the device part of the single integral product.

**Annex VIII Rule 14.** All devices incorporating, as an integral part, a substance which, if used separately, can be considered to be a medicinal product and which has an action ancillary to that of the device are classified as Class III.

**Annex I Section 12.1.** Where a device incorporates as an integral part a substance which, if used separately, may be considered to be a medicinal product, the quality, safety and usefulness of the substance shall be verified by analogy with the methods specified in Annex I to Directive 2001/83/EC.

Plain language: MDR Article 1(8) plus Annex VIII Rule 14 is the classical drug-eluting stent or antibiotic-loaded bone cement path. Class III, medicinal consultation, MDR file. Article 1(9) covers delivery devices. Most reusable pumps and injectors stay in their own MDR lane while the drug stays in its own lane. True single integral products, a prefilled single-use pen with a named drug, sit under medicinal product law, with the device part still owing the relevant MDR Annex I GSPRs including the risk management GSPRs in Annex I Chapter I.

Whichever lane the product sits in, ISO 14971 risk management does not go away. It either lives in the MDR technical file or it lives in the device part of a medicinal marketing authorisation. The patient experiences both.

## A worked example (Test)

A startup is developing a single-use inhaler with a named corticosteroid cartridge. Primary mode of action is pharmacological: the drug treats the airway inflammation, the inhaler delivers the dose. Single integral product, intended exclusively for use in that combination, not reusable. Under Article 1(9), this sits under medicinal product law. The relevant Annex I MDR GSPRs still apply to the device part.

Here is what a credible risk management approach looks like in this case.

First, the team writes a use specification in the IEC 62366-1 sense that covers the full lifecycle: unboxing, first use, repeat dosing over shelf life, final disposal. This specification names every real procedure a patient will perform.

Second, the hazard analysis is run by a multidisciplinary group. Tibor's consistent observation is that the credible risk files are built by teams, not by a lone regulatory person on a Tuesday afternoon. Development, pharma, top management, sales, RA all sit in the same room. Different disciplines surface different hazards. That is the whole point of a structured ISO 14971 process.

Third, the interface hazards get their own explicit branch of the hazard tree. Dose accuracy drift as propellant pressure changes over shelf life. Particle size distribution when the actuator wears. Extractables from the plastic housing entering the aerosol plume. Patient technique errors that leave half the dose in the mouth instead of reaching the lung.

Fourth, risk control follows the hierarchy. Inherent safety by design first: a geometry that forces a correct breath-hold. Protective measures second: a dose counter that physically locks the device when empty. Safety by information last: the IFU, the label, the training video. Tibor points out that skipping to information alone is a classic auditor finding and is almost never the most efficient control even when it looks like it is.

Fifth, the team builds the ALARP loop that MDR requires. ISO 14971 Section 6 says that if a risk is initially seen as acceptable, no further risk control is needed. MDR does not accept that. MDR requires risks to be reduced as far as possible, regardless of initial acceptability. This is the trap Tibor sees startup teams fall into most often: they copy the ISO standard into their QMS and silently miss the MDR ratchet. For a Class III drug-device product, missing this ratchet is a ticking clock on an NB finding.

## The Subtract to Ship playbook (Ship)

The Subtract to Ship move on combination products is to stop pretending the two halves are separate. One risk file, one team, one review cadence. Fewer documents, more rigour.

1. **Decide the lane first, in writing.** Before any hazard analysis, write the one-page justification for Article 1(8), Article 1(9) single integral, or Article 1(9) non-integral. Cite the articles. Cite Annex VIII Rule 14 if Class III. This one page saves months of rework.
2. **Name the primary mode of action.** Device? Drug? Ancillary? This is the question that determines where the dossier lives and which authority leads the review. Ambiguity here poisons everything downstream.
3. **Build one hazard list with an interface section.** Device hazards, substance hazards, and a dedicated interaction branch. Every row in the interaction branch has to name both domains.
4. **Run multidisciplinary hazard sessions.** Tibor's rule: if the team around the table does not include someone from drug stability, someone from device engineering, someone from clinical, and someone who has used the device in anger, the session is not credible.
5. **Close the ALARP loop per MDR, not per ISO 14971 alone.** Every initially acceptable risk still gets a pass through the "can we go lower?" question. Document the answer either way.
6. **Feed PMS back into the file on a cadence shorter than two years.** Tibor has seen too many files updated only at surveillance audit time. Probability and severity change as real-world data comes in. So should the file.
7. **Get the medicinal consultation scoped early if Rule 14 applies.** Class III with an ancillary substance means a competent authority consultation on the substance. Budget and schedule for it the moment the classification decision lands.

## Reality Check

1. Can the team state, in one sentence with article references, which legal lane the product sits in under Article 1(8), 1(9), or neither?
2. Is there a single risk file that covers device, substance, and interface, or three disconnected files?
3. Who was physically in the room at the last hazard analysis session, and did it include development, clinical, and regulatory?
4. For every initially acceptable risk in the file, is there a documented answer to "can this be reduced further" under the MDR ratchet?
5. If Rule 14 applies, has the medicinal consultation been scoped with a named competent authority and a realistic timeline?
6. Does the file have a dedicated interface hazard branch, or are interaction risks scattered across device and substance sections?
7. When was the last PMS-driven update to probability and severity estimates? If the answer is "years ago", the file is already stale.
8. Does the IFU pass the Tibor test: give it plus the device to an untrained user, without coaching, and watch whether they can complete the task safely?

## Frequently Asked Questions

**Is a drug-eluting stent one file or two?**
One integrated MDR technical file under Article 1(8) and Annex VIII Rule 14 as Class III, with the substance section evaluated by the consulted medicinal authority. The risk management file sits inside the MDR dossier and covers the stent, the coating, the drug release, and the interaction.

**Our device is a reusable pump and the drug is a separate vial. Do we need combination-product risk management?**
Under Article 1(9) the pump is a device governed by MDR and the drug is governed by medicinal product law. But the risk file still has to analyse the interface: dose accuracy, compatibility with named drug formulations, error modes when the wrong drug is loaded. The two legal files are separate. The clinical hazard is joint.

**What is ancillary action under Article 1(8)?**
It means the substance supports the primary device function rather than being the main therapeutic agent. A heparin coating on a catheter that prevents clotting at the device surface is ancillary. A drug-eluting stent where the drug modulates local tissue response is ancillary. If the main therapeutic effect is pharmacological, it is not ancillary and Article 1(8) does not apply.

**Does ISO 14971 alone satisfy MDR risk management for a combination product?**
No. ISO 14971:2019+A11:2021 is the state-of-the-art standard and its Annex ZA maps presumption of conformity to the relevant GSPRs, but the MDR ratchet on residual risk is stricter than the ISO text alone. A credible file explicitly honours the MDR "as far as possible" requirement, not the ISO "reasonably practicable" baseline.

**Who leads the risk file when a single integral product sits under medicinal law?**
The medicinal product marketing authorisation holder leads. The device part still has to demonstrate compliance with the relevant MDR Annex I GSPRs. In practice, the device manufacturer runs an ISO 14971 risk file that is incorporated into the medicinal dossier, and both parties sign off.

**Does a Rule 14 combination device have to go to a notified body with combination-product experience?**
Yes, effectively. Not all NBs with MDR scope have Class III and drug-device experience. Founders should confirm scope and case history before signing. Tibor has seen startups onboard with an NB that could not support the medicinal consultation and lose months of schedule.

## Related reading
- [Combination Products Under MDR: Drug-Device and Biologic-Device Rules](/blog/combination-products-mdr-drug-device-biologic-device-rules): the classification and legal lane decision explained in full.
- [MDR Risk Management Process Under ISO 14971](/blog/mdr-risk-management-process-iso-14971): the baseline process this post extends to combination products.
- [Clinical Evaluation for Combination Products](/blog/clinical-evaluation-combination-products): how clinical evidence is structured across the drug-device boundary.
- [The ISO 14971 Annex Z Trap](/blog/iso-14971-annex-z-trap): why the ALARP-to-MDR ratchet mismatch quietly breaks risk files.

## Sources
1. Regulation (EU) 2017/745 on medical devices, consolidated text. Articles 1(8) and 1(9), Annex I Section 12.1, Annex VIII Rule 14.
2. EN ISO 14971:2019+A11:2021: Medical devices, application of risk management to medical devices.
3. Directive 2001/83/EC of the European Parliament and of the Council on the Community code relating to medicinal products for human use, Annex I.

---

*This post is part of the [Risk Management Under MDR](https://zechmeister-solutions.com/en/blog/category/risk-management) 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).*