Medical Device Reporting (MDR) Requirements the New FDA Draft Guidance



Similar documents
Medical Device Reporting (MDR) 21 CFR Part 803

Section 5: Quality Systems Regulation (QSR) and Good Manufacturing Practice (GMP)

Mobile Medical Application Development: FDA Regulation

Inspections, Compliance, Enforcement, and Criminal Investigations

Medical Device Reporting. Sharon Kapsch Office of Surveillance and Biometrics Center for Devices & Radiological Health Food & Drug Administration

Clinical trials for medical devices: FDA and the IDE process

CAPA - the importance of data analysis

JUL Ms. Kendra Basler Regulatory Affairs Associate Abbott Vascular Cardiac Therapies 3200 Lakeside Drive Santa Clara, CA

FMEA Failure Risk Scoring Schemes

Corrections and Removals 21 CFR Part 806

ORACLE CONSULTING GROUP

Topics for today. Issues: Regulatory Obligations Post-marketing Adverse Event Reporting; MDRs and Safety Reports. Post-marketing Submissions

FDA Regulation of Hearing Aids. Eric A. Mann, MD, PhD Clinical Deputy Director Division of Ophthalmic and ENT Devices ODE/CDRH/FDA

Mobile Medical Applications: FDA s Final Guidance. M. Elizabeth Bierman Anthony T. Pavel Morgan, Lewis & Bockius, LLP

SENTINEL EVENTS AND ROOT CAUSE ANALYSIS

G. Recalls.

Breakout Sessions: FDA s Regulation of Mobile Health and Medical Applications

Medical Device Software

CENTER FOR CONNECTED HEALTH POLICY


Vigilance Reporting. Vicky Medley - Head of QMS, Medical Devices. September Copyright 2015 BSI. All rights reserved.

PMAs, 510(k)s, and Advanced IDE Topics

Medical Device Data Systems, Medical Image Storage Devices, and Medical Image Communications Devices

Marketed Unapproved Drugs: FDA to Take Immediate Enforcement Action at Any Time, Without Prior Notice

Complaints, Servicing, and FDA Reporting

A New Standard for Medical Device Adverse Event Classification

ADMINISTRATIVE POLICY & PROCEDURE RISK MANAGEMENT PLAN (MMCIP)

Guidance Medication Guides Distribution Requirements and Inclusion in Risk Evaluation and Mitigation Strategies (REMS)

Regulatory Considerations for Medical Device Software. Medical Device Software

Recall Communication: Medical Device Model Press Release Ron Brown

CHAPTER 7 - RECALL ACTIVITIES

Medical devices adverse incidents reported to MHRA 2011 to 2013

Medical Software Development. International standards requirements and practice

Guidance for Industry Bar Code Label Requirements Questions and Answers

Reporting Adverse Events and Concerns at Stroger Hospital

On Behalf of: InTouch Health

IOWA STATE UNIVERSITY Institutional Review Board. Reporting Adverse Events and Unanticipated Problems Involving Risks to Subjects or Others

August 21, TCM Associates Ltd Mr. Iain Alligan Technical Director 3 Hillgrove Business Park Nazeing Road Essex EN9 2HB United Kingdom

The Mammography Quality Standards Act Final Regulations Document #1

MOBILE MEDICAL APPLICATIONS

Guidance for Industry

Application Submitted on Received on Supplement type NDA /S-005 July 24, 2008 July 25, 2008 Changes Being Effected

Triangle Compounding 11/2/15

Manifestation Determinations: Legal and Practical Considerations

International Medical Device Regulators Forum (IMDRF) US FDA Center for Devices and Radiological Health - Update

IACP Comparison of 503A and 503B The Drug Quality and Security Act of 2013

The U.S. FDA s Regulation and Oversight of Mobile Medical Applications

It s all about managing food. Food Recall Plan Template For Food Manufacturers

Cutting Edge Issues in Health Care Technology & mhealth. Agenda

AW Server 510 (k) Summary of Safety and Effectiveness

FOOD FACILITIES REGISTRATION OF. Protecting the U.S. Food Supply. What You Need to Know About

INSTITUTIONAL POLICY AND PROCEDURE (IPP) Department: Manual: Section:

Guidance for Industry

Guidance for Industry. Further Amendments to General Regulations of the Food and Drug Administration to Incorporate Tobacco Products

ADDRESSES SYSTEM LOCATION

