MAUDE data represents reports of adverse events involving medical devices. The download data files consist of voluntary reports since June 1993, user facility reports since 1991, distributor reports since 1993, and manufacturer reports since August 1996. The searchable database data contains the last 10 year's data. MAUDE may not include reports made according to exemptions, variances, or alternative reporting requirements granted under 21 CFR 803.19.

An on-line search is available which allows you to search the CDRH's database information on medical devices which may have malfunctioned or caused a death or serious injury. MAUDE data is current through the end of the previous month. FDA seeks to include all reports received prior to the update. However, the inclusion of some reports may be delayed by technical or clerical difficulties.

MAUDE data is not intended to be used either to evaluate rates of adverse events or to compare adverse event occurrence rates across devices.

Please be aware that reports regarding device trade names may have been submitted under different manufacturer names. Searches only retrieve records that contain the search term(s) provided by the requester.

The data is also available in zipped files for downloading. The data is updated on a weekly basis.

These files were then compressed ("zipped") in order to save space. For these files to be useful to you, you'll first have to download them, unzip them, and then import them into a database or word processor for your further processing.

The releasable MAUDE data is presented in four logical records types. For this data to be meaningful, you should download all four types of files. The four record formats contain all releasable information on MEDWATCH Form 3500.

Downloading Hint: When downloading the MAUDE data files to a database such as Microsoft Access, it is recommended that you first open, then save the data file in Microsoft WORD. This will add an "end of record" marker to each MAUDE record that can be recognized by Microsoft ACCESS. For files such as the FOIDEV files, you may need to put in an extra character at the end of the first record prior to importing the file, otherwise the last column of data may be lost.

Master Event Data: A distinct master event data record will be present for each source reporting anevent. In other words, if a User Facility, Distributor, Manufacturer, and voluntary submitter all report an event, there will be four event records.

Device Data: Record Type 2 contains information related to the device(s) involved in the event.

Patient Data: Record Type 3 contains information related to the patient(s) involved in the event.

Text Data: Record Type 4 contains textual information from MEDWATCH Form Sections B5, H3, and H10.

All record types are linked via the MDR REPORT KEY.

For distributor reports which have had subsequent manufacturer reports, a special data element, MANUFACTURER LINK FLAG, will be set to 'Y'. In this case, the DISTRIBUTOR information (Section F on the master event data record) will be present; otherwise, these data elements will be blank.

The following files are available: (File Sizes are approximate)

[Accessibility]

Note: This documentation is intended to be used in conjunction with a copy of Medwatch Form 3500A and 3500.

Record/Data Characteristics:

• The data has one record per line, with the data fields in a pipe-delimited, (i.e., "|") format
• All data elements are alpha-numeric
• All text fields contain whatever data was provided/entered. If no information was provided/entered the field will be left empty. If an asterisk ("*") is present, it represents what was entered on the 3500/3500A.
• All "FLAG" data elements have the value of "Y" for Yes, "N" for No, or are blank if no data was available/entered.
• All fields identified as multiply-occurring represent data elements which may have multiple values. Each value will be present in the field, separated by a comma. The word "OTHER" may appear as one of the values if the "Other" box was checked off. If the whole field is blank, no data was reported/entered.
• Section G CONTACT address information may not necessarily be the address where the device is manufactured.

Special Note for REPORT NUMBER data element:

The REPORT NUMBER data element represents Manufacturer Report Number, Distributor Report Number, or internally-generated voluntary report number, depending on the source of the record.

This REPORT NUMBER field will be blank when:

• User Facility submitted the report
• Distributor report has not been followed by a subsequent Manufacturer report.

Special Notes for Voluntary Reports and User Facility Malfunction Reports:

The only data elements which will be present on the Master Event Record will be:

• NEW RECORD
• DEVICE EVENT KEY
• REPORT SOURCE CODE
• MDR REPORT KEY
• Section B

All other data elements will be blank.

MDRFOI file contains following 81 fields, delimited by pipe (|), one record per line:

1. MDR Report Key
2. Empty field (not used)
3. Report Number
4. Report Source Code

