Vigilance Reporting Under the MDR: Insider's Guide (2024)

Implementing the European Medical Devices Regulation (MDR; 2017/745) and the In Vitro Diagnostic Medical Devices Regulation (IVDR; 2017/746) have significantly increased post-market surveillance and vigilance system requirements for medical device manufacturers compared to previous regulations.

The regulations are clear that medical device manufacturers and authorized representatives (AR) must take action to notify competent authorities of any incident or field safety corrective action (FSCA) involving their medical device.

However, the circ*mstances of incident reports and their timing and follow-up are not always clear to regulatory and quality professionals in the industry.

Fear not! This article reviews vigilance system reporting requirements in the EU and gives tips on how you can ensure compliance and appropriate follow-up for any events involving your medical device.

A note: adverse event reporting and incident reporting can be considered similar concepts. The phrase "adverse event" is used mostly in the United States, while the European equivalent is "incident."

Vigilance Reporting Requirements Under the MDR

Before going into details on the medical device vigilance system and reporting requirements in the EU, first, we need to understand which events require reporting and when.

What is a reportable event?

According to the MDR, any event involving a medical device must live up to the established criteria to be considered reportable.

A medical device event is reportable if:

  • It caused or might cause a serious public health threat
  • It caused death or serious deterioration of health of the patient, user, or any other person involved
  • If it did not cause serious deterioration of health in the patient or user but might lead to it should the event recur

"Serious deterioration of health" is defined as life-threatening illness or injury, permanent impairment of a body structure or function, hospitalization or prolongation of hospitalization, medical or surgical intervention to prevent life-threatening illness or permanent impairment, chronic disease, indirect harm as a consequence or incorrect diagnostic or test results, fetal distress or death, and congenital abnormalities.

Timelines for reporting

Recommended by LinkedIn

Vigilance Under the EU MDR: A glossary Ethan Drower 1 year ago
The UK unveils a new roadmap for medical device… Global Regulatory Services Ltd 4 months ago
Navigating Factsheet for Authorities in Non-EU/EEA… Avisek Ghose 7 months ago
Vigilance Reporting Under the MDR: Insider's Guide (4)

Events related to serious public health threats must be reported immediately but no later than two days after the manufacturer becomes aware of the incident.

Events related to death or serious deterioration of health must be reported immediately but no later than ten days after the manufacturer becomes aware of the incident.

Events with no consequence to the patient but the risk of death or serious deterioration of health should the event recur must be reported immediately but no later than 15 days after the manufacturer becomes aware of the incident.

MEDDEV 2.12

In 2013, the European Commission issued MEDDEV 2.12-1 rev.8 Guidelines of a medical devices vigilance system. The guideline is meant to clarify and describe the European system for the notification and evaluation of incidents and field safety corrective actions involving medical devices and in vitro diagnostic medical devices.

While MEDDEV 2.12 1 rev.8 is not a legally binding document, it is extremely helpful for anyone involved with vigilance reporting in the EU.

The additional guidance updates the definitions of field safety corrective action and field safety notice. It also provides the new Manufacturer's Incident Report Form and explains the new concepts included within.

Frequently Asked Questions

Vigilance Reporting Under the MDR: Insider's Guide (5)

Do I need to submit vigilance reports for incidents that occur outside the EU?

Events are only reportable if the incident or field safety corrective action takes place within the EU.

Please note the phrasing of the latter - events that happen outside of the EU that result in a field safety corrective action within the EU must also be reported.

Are user errors reportable?

User errors are reportable if they result in death or serious deterioration of the patient or user. If they do not, they can be handled by the manufacturer internally.

All user errors should be included in trend analysis and trend reporting. If a significant trend in user errors appears, it must be reported.

Abnormal use, i.e., use that deviates from the norm, such as off-label use or untrained use, does not need to be reported to the competent authority.

What about events that are reported in the literature or social media?

Vigilance Reporting Under the MDR: Insider's Guide (6)

While there are no direct requirements to report events originating in the literature or social media, the requirement to report to the competent authority when a medical device manufacturer "becomes aware" of the incident can be interpreted as the manufacturer has to report events coming from any source.

If a manufacturer comes across any events reported outside of the traditional sources. In that case, they should be logged into their complaint system and evaluated as reportable incidents using the criteria outlined above.

It is recommended that manufacturers report in cases of doubt.

What is the timeline for following up on my initial incident report?

