FDA Medical Device Reporting: manufacturer deadlines under 21 CFR 803
Once a surgical robot or software device is on the market, manufacturers must report certain adverse events to the FDA. This page summarizes the reporting deadlines set by 21 CFR Part 803.
Ask your question
Free account requiredAnswers are written by a language model solely from this base's documents, with numbered sources. They can be wrong and aren't legal, medical or financial advice: check the sources before any important decision.
The two main deadlines
Manufacturers must submit reports of individual adverse events no later than 30 calendar days after becoming aware of a reportable death, serious injury or malfunction.
A shorter deadline of 5 work days applies to a reportable event that requires remedial action to prevent an unreasonable risk of substantial harm to public health, or to an event for which FDA has made a written request.
Format and awareness
Manufacturers and importers must submit initial and supplemental or followup reports to FDA in an electronic format that FDA can process, review and archive.
A manufacturer becomes aware of an event when any employee becomes aware of a reportable event. For 5-day reports tied to remedial action, awareness also arises when a person with management or supervisory responsibility over regulatory, scientific or technical staff learns, including through trend analysis, that remedial action is needed.
Frequently asked questions
What does remedial action mean in Part 803?
It means any action other than routine maintenance or servicing of a device, where that action is necessary to prevent recurrence of a reportable event.
Do importers have reporting deadlines too?
Yes. Importers must report to the manufacturer and to FDA within 30 calendar days of becoming aware of information suggesting a device may have caused or contributed to a death or serious injury. Reportable malfunctions go to the manufacturer within 30 calendar days.
Is there FDA guidance beyond the regulation itself?
Yes. The base includes the FDA's final guidance on Medical Device Reporting for Manufacturers, which explains how to apply Part 803 in practice.
Embed / API / MCP
Connect this base to Claude, Cursor, ChatGPT or your own app. Each API or MCP request costs β¬0.10, charged to your Kopik credit (not charged if nothing is found). You need an API key: create one from your dashboard.
MCP for your agents
This base's MCP server URL (tools ask_base and search_base):
https://kopik.io/api/mcp?base=us-fda-surgical-robotics-samdClaude Code, Cursor and other clients
claude mcp add --transport http kopik-us-fda-surgical-robotics-samd "https://kopik.io/api/mcp?base=us-fda-surgical-robotics-samd" --header "Authorization: Bearer kpk_β¦"{
"mcpServers": {
"kopik-us-fda-surgical-robotics-samd": {
"url": "https://kopik.io/api/mcp?base=us-fda-surgical-robotics-samd",
"headers": {
"Authorization": "Bearer kpk_β¦"
}
}
}
}REST API for your apps
mode is "answer" (written answer + sources) or "passages" (raw passages only). Add an optional maxPriceCents to cap the price: if the base costs more, the call is refused and nothing is charged.
curl -X POST https://kopik.io/api/v1/bases/us-fda-surgical-robotics-samd/query \
-H "Authorization: Bearer kpk_β¦" \
-H "Content-Type: application/json" \
-d '{"question": "Your question here", "mode": "answer"}'Getting started
- Create a key in your dashboard and top up your credit.
- Replace
kpk_β¦with your key. - Full details (responses, errors, JS and Python examples): developer docs.