PSUR Report
The vigilance database section of your PSUR, generated in seconds: FDA MAUDE adverse event trends, recalls, and enforcement classifications for your device and similar devices — with the documented, reproducible methodology auditors ask for.
Reporting period 2024-07 – 2026-06 · FDA data refreshed ~monthly
Percussor, Powered-Electric
Adverse events per month
2024-07 – 2026-06Events by type
Period vs. prior periodYour device vs. all similar devices
Name-matched — verify0 of 77 adverse events in the period (0.0%) matched the device/manufacturer names above. Matching is by name within the reported MAUDE fields — it can miss differently-spelled reports and include similarly-named devices. Verify individual reports before citing them in a PSUR.
Most reported coded problems
Top 15Recalls in period
0 totalNo recalls recorded for these product codes in the reporting period.
Adverse events by year
Methodology & data provenance
For your PSUR appendixSearch protocol: FDA MAUDE adverse event reports, FDA device recalls, and FDA enforcement reports (openFDA datasets) were queried for product code BYI, reporting period 2024-07 to 2026-06 (prior comparison period 2022-07 to 2024-06). Device-level attribution used name matching against “Exemplar Medical”, “LLC” — name matches are indicative, not authoritative.
Data coverage: adverse event data for these product codes extends through 2026-05. Source openFDA export dated 2026-06-30. Recall records with missing or implausible initiation dates (0 for these codes) are excluded from period counts.
Generated: 2026-07-06 07:40 UTC by BEUDAMED (beudamed.com/fda/psur-report). Dataset sizes: 25,039,198 adverse events, 58,607 recalls, 39,365 enforcement reports.
PSUR database searches, explained
Under the EU MDR, manufacturers must produce a Periodic Safety Update Report (PSUR) (Class IIa and above; a PMS report for Class I) on a defined schedule. A required part of that report is a survey of publicly available vigilance data — most importantly the FDA's MAUDE adverse event database and FDA recall records — covering both your own device and similar devices on the market (the "state of the art").
Doing this by hand means repeated MAUDE queries, manual export, deduplication, and trending — hours of work per report, repeated every reporting period. This tool runs the same search protocol in seconds and documents it: which datasets were queried, with which filters, when, and with what coverage — so the search is reproducible, which is exactly what a Notified Body auditor wants to see.
Event counts are grouped by the FDA's reported event type (death, injury, malfunction). Name-based device matching is clearly labeled as indicative: only you can confirm whether a specific MAUDE report concerns your device. Recall records with implausible dates are excluded and the exclusion is disclosed. All data is from the official openFDA datasets and refreshed approximately monthly.