P = Voluntary report
U = User Facility report
D = Distributor report
M = Manufacturer report

5. Manufacturer Link Flag (internal information flag)
6. Number Devices in Event (if source code is 'P', field will be null)
7. Number Patient in Event (if source code is 'P', field will be null)
8. Date Received

SECTION-B

9. Adverse Event Flag (B1)
10. Product Problem Flag (B1)
11. Date Report (B4)
12. Date of Event (B3) -- new added, 2006
13. Single Use Flag (Reprocessor Flag) (D8) -- new added, 2006
14. Reporter Occupation Code (E3) -- new added, 2006

SECTION-E (if source code is 'P', Section E to H will contain no data)

15. Health Professional (E2)
16. Initial Report to FDA (E4)

Y = Yes
N = No
U = Unknown
* = No answer provided

SECTION-F

17. Date Facility Aware (F6)

18. Report Date (F8)
19. Report to FDA (F11)
20. Date Report to FDA (F11)
21. Event Location (F12)
22. Date Report to Manufacturer (F13)

SECTION-G (only for report source 'M', others sources will be null)

23. Manufacturer Contact Title Name (G1)
24. Manufacturer Contact First Name (G1)
25. Manufacturer Contact Last Name (G1)
26. Manufacturer Contact Street 1 (G1)
27. Manufacturer Contact Street 2 (G1)
28. Manufacturer Contact City (G1)
29. Manufacturer Contact State Code (G1)
30. Manufacturer Contact Zip Code (G1)
31. Manufacturer Contact Zip Code Ext (G1)
32. Manufacturer Contact Country Code
33. Manufacturer Contact Postal Code
34. Manufacturer Contact Phone No Area Code (G1)
35. Manufacturer Contact Phone No Exchange (G2)
36. Manufacturer Contact Phone No (G2)
37. Manufacturer Contact Phone No Ext (G2)
38. Manufacturer Contact Phone No Country Code
39. Manufacturer Contact Phone No City Code
40. Manufacturer Contact Phone No Local
41. Manufacturer G1 Name (G1)
42. Manufacturer G1 Street 1 (G1)
43. Manufacturer G1 Street 2 (G1)
44. Manufacturer G1 City (G1)
45. Manufacturer G1 State Code (G1)
46. Manufacturer G1 Zip Code (G1)
47. Manufacturer G1 Zip Code Ext (G1)
48. Manufacturer G1 Country Code
49. Manufacturer G1 Postal Code
50. Date Manufacturer Received (G4)

SECTION-H
51. Device Date Of Manufacture (H4)
52. Single Use Flag (H5)
53. Remedial Action (H7) -- multiple source type, separate by ','

RC = Recall
RP = Repair
RL = Replace
RB = Relabeling
OT = Other
NO = Notification
IN = Inspection
PM = Patient Monitoring
MA = Modification/Adjustment
* = Invalid Data

54. Previous Use Code (H8)
55. Removal/Correction Number (H9)
56. Event type (H1) -- only relevant for report sourcetype 'M'

D = Death
IN = Injury
IL = Injury
IJ = Injury
M = Malfunction
O = Other
* = No answer provided

57. Distributor Name (F3) -- if report source code = 'M' and
58. Distributor Address line 1 (F3)
59. Distributor Address line 2 (F3)
60. Distributor City (F3)
61. Distributor State Code (F3)
62. Distributor Zip Code (F3)
63. Distributor Zip Code Ext (F3)
64. Report to Manufacturer (F13)
65. Manufacturer Name (F14)
66. Manufacturer Address line 1 (F14)
67. Manufacturer Address line 2 (F14)
68. Manufacturer City (F14)
69. Manufacturer State Code (F14)
70. Manufacturer Zip Code (F14)
71. Manufacturer Zip Code Ext (F14)
72. Manufacturer Country Code (F14)
73. Manufacturer Postal Code (F14)
74. Type of Report (F7) !multiple submission type, separate by ','

I = Initial submission
F = Followup
X = Extra copy received
O = Other information submitted

75. Source Type (G3) -- multiple source type, separate by ','