510(k) Summary GlobalMedia Group, LIC. MAY CONiM

TEXAS DEPARTMENT OF STATE HEALTH SERVICES. Executive Summary. Report on Regulation of Laser Hair Removal

January 12, Dear Amy Yang:

FDA Releases Final Cybersecurity Guidance for Medical Devices

Guidance for Industry

Final Guidance on Electronic Source Data in Clinical Investigations Promoting esource Data Capture

FDA Guidance for Industry Update - Process Validation

DEPARTMENT OF HEALTH & HUMAN SERVICES NDA NDA NDA [inside address] Dear :

Information Sheet Guidance For IRBs, Clinical Investigators, and Sponsors

Guidance for Sponsors, Institutional Review Boards, Clinical Investigators and FDA Staff

General Wellness: Policy for Low Risk Devices. Draft Guidance for Industry and Food and Drug Administration Staff

How To Regulate A Medical Device From A Cell Phone

By Natalia Wilson, MD, MPH

Medical Device Reporting for User Facilities

Unique Device Identification System; Final Rule

Case 1:15-cv XXXX Document 1 Entered on FLSD Docket 09/10/2015 Page 1 of 8

Guidance for Industry Information Program on Clinical Trials for Serious or Life-Threatening Diseases and Conditions

WHITEPAPER: SOFTWARE APPS AS MEDICAL DEVICES THE REGULATORY LANDSCAPE

0 EC V-,) 133 Lj9a

Unique Device Identifier System: Frequently Asked Questions, Vol. 1 Guidance for Industry and Food and Drug Administration Staff

February 5, Dear Kristin Pabst,

Strengthening Our national SyStem for medical device POStmarket Surveillance

IVD Regulation Overview. Requirements to Assure Quality & Effectiveness

NOTICE OF PRIVACY PRACTICES Effective: September 20, 2013

CONDUCTING GLOBAL CLINICAL RESEARCH TRIALS:

GE Healthcare MAR

The Shifting Sands of Medical Software Regulation

Transcription:

Medical Device Reporting (MDR) Requirements the New FDA Draft Guidance February 27, 2014 Jeffrey K. Shapiro (202) 737-9633 jshapiro@hpm.com 1

Essential Requirements n Submit MDR reportable events to FDA (21 CFR 803.10(c), 803.50) n Establish and maintain written procedures to review complaints for MDR reportability (21 CFR 803.17, 820.198) n Establish and maintain complete MDR files (21 CFR 803.18, 820.198) 2

Definition of Reportable Event (21 CFR 803.3) n MDR reportable event (or reportable event) means: An event that manufacturers or importers become aware of that reasonably suggests that one of their marketed devices: (i) May have caused or contributed to a death or serious injury, or (ii) Has malfunctioned and that the device or a similar device marketed by the manufacturer or importer would be likely to cause or contribute to a death or serious injury if the malfunction were to recur. 3

Elements of an MDR Reportable Event n Manufacturer n becomes aware of information n that reasonably suggests n one of its marketed devices n may have caused or contributed to a serious injury or death OR n malfunctioned and same or similar device would likely cause or contribute to serious injury or death upon if malfunction were to recur 4

Preamble statement likely Reporters do not need to assess the likelihood that a malfunction will recur. The fact that the malfunction occurred once leads to the presumption that the malfunction will recur. A malfunction is reportable if any one of the following is true: (1) The chance of a death or serious injury occurring as a result of a recurrence of the malfunction is not remote; 5

Draft Guidance likely n If malfunction causes death or serious injury once, it is presumed likely to do so q Subsequent malfunctions must be reported n Must file exemption to lift presumption q Based on investigation of subsequent malfunctions q FDA appears to abandon previous two year presumption guidance 6

Requirement to Investigate n Perennial problem sometimes difficult to obtain information, healthcare facility or clinician may be uncooperative n Draft guidance says q Level of effort should relate to nature and severity of the event, rather than just focusing on number of attempts n Many manufacturers have a procedure requiring three attempts q Good faith effort includes at least one written request q Record each attempt and response by reporter 7

Requirement to Investigate n Draft guidance recommends focus on q Patient involvement and outcome your ability to capture this information is part of good faith effort q If initial report is for a malfunction, but patient subsequently dies, supplemental report should be submitted for death 8

Requirement to Investigate n Draft guidance q Good faith effort does not require specific number of attempts one attempt should be in writing q Try to get the device back n If users do not cooperate, you must still analyze event cannot just close the file n Look at device history, manufacturing processes, similar events 9

