If your product is a prefilled syringe, a pen injector, an autoinjector, an inhaler or any other medicine delivered through a device, you are running two safety systems at once, whether you planned to or not. The medicine is governed by pharmacovigilance rules. The device is governed by device vigilance and post-market surveillance rules. The two have different legal bases, different reporting routes, different databases, different timelines and, very often, different people responsible for them inside the company.
A single patient report does not respect that division. A patient who injects the wrong dose because the pen jammed has experienced a device problem, a medication error and possibly an adverse reaction, all in one event. This guide explains how drug-device combination products are classified, where the two vigilance systems meet, how the reporting clocks differ, and how to build one intake process that serves both. If you are searching for combination product vigilance, drug-device combination adverse event reporting, device vigilance for pharmaceutical companies, or pharmacovigilance and medical device vigilance interface, this is written for you.
Start with the Configuration of Your Product
The rules that apply depend on how the medicine and the device are put together. Three broad configurations are used in regulatory thinking:
- Integral products, where the medicine and the device form a single product placed on the market as such, and the device is not reusable or is intended to be used exclusively in that combination. Prefilled syringes, prefilled pens and many inhalers fall into this group
- Co-packaged products, where the medicine and the device are sold together in the same pack but remain separate items, such as a vial supplied with a dosing syringe or an adapter
- Cross-labelled or referenced products, where the device is sold separately but the medicine’s labelling says it must be used with that device or class of device
In the EU, integral products are authorised as medicinal products under the medicines legislation, but the device part must meet the general safety and performance requirements of the Medical Device Regulation. Article 117 of that regulation requires the application for marketing authorisation to include a notified body opinion on the conformity of the device part. For co-packaged products, the device is regulated as a device in its own right under the Medical Device Regulation, and the device manufacturer carries device obligations, while the pharmaceutical company is the marketing authorisation holder for the combined pack. These distinctions are the starting point for working out who reports what.
The EU does not give combination products a single regulator for the whole lifecycle. Medicines are overseen through the medicines framework and EudraVigilance, and devices through the device framework and its own databases. In the United States, a different structure applies, with the FDA’s adverse event system for drugs and a separate system for device reports. A company selling in several regions therefore faces several versions of the same question.
Why the Clocks Differ
The reporting timelines are one of the most practical differences, and they are easy to get wrong when one team handles both streams.
- For medicines, serious suspected adverse reactions are generally reported to the authorities within 15 days of the company becoming aware of them, and non-serious reactions on a longer timescale, depending on the jurisdiction
- Under the EU Medical Device Regulation, serious incidents are generally reportable within 15 days of awareness, but shorter limits apply to some situations. A serious public health threat is reportable immediately and no later than 2 days, and a death or unanticipated serious deterioration in health is reportable within 10 days
- The trigger events differ. A device regulator is interested in malfunctions and deficiencies that could lead to harm, even if no harm has yet occurred, while pharmacovigilance is built around suspected adverse reactions and medication errors
Always check the current legal text for each market, since requirements and interpretations change. The point is that one event may start two clocks with different lengths and different definitions of when the clock starts.
Where the Two Systems Overlap
The overlap is greater than many teams realise. Consider the reports that arrive from patients and healthcare professionals:
- A device malfunction with no adverse effect: a device vigilance matter, and often a quality complaint, but potentially also relevant to pharmacovigilance if the dose delivered was affected
- A malfunction with a clinical effect, such as an underdose, an overdose or a missed dose: both systems, and a likely medication error
- A use error, such as a patient misunderstanding the injection steps: relevant to the medicine’s risk management, the device’s human factors file and the labelling
- A local reaction at the injection site: possibly an adverse reaction, possibly linked to needle, device or formulation
- An allergic reaction to a component of the device, such as a latex or adhesive element: could be both
- A complaint about a leak or a broken part, with no patient information: quality and device vigilance, with an assessment of whether a hidden safety issue exists
The practical consequence is that every report about a combination product needs to be looked at from both sides before it is classified, not routed by whichever team picked it up.
One Intake, Two Assessments
The cleanest design is a single intake that triages every report for both systems. A workable approach looks like this:
- All sources, including customer service, medical information, sales, distributors and social media monitoring, feed into one intake point for combination products
- At intake, a trained person records the minimum data for both systems: patient and reporter details, product and lot number, device details, description of what happened, whether harm occurred and whether the device is available for return
- Each report is assessed for pharmacovigilance criteria and for device vigilance criteria, and the outcome of both assessments is recorded, even when the answer for one of them is “no”
- Two clocks are started where needed, with owners for each
- The returned device, where available, goes to technical investigation, and the findings are shared with the safety team
- Closure requires both assessments to be complete, and any trend across both streams to be reviewed
Practical Controls That Make This Work
- Include the device in training for pharmacovigilance staff, and the medicine in training for the device team, so each can recognise what the other needs
- Add specific questions to intake forms about the device, such as whether the device was working normally, how it was used, and whether it is available for return
- Set a rule for how quickly each team shares a report with the other, for example the same working day
- Keep a joint log of all combination product reports, with their classification and reporting decisions
- Include device complaint data in signal detection and periodic safety reports, and pharmacovigilance data in device post-market surveillance reviews
- Include use errors and human factors information when reviewing risk management plans and device risk files, so that the two documents are consistent
A Worked Example: The Jammed Pen
The following case is invented, but typical. A patient with diabetes calls a company’s medical information line to say that their pen injector jammed halfway through an injection. They are unsure how much insulin they received, and later that day their blood sugar was high. They still have the pen.
In a well designed process, the call handler records the product, lot number, device details and the sequence of events. Pharmacovigilance assesses the report as a suspected lack of effect and a possible medication error with a serious or non-serious outcome depending on what happened next, and starts the relevant reporting clock. Device vigilance assesses the malfunction as an incident that has led, or could have led, to harm, and starts its own clock. The pen is collected and sent for technical investigation, and the findings go to both teams. If the investigation finds a defect in a component batch, the quality team considers whether other lots are affected, and the safety team looks for similar reports. When the case closes, the human factors team checks whether the instructions for use contributed.
In a poorly designed process, the same call is logged as a complaint, the pen is never requested, and the high blood sugar is mentioned in a note that nobody reads. Weeks later, several similar reports arrive and a pattern becomes visible only because a patient group raises it. By then, the opportunity to examine the original device has gone.
Contracts Between Drug and Device Companies
Many combination products involve a device manufacturer who is not the medicine’s marketing authorisation holder. Where that is the case, the agreement between the two parties is central. A good safety and quality agreement covers:
- Which party receives reports from each source, and how quickly they are passed to the other
- Which party reports to which authority, in which timelines, and how reporting decisions are made when the classification is unclear
- What data each side shares, including device investigation results and lot information
- How trends, signals and corrective actions are shared and decided
- Who carries out technical investigation and who pays for it
- How changes to the device, the medicine or the labelling are notified, assessed and approved
- Audit rights, and cooperation during inspections by either type of authority
- Responsibilities for field safety actions, recalls and communications with healthcare professionals
A frequent failing is an agreement written when the product was developed, which describes development responsibilities but says little about post-market reporting.
What Inspectors Look At
Inspectors from either side may ask about the interface. Pharmacovigilance inspectors can ask how device-related reports are identified and handled, since a medication error caused by a device is within scope. Device authorities and notified bodies can ask how medicine-related safety information is considered within device surveillance. Be ready to show:
- A written description of the interface in both quality systems
- Evidence of training on both sides
- Examples of reports classified from both angles, with the reasoning recorded
- Records showing the two clocks were managed
- Joint trend reviews and how their conclusions led to action
- Contracts with device manufacturers and distributors, with evidence that they work in practice
Common Mistakes
- Treating device complaints as purely quality events and never checking them for safety content
- Assuming the device manufacturer will report everything, without confirming this in writing
- Having a pharmacovigilance team that has never seen the device or its instructions for use
- Ignoring use errors until a signal emerges
- Starting one clock and forgetting the other
- Failing to include device information in periodic safety reports and risk management plans
- Not reviewing how a device change or supplier change affects safety reporting
A Starter Plan
- List every product with a device component and classify its configuration for each market
- Map who receives reports today, and where each route ends
- Draw the intake process you want, with dual triage and two clocks, and test it using five real or realistic cases
- Review the agreements with device manufacturers and distributors, and update where post-market duties are unclear
- Train both teams, update procedures and set a joint review of data at least quarterly
- Run a mock inspection question on a combination product complaint, and trace it through both systems
Closing the Gap Between Your Drug and Device Safety Systems
Quality and Vigilance Ltd is unusual in working across pharmacovigilance and medical device audits and inspection support, as well as GMP and GDP, which puts it in a good position to look at where the two safety systems meet. A joined-up view tends to reveal gaps that neither a pure pharmacovigilance team nor a pure device team will see on its own. The support typically includes:
- Classification of each product by configuration and a map of the reporting obligations in your markets
- Design of a single intake and dual assessment process, with clear ownership of each clock
- Review and strengthening of safety and quality agreements with device manufacturers and distributors
- Audits of the pharmacovigilance and device vigilance interface, including ISO 13485 and MDR-related requirements
- Inspection readiness support for both pharmacovigilance and device authorities, including mock questions on combination product complaints
Get in touch with Quality and Vigilance Ltd today to close the gap between your drug and device safety systems before an inspector finds it.