Medical Device Reports Medical Device Vigilance Systems
Medical Device Reports Medical Device Vigilance Systems
Medical Device Reports Medical Device Vigilance Systems
OTHER
STAMP HERE
Table of Contents
1.0 Purpose..........................................................................................................................................................3
2.0 Scope.............................................................................................................................................................3
7.0 Procedure......................................................................................................................................................7
7.1 Reporter..............................................................................................................................................7
7.2 Quality Assurance..............................................................................................................................8
1.0 Purpose
To establish and implement a system for reporting adverse incidents as a basis for effective
identification and evaluation of adverse events, and timely submission of Medical Device Reports to the
FDA and/or incident reports to Competent Authorities of the Medical Devices Vigilance System.
2.0 Scope
This procedure applies to reportable events of products manufactured at all facilities of [Company
Name].
1.2 Attachments
Copies of any test reports, laboratory reports, service records and reports, records of
investigations, lab notebook notes, or any completed forms.
1.9 Incident
Any malfunction or deterioration in the characteristics and/or performance of a device, as well as
any inadequacy in the labeling or the instructions for use, which might have led to the death of a
patient or user or to a serious deterioration in his state of health. Also, any technical or medical
reason in relation to the characteristics or performance of a device leading to systematic recall of
devices of the same type by the manufacturer.
1.12 Malfunction
A "malfunction" is a failure of the device to meet its performance specifications or otherwise
perform as intended.
1.13 Manufacturer
The natural or legal person with responsibility for the design, manufacture, packaging and
labeling of a device before it is placed on the market under his own name, regardless of whether
these operations are carried out by that person himself or on his behalf by a third party.
Also, the natural or legal person who assembles, packages, processes, fully refurbishes and/or
labels one or more ready-made products and/or assigns to them their intended purpose as a device
with a view to their being placed on the market under his own name.
1.21 Product
Product that has been returned by a customer or has failed in the manufacturing process
1.22 Recall
When there is a risk of death or serious deterioration to the state of health, the return of a medical
device to the supplier, its modification by the supplier at the site of installation, its exchange or
its destruction, in accordance with the instructions contained in an advisory notice.
1.24 Reporter
A [Company Name] employee or Department that reports a problem / event which may be a
reportable event.
1.31 References
Customer Servicing
Customer Complaint Processing
Field Service
Corrective and Preventive Action
Correction or Removal of Marketed Product
Quality Records
Quality Investigation
Returned Product Authorization, Evaluation, and Disposition
Quality System Report to Senior Management
NOTE: It is the responsibility of the individual who downloads this template for guidance to make
sure these are the latest versions of the FDA and EEC references.
3.1 Malfunction
A malfunction should be considered reportable if any one of the following is true:
• The consequences of the malfunction affect the device in a catastrophic manner that may
lead to a death or serious injury-, it causes the device to fail to perform its essential function
and compromises the device's therapeutic, monitoring or diagnostic effectiveness which
could cause or contribute to a death or serious injury, or other significant adverse device
experiences. The essential function of a device refers not only to the device's labeled use, but
for any use widely prescribed within the practice of medicine; it involves an implant
malfunction that would likely to cause or contribute to death or serious injury, regardless of
how the device is used;
• The device is considered life-supporting or life-sustaining, and thus essential to maintaining
human life; or
The manufacturer takes or would be required to take action under section 518 or 519 (f) of
the Food and Drug Cosmetic Act as a result of the malfunction of the device or other similar
devices;
• A malfunction which is or can be corrected during routine service or device maintenance
must be reported if the recurrence of the malfunction is likely to cause or contribute to a
death or serious injury if it were to recur.
5.0 Procedure
5.1 Reporter
Upon receipt or identity of a presumable reportable problem or event as defined in the definition
of terms of this procedure, reporter fills out the MDR Event Form.
Reporter fills in date of problem or event and date problem or event reported to [Company
Name].
If the event was an internal event, reporter fills in device name, model number, serial / lot
number and details of event.
If the event was an external event generated by a customer complaint, the reporter refers to the
Customer Complaint Form.
The Reporter signs and dates and gives MDR Event Form with any attachments and product, if
any, to Quality Assurance.
Assigns a sequential report number to the problem / event and enters the problem/ event into the
MDR/MDVS Log. The report number will consist of the letters "MDW' followed by the last two
digits of the year then a sequential number. The sequential number will begin with "001". Ex.
MDR97001
If product was received , verifies device name, model number, serial / lot # on MDR Event Form.
If additional information is needed, requests additional information through a written letter, fax
or phone requests to the reporter and records date requested and attaches any attachments or
documents phone conversation details.
If additional information is not needed, documents reasons why on the Medical Device Report
Analysis Form.
Makes I copy of the MDR Event Form and MDR Analysis Form and attachments, and distributes
the copy to the "MDR Event Under Investigation" folder.
Documents the reason why or why not the event was reportable.
If the event was reportable, submits appropriate Medical Device Report to the FDA and
documents date submitted and by whom.
Makes 2 copies of the MDR Event Form, MDR Analysis Form, and Quality Investigation Form
and attachments, and distributes one copy to the "MDR Event Closed" folder and attaches one
copy to the customer complaint form if applicable and removes the previously filed MDR Event
form from the "MDR Event Under Investigation" folder.
Table 8.0
30- day report 30-day reports of deaths, serious Within 30 calendar days from
injuries and malfunctions becoming aware of an event.
5-day report 5-day reports on events that Within 5 work days from
require remedial action to becoming aware of an event.
prevent an unreasonable risk
of substantial harm to the public
health and other types
of events designated by FDA.
Baseline report Baseline report to identify and Within 30 calendar and 5 work
provide basic data on each days when device or device
device that is subject of an MDR family is reported for the first
Report. time.
Supplemental report This report will contain Within one month (30 calendar
information that was unknown, days) following receipt of
not available, or new facts that additional information on FDA
alter any information on the form 3500A.
original 30-day or 5-day MDR
reports.
NOTE. The 5-day time frame for remedial actions begins the day after any employee, who is a
person with management or supervisory responsibilities over persons with regulatory, scientific,
or technical responsibilities, or a person whose duties relate to the collection and reporting of
adverse events, "becomes aware" that a reportable MDR event has occurred. The 5-day time
frame for reports requested by FDA begins when any employee of [Company Name] becomes
aware that a reportable event has occurred.
An annual update to a baseline report does not have to be submitted if during the
previous twelve month period, there were no I~MR reportable adverse events filed with
the FDA for the current model(s) or for any new model(s) that may have been added to
the initial baseline report during that designated time period and there were no other
changes in the information previously submitted. This waiver remains in effect until
[Company Name] files an adverse event report either for the current model(s), or
[Company Name] adds new models after the last update. In this case, an annual update
report is required at the time of the next annual registration and will contain the same
information identified above. The update must include the designated information
covering the time frame from the last baseline report update to the present. This may be
a period longer than 12 months.
Table 8.6.
TYPE OF MDR REPORT Code level IDENTIFICATION OF
FORM ENVELOPE: Place in lower
left-hand corner of the
envelope above bar.
5-Day 3500A 5-Day Report
30-Day 3500A 30-Day Manufacturer Report
Supplemental 3500A Manufacturer Supplemental
Report
Baseline 3417 Baseline Report or Annual /
Interim Update Baseline Report
(301)594-3886
When assessing the link between the device and the incident or near incident, the opinion of
health care professionals, the preliminary assessment of the incident, knowledge of previous
similar incidents, and other knowledge of the device should be taken into account. The following
may indicate an association between the device and the incident:
• A device with a characteristic which could lead to an incident, even though the device has
not malfunctioned or deteriorated (report as a near incident)
For additional clarification on the types of incidents or near incidents to report, see the
Guidelines On A Medical Devices Vigilance System.
If [Company Name] determines within 10 days for an incident or within 30 days for a near
incident that the device was not the cause of the incident or near incident, then an initial report is
not filed, and this procedure terminates.
For incidents occurring outside the EEA which lead to corrective action on CE marked devices
within the EEA, an initial report should be filed as soon as possible, once the decision is made to
perform corrective action on CE marked devices within the EEA.
For incidents occurring outside the EEA which lead to corrective action on CE marked devices
within the EEA, the initial report should be made, for Class Il or Class III devices, to the
Competent Authority in the country where the Notified Body is located which attested to the CE
marking for the device, or for Class I devices, to the Competent Authority in the country in which
Authorized Representative for the device is located.
For the list of Competent Authorities, as well as the Authorized Representative, Notified Body,
and Distributors for [Company Name] CE marked product, see MDVS Contacts.
In addition to filing an initial report with the appropriate Competent Authority, consideration
should be given to notifying the Authorized Representative, the Notified Body attesting to the CE
mark, and distributors of the device.
Retain a copy of the report and enter the report into the MDR/MDVS Log. If the report is first
made by telephone or fax, written confirmation should be mailed as soon as possible. When
acknowledgment of receipt by the Competent Authority is received, attach acknowledgment to
the initial report copy.
7.5 Investigation
Investigate the incident or near incident, keeping the Competent Authority informed as necessary
and cooperating with the Competent Authority as requested. If a single coordinating Competent
Authority is named, then all correspondence should be with the coordinating Competent
Authority, unless otherwise instructed. If [Company Name] cannot investigate an incident, then
we must inform the Competent Authority immediately.
Carry out the investigation in an organized and timely manner. Gather information from the
individuals involved in the incident. Examine the device involved in the incident, if possible
(note: any examination of the device which alters the condition of the device requires prior
notification of the Competent Authority). Determine the root cause of the incident and
appropriate actions to be taken, if any. Obtain information from and coordinate information with
other [Company Name] systems during the investigation, such as Customer Complaint
Processing, Field Service, Customer Servicing, Corrective and Preventive Action, Correction or
Removal of Marketed Product, Quality Investigation, and Returned Product Authorization,
Evaluation, and Disposition.
Complete all applicable sections of the form, and attach sheets if necessary to include all relevant
information.
The final report should be sent to all Competent Authorities who received an initial report from
[Company Name]. Consideration should also be given to sending the final report to the
Authorized Representative, the Notified Body attesting to the CE mark, and distributors of the
device.
The Competent Authority will inform [Company Name] when the file is endorsed as "closed".
[Company Name] will also be informed of the results of investigations by Competent Authorities,
if any.
All records associated with the incident or near incident shall be maintained as Quality Records.
Be sure to update the MDR/MDVS Log when a file is closed.