Exemptions Are Becoming More Important n FDA s position (in warning letters and draft guidance) is that q Manufacturers and importer have duplicate requirement to report death or serious injuries need an exemption to have just one report q Manufacturer and contract manufacturer of the finished device have duplicate reporting requirements absent an exemption n Many firms have allocated responsibility by contract but have not requested exemptions for the nonreporter q This needs to change need a contract allocation and an exemption! 10

Delay in Surgery n If your device causes or contributes to a delay in surgery, is it a reportable event? q Maybe! n Draft guidance q Delay not automatically reportable q Need to gather details about impact on the patient s condition to support reporting decision 11

Routine Surgical Explants n Draft guidance - not reportable if implant has reached (or is near) its established life expectancy q Unless there is device-related death or serious injury associated with explantation / replacement 12

Labeled Incompatibility n Device A s labeling states it is not compatible with Device B n Physician uses them together adverse event n Reportable? q Yes if there is a patient serious injury or death because these are reportable even when caused by user error! q No if there is no patient adverse event but the devices do not work not a malfunction because labeling was not followed, so no malfunction report required 13

Diagnostic Devices n If diagnostic device failure indirectly serious injury or death reportable? n Draft guidance yes! 14

Difference of Medical Opinion n What is healthcare professionals at facility differ over whether malfunction occurred or device may have caused or contributed to serious injury or death? n Draft guidance says- q You must investigate and determine if information reasonably suggests malfunction / serious injury / death q Evaluate the differences in opinion and explain why you choose one over the other 15

Same Patient / Different Days n Draft guidance - same patient experiences adverse events on different days with same device report each as separate submission 16

Devices under Investigational Device Exemption (IDE) n Draft guidance q Device X is cleared or approved q Device X is being studied for a second intended use under an IDE q Adverse event occurs in the IDE study n Reportable? q Yes both MDR and IDE reporting requirements apply! 17

Foreign Events n Device X is exported under section 801(e) or 802 of the Food, Drug, and Cosmetic Act (so it is not cleared or approved for sale in the US) n Reportable event occurs in the EU n Reportable? q Draft guidance yes but we re going to exercise enforcement discretion q Excepts if a concern has arisen but we ll let you know in writing 18

Foreign Events n US manufacturer q Device under IDE study in US q Exported under 801(e) or 802 of the FDCA q Adverse event outside US n Reportable? q Draft guidance yes, but enforcement discretion q But it may be reportable to the IDE program 19

Foreign Manufacturer n Draft guidance hypothetical q Foreign manufacturer q US clearance or approval q Marketed outside US q Adverse event outside US n Reportable? q Draft guidance yes even if devices are tweaked to meet different standards outside US q Unless modification is directly involved 20

Foreign Manufacturer n Draft guidance hypothetical q Foreign manufacturer q No US clearance or approval, but IDE study q Marketed outside US q Adverse event outside US n Reportable? q Draft guidance no MDR report (might be reportable to IDE program) 21

Malfunction Caught Before Use n Draft guidance health care provider notices that device is malfunctioning and intervenes before patient harm can occur n Reportable? q Yes, if it could cause serious injury or death if malfunction were to recur n What if device malfunctions and alarms to alert users? q Draft guidance yes because alarm might not work or there might be no one present to respond 22

Sale of 510(k) n Draft guidance hypothetical- q Firm A manufacturers and distributes cleared device q Sells 510(k) to Firm B which takes over manufacture and distribution q Adverse event for device sold by Firm A n Who must report? q Firm A q Or firms could agree that Firm B will report but Firm A needs to apply for an exemption as well 23

IMPORTANT LINKS MDR Guidance Document - http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/ucm094529.htm MDR Preamble http://www.gpo.gov/fdsys/pkg/fr-1995-12-11/html/95-29906.htm Compliance Program Guidance Manual http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/ucm072753.htm CDRH Learn http://www.fda.gov/training/cdrhlearn/default.htm emdr Draft Guidance http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/ucm175805.htm? utm_campaign=google2&utm_source=fdasearch&utm_medium=website&utm_term=mdr %20Guidance&utm_content=2 24

Jeffrey Shapiro (202) 737-9633 jshapiro@hpm.com Thank You! Visit our firm s top-rated blog: www.fdalawblog.net 25