eduKateSG · Why Science?
Turn adverse-event awareness into a timely, traceable report
Use FDA’s manufacturer MDR rules through death, serious injury and malfunction criteria, awareness dates, 30-day and 5-day reports, electronic submission, event files and follow-up.
Medical-device safety signals often begin as a phone call, complaint, service note, literature report or clinical message. A reporting system must decide quickly whether the information meets a legal threshold while the deeper investigation continues.
FDA’s Medical Device Reporting regulation requires manufacturers to report device-related deaths, serious injuries and qualifying malfunctions. Most reports are due within 30 calendar days; specified urgent circumstances use a five-work-day route.
Did you know? Filing an MDR does not prove that a device caused an event. The reporting threshold deliberately allows notification when information reasonably suggests a possible contribution, helping surveillance begin before every uncertainty is resolved.
This guide supports adverse-event and reporting literacy. It does not decide whether a specific event is reportable.
Chapter index
Chapters 1–9: reportability, awareness and deadlines
- 1. The MDR regulation is 21 CFR part 803
- 2. Manufacturer awareness starts the clock
- 3. Deaths are reportable
- 4. Serious injuries are reportable
- 5. Qualifying malfunctions are reportable
- 6. Most manufacturer reports use 30 calendar days
- 7. Five-day reports address urgent circumstances
- 8. Electronic submission is the standard route
- 9. Form 3500A organizes mandatory data
Chapters 10–17: event files, electronic reports and evidence limits
- 10. Causation need not be proven before reporting
- 11. Event files preserve the evidence route
- 12. Non-reportable decisions need rationale
- 13. Follow-up reports update new information
- 14. Corrections explain report changes
- 15. Complaint handling and MDR interact
- 16. Reports feed signal detection but have limits
- 17. A complete MDR receipt preserves timing and judgment
A medical-device report begins with awareness, event classification and a deadline. Mandatory reporting requirements help FDA and manufacturers identify and monitor significant device adverse events and qualifying malfunctions. This turns scattered complaints into reviewable surveillance evidence.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about the mdr regulation is 21 cfr part 803? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for the mdr regulation is 21 cfr part 803. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the mdr regulation is 21 cfr part 803, its identifier or version context, and one limit that must remain visible.
FDA’s MDR regulation uses reports of deaths, serious injuries and qualifying malfunctions to detect safety signals. Awareness can arise when an employee with responsibility receives information suggesting a reportable event. It also keeps a reporting threshold separate from a causal conclusion.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about manufacturer awareness starts the clock? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for manufacturer awareness starts the clock. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for manufacturer awareness starts the clock, its identifier or version context, and one limit that must remain visible.
A report is a notification, not a final proof that the device caused the event. A manufacturer reports when information reasonably suggests its device may have caused or contributed to a death. Electronic identifiers help updates remain connected to the original report.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about deaths are reportable? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for deaths are reportable. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for deaths are reportable, its identifier or version context, and one limit that must remain visible.
Strong event files preserve sources, dates, investigations and follow-up. Reports cover injuries or illnesses that are life threatening, cause permanent impairment or damage, or require intervention to prevent permanent harm. Timely reporting supports action while investigation continues.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about serious injuries are reportable? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for serious injuries are reportable. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for serious injuries are reportable, its identifier or version context, and one limit that must remain visible.
A medical-device report begins with awareness, event classification and a deadline. A malfunction is reportable when recurrence would be likely to cause or contribute to a death or serious injury. This turns scattered complaints into reviewable surveillance evidence.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about qualifying malfunctions are reportable? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for qualifying malfunctions are reportable. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for qualifying malfunctions are reportable, its identifier or version context, and one limit that must remain visible.
FDA’s MDR regulation uses reports of deaths, serious injuries and qualifying malfunctions to detect safety signals. Manufacturers submit initial reports within 30 calendar days after becoming aware of a reportable death, serious injury or malfunction. It also keeps a reporting threshold separate from a causal conclusion.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about most manufacturer reports use 30 calendar days? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for most manufacturer reports use 30 calendar days. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for most manufacturer reports use 30 calendar days, its identifier or version context, and one limit that must remain visible.
A report is a notification, not a final proof that the device caused the event. A report is due within five work days when FDA requests it or remedial action is needed to prevent an unreasonable risk of substantial public-health harm. Electronic identifiers help updates remain connected to the original report.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about five-day reports address urgent circumstances? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for five-day reports address urgent circumstances. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for five-day reports address urgent circumstances, its identifier or version context, and one limit that must remain visible.
Strong event files preserve sources, dates, investigations and follow-up. Manufacturers and importers generally submit MDRs electronically using the required systems and structured fields. Timely reporting supports action while investigation continues.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about electronic submission is the standard route? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for electronic submission is the standard route. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for electronic submission is the standard route, its identifier or version context, and one limit that must remain visible.
A medical-device report begins with awareness, event classification and a deadline. The report captures reporter, patient, event, device, manufacturer and evaluation information with applicable codes and dates. This turns scattered complaints into reviewable surveillance evidence.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about form 3500a organizes mandatory data? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for form 3500a organizes mandatory data. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for form 3500a organizes mandatory data, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Submit the record
10. Causation need not be proven before reporting
FDA’s MDR regulation uses reports of deaths, serious injuries and qualifying malfunctions to detect safety signals. The threshold is information that reasonably suggests the device may have caused or contributed, so investigation can continue after timely notification. It also keeps a reporting threshold separate from a causal conclusion.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about causation need not be proven before reporting? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for causation need not be proven before reporting. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for causation need not be proven before reporting, its identifier or version context, and one limit that must remain visible.
A report is a notification, not a final proof that the device caused the event. Manufacturers maintain files containing source information, evaluations, decisions, communications and copies or identifiers for submitted reports. Electronic identifiers help updates remain connected to the original report.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about event files preserve the evidence route? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for event files preserve the evidence route. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for event files preserve the evidence route, its identifier or version context, and one limit that must remain visible.
Strong event files preserve sources, dates, investigations and follow-up. When an event is not reported, the file should document the information reviewed and the reason the criteria were not met. Timely reporting supports action while investigation continues.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about non-reportable decisions need rationale? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for non-reportable decisions need rationale. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for non-reportable decisions need rationale, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Investigate and follow up
13. Follow-up reports update new information
A medical-device report begins with awareness, event classification and a deadline. Additional medical, device-evaluation or corrective information is submitted and linked to the original MDR when required. This turns scattered complaints into reviewable surveillance evidence.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about follow-up reports update new information? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for follow-up reports update new information. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for follow-up reports update new information, its identifier or version context, and one limit that must remain visible.
FDA’s MDR regulation uses reports of deaths, serious injuries and qualifying malfunctions to detect safety signals. A corrected report identifies the field changes and remains connected to the prior submission rather than silently replacing history. It also keeps a reporting threshold separate from a causal conclusion.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about corrections explain report changes? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for corrections explain report changes. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for corrections explain report changes, its identifier or version context, and one limit that must remain visible.
A report is a notification, not a final proof that the device caused the event. Complaints should be evaluated promptly for reporting, investigation and quality-system action without waiting for a final root cause. Electronic identifiers help updates remain connected to the original report.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about complaint handling and mdr interact? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for complaint handling and mdr interact. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for complaint handling and mdr interact, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Investigate and follow up
16. Reports feed signal detection but have limits
Strong event files preserve sources, dates, investigations and follow-up. MDR data are valuable surveillance inputs yet do not alone establish incidence, prevalence or causation. Timely reporting supports action while investigation continues.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about reports feed signal detection but have limits? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for reports feed signal detection but have limits. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for reports feed signal detection but have limits, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Investigate and follow up
17. A complete MDR receipt preserves timing and judgment
A medical-device report begins with awareness, event classification and a deadline. Record source, awareness date, event date, device and UDI, patient outcome, reportability assessment, deadline, report number, submission, evaluation, follow-up, corrections, CAPA and related safety action. This turns scattered complaints into reviewable surveillance evidence.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about a complete mdr receipt preserves timing and judgment? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for a complete mdr receipt preserves timing and judgment. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a complete mdr receipt preserves timing and judgment, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A timely report stays trustworthy when its uncertainty and updates remain visible
MDR links fast notification with ongoing investigation. The event file should show what the manufacturer knew, when it knew it, how reportability was assessed and how later evidence changed the record.
Save the source and receipt date, awareness date and responsible person, patient outcome, event narrative, device name, model, UDI, lot and serial, initial reporter, reportability criteria and rationale, 30-day or five-day deadline, electronic report and acknowledgement, manufacturer report number, evaluation, missing information attempts, follow-ups, corrections, complaints, CAPA, recalls or other action.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Awareness record | Starts the reporting assessment | Who received what information when? |
| Reportability decision | Applies death, injury or malfunction criteria | What evidence and uncertainty? |
| MDR submission | Notifies FDA in structured form | Which number and deadline? |
| Event file | Preserves investigation and updates | What changed after the initial report? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA Mandatory Reporting Requirements — accessed 25 October 2026.
- FDA Medical Device Reporting for Manufacturers Guidance — accessed 25 October 2026.
- FDA How to Report Medical Device Problems — accessed 25 October 2026.
- FDA eMDR Resources — accessed 25 October 2026.
- FDA MDR Data Files — accessed 25 October 2026.