00 Other
01 Foreign
02 Study
03 Literature
04 Consumer
05 Health Professional
06 User facility
07 Company representation
08 Distributor
99 Unknown
* Invalid data

76. Date Added
77. Date Changed
78. Reporter Country Code
79. PMA PMN Number
80. Exemption Number
81. Summary Report

DEVICE file contains following 45 fields, delimited by pipe (|), one record per line:

1. MDR Report Key
2. Device Event key
3. Implant Flag -- D6, new added; 2006
4. Date Removed Flag -- D7, new added; 2006; if flag in M or Y, print Date

U = Unknown
A = Not available
I = No information at this time
M = Month and year provided only, day defaults to 01
Y = Year provided only, day defaulted to 01, month defaulted to January

5. Device Sequence No -- from device report table
6. Date Received (from mdr_document table)

SECTION-D

7. Brand Name (D1)
8. Generic Name (D2)
9. Manufacturer Name (D3)
10. Manufacturer Address 1 (D3)
11. Manufacturer Address 2 (D3)
12. Manufacturer City (D3)
13. Manufacturer State Code (D3)
14. Manufacturer Zip Code (D3)
15. Manufacturer Zip Code ext (D3)
16. Manufacturer Country Code (D3)
17. Manufacturer Postal Code (D3)
18. Expiration Date of Device (D4)
19. Model Number (D4)
20. Catalog Number (D4)
21. Lot Number (D4)
22. Other ID Number (D4)
23. Device Operator (D5)
24. Device Availability (D10)

Y = Yes
N = No
R = Device was returned to manufacturer
* = No answer provided

25. Date Returned to Manufacturer (D10)
26. Device Report Product Code
27. Device Age (F9)
28. Device Evaluated by Manufacturer (H3)

Y = Yes
N = No
R = Device not returned to manufacturer
* = No answer provided

BASELINE SECTION (for records prior to 2009)

29. Baseline brand name
30. Baseline generic name
31. Baseline model no
32. Baseline catalog no
33. Baseline other id no
34. Baseline device family
35. Baseline shelf life contained in label

Y = Yes
N = No
A = Not applicable
* = No answer provided

36. Baseline shelf life in months
37. Baseline PMA flag
38. Baseline PMA no
39. Baseline 510(k) flag
40. Baseline 510(k) no
41. Baseline preamendment
42. Baseline transitional
43. Baseline 510(k exempt flag
44. Baseline date) first marketed
45. Baseline date ceased marketing

PATIENT file contains following 5 fields, delimited by pipe (|), one record per line:

1. MDR Report Key (from patient report table)
2. Patient Sequence Number (from patient report table)
3. Date Received (from mdr_document table)
4. Sequence Number||','|| Treatment -- multiple source type, separate by ';'
5. Sequence Number||','|| Outcome -- multiple source type, separate by ';'

L - Life Threatening
H - Hospitalization
S - Disability
C - Congenital Anomaly
R - Required Intervention
O - Other
* - Invalid Data
U - Unknown
I - No Information
A - Not Applicable
D - Death

TEXT file contains following 6 fields, delimited by pipe (|), one record per line:

1. MDR Report Key
2. MDR Text Key
3. Text Type Code (D=B5, E=H3, N=H10 from mdr_text table)
4. Patient Sequence Number (from mdr_text table)
5. Date Report (from mdr_text table)
6. Text (B5, or H3 or H10 from mdr_text table)

FOIDEVPROBLEM contains 2 fields, delimited by pipe (|), one record per line:
1. Device Problem Code
2. Problem Description

DEVICEPROBLEMCODES contains 2 fields, delimited by pipe (|), one record per line:
1. MDR Report Key
2. Device Problem Code -- (F10) new added; 2006

PATIENTPROBLEMDATA contains following 2 fields, delimited by pipe (|), one record per line:
1. Patient Problem Code
2. Problem Description

PATIENTPROBLEMCODE contains following 2 fields, delimited by pipe (|), one record per line:
1. MDR Report Key
2. Patient Problem Code

Device Operator Code Key

Event Location Code Key