MEDDEV does not specify any timelines for follow-up reports. It is recommended to submit a follow-up report within 30 days of the initial report or as soon as additional information becomes available.

Note that member states might have local timeline expectations that differ from the European Commission. We always recommend making sure you check the rules and recommendations in the member state where your incident report is submitted.

Vigilance Reporting Process

You have become aware of an incident that requires reporting - now what?

  1. Determine the timeline for reporting. Serious public health threats have much shorter reporting timelines than serious incidents. Make sure you understand what event category your incident belongs to.
  2. Report the incident to the appropriate competent authorities.
  3. Respond to any questions the competent authority might have about the incident. It is normal for the competent authority to return with clarifying questions and requests for more documentation.
  4. Determine if your incident requires any field safety corrective actions or field safety notices. If so, report them to the appropriate competent authority.
  5. Submit final incident reports and FSCA reports to the authorities.
  6. Add the vigilance report and any relevant documentation to your quality system records or ISO 13485.
  7. Inform your notified body of the incident and/or FSCA. If your device is class I self-certified, you are exempt from this requirement.

Additional vigilance resources

Vigilance Reporting Under the MDR: Insider's Guide (2024)

References

Top Articles
Top 3 Beyonce AI Voice Generator to Make You Sing Like A Star
Transfer portal rankings: College football's 24 teams who crushed the 2024 recruiting cycle
Leah4Sci Alkene Reactions
Barstool Sports Gif
Zavvi Discount Code → 55% Off in September 2024
Champion Our Cause Wow
My.doculivery.com/Crowncork
Defense Immunity 2K23 Meaning
Kutty Movie Net
Lake Charles, LA Houses and Single Family Homes For Rent | realtor.com®
Making a Docker Container Use a VPN – Natural Born Coder
Sandra Sancc
T33N Leaks 5 17
P1 Offshore Schedule
Hulu documentary delves deeper into the Randall Emmett scandal
636-730-9503
3 30 Mountain Time
That Is No Sword X Kakushi By Nez_R
Aldi Sign In Careers
Point After Salon
Maurice hat ein echtes Aggressionsproblem
Apple iPhone SE 2nd Gen (2020) 128GB 4G (Very Good- Pre-Owned)
Chris Bailey Weather Forecast
Watch ESPN - Stream Live Sports & ESPN Originals
Alexandria Van Starrenburg
Dutchessravenna N Word
Craigslist Cars Los Angeles
Bureaustoelen & Kantoorstoelen - Kantoormeubelen | Office Centre
Eromancer Kemono Party
VMware accompagne ses partenaires et soutient leur transformation en faisant évoluer son programme « VMware Partner Connect » - Broadcom News & Stories - Français
Nail Supply Glamour Lake June
Panama City News Herald Obituary
Wisconsin Volleyball Team Leaked Pictures And Videos
Pho Outdoor Seating Near Me
Peoplesgamezgiftexchange House Of Fun Coins
Tapana Telugu Movie Download Kuttymovies
Let's Take a Look Inside the 2024 Hyundai Elantra - Kelley Blue Book
Associate Resources Aces-How To Create An Account And How Its Features Work
Heatinghelp The Wall
Harpel Hamper
Plusword 358
Download Diablo 2 From Blizzard
Natalya Neidhart: Assembling the BOAT
Dean of Students | Alcohol & Drug Policies
Jesus Calling December 1 2022
Commissary Exchange Benefits What You Need To Know Aafes To Offer Service To Former Military
Giorgia Meloni, die Postfaschistin und ihr "linker" Lebensgefährte
Costco Gas Prices Sioux Falls
Fintechzoommortgagecalculator.live Hours
Used Go Karts For Sale Near Me Craigslist
Boyle County Busted Newspaper
Perolamartinezts
Latest Posts
Article information

Author: Msgr. Benton Quitzon

Last Updated:

Views: 6172

Rating: 4.2 / 5 (63 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Msgr. Benton Quitzon

Birthday: 2001-08-13

Address: 96487 Kris Cliff, Teresiafurt, WI 95201

Phone: +9418513585781

Job: Senior Designer

Hobby: Calligraphy, Rowing, Vacation, Geocaching, Web surfing, Electronics, Electronics

Introduction: My name is Msgr. Benton Quitzon, I am a comfortable, charming, thankful, happy, adventurous, handsome, precious person who loves writing and wants to share my knowledge and understanding with you.