Post-market surveillance in year one should track the data most likely to reveal early safety, performance, quality, and usability problems after launch. Your priority is to detect signals early enough to report, investigate, correct, and update the risk file before small issues become repeat findings.
The first 12 months after launch give you the clearest view of how the device performs outside controlled premarket conditions. Regulators set minimum expectations, but your real job is deciding which data deserves attention, which signals need escalation, and which records prove that your surveillance system works. Use the first year to build a disciplined operating rhythm across complaints, adverse events, clinical follow-up, risk management, and corrective and preventive action.
Why The First Year Of Post-Market Surveillance Sets The Tone
The first year is your early-warning period. Design assumptions, manufacturing variation, training gaps, labeling gaps, distributor practices, and user behavior all start showing up in real-world use. A strong post-market surveillance process helps you spot those patterns before they turn into repeat complaints, field actions, or audit findings.
You shouldn’t treat year one as a passive data collection exercise. Every data stream should connect to a decision: report the event, open an investigation, escalate a trend, update the risk file, revise labeling, initiate corrective and preventive action, or collect more clinical evidence. If a metric doesn’t support one of those decisions, it belongs lower on your dashboard.
The best year-one systems are practical. They don’t bury small teams under endless spreadsheets. They define which data gets reviewed, who reviews it, how often it gets reviewed, what thresholds trigger escalation, and where the outcome gets recorded.
Regulatory Anchors For Post-Market Surveillance: FDA, EU MDR, And ISO Requirements
For medical devices, your year-one plan needs to reflect the markets where the device is sold. In the United States, Food and Drug Administration (FDA) requirements include Medical Device Reporting under Title 21 Code of Federal Regulations Part 803. The FDA may also require postmarket surveillance under Section 522, covered by Title 21 Code of Federal Regulations Part 822.
In the European Union, the European Union Medical Device Regulation (EU MDR) requires a post-market surveillance system for every device. Article 83 covers the surveillance system, Article 84 covers the post-market surveillance plan, Article 86 covers the Periodic Safety Update Report (PSUR), and Article 87 covers serious incident reporting timelines. Annex III describes required plan elements, including data collection, analysis, communication, corrective and preventive action, trend reporting, and post-market clinical follow-up.
International Organization for Standardization (ISO) standards help you build the operating process behind those legal requirements. ISO 20416 gives guidance on post-market surveillance for medical device manufacturers. ISO 13485 connects feedback, analysis of data, and corrective and preventive action inside the quality management system. ISO 14971 requires production and post-production information to feed back into risk management.
What A Year-One Post-Market Surveillance Plan Must Contain
Your year-one post-market surveillance plan should define the data you collect, the method for reviewing it, and the actions triggered by findings. At minimum, it should cover complaint data, serious incidents, adverse event reports, non-serious events, trend analysis, post-market clinical follow-up, production feedback, servicing data, literature review, user feedback, distributor feedback, and risk management updates.
The plan also needs clear ownership. Regulatory affairs can manage reportability decisions, quality assurance can manage complaint handling and corrective and preventive action, clinical affairs can manage post-market clinical follow-up, and risk management owners can update the risk file. The exact structure depends on your company size, but the decision rights should never be vague.
Build the plan around review cadence. High-risk signals may need immediate escalation, complaints may need weekly or monthly review early after launch, and broader trend reviews may fit a quarterly rhythm. The point is to avoid waiting until the annual review or audit prep period to discover that your data has been sitting untouched.
Complaints And Serious Incidents: Your Highest-Priority Data Stream
Complaints and serious incidents deserve top placement in your year-one dashboard. They are closest to patient safety, user experience, product performance, and reportability obligations. A low complaint count can be reassuring, but it can also mean your intake channels are weak, distributors are not forwarding feedback, or users don’t know how to report issues.
Track complaint rates by product, model, lot or batch, region, customer type, severity, failure mode, and use setting. Raw complaint counts don’t tell you enough. A small number of complaints tied to the same failure mode, lot, or clinical workflow can carry more weight than a larger number of unrelated low-severity issues.
You also need to separate administrative complaints from potential safety and performance signals. Shipping issues, missing accessories, packaging damage, device malfunctions, user errors, labeling confusion, and adverse outcomes should not sit in one undifferentiated bucket. Clean categorization makes trend review, investigation, reporting, and risk updates much faster.
Adverse Event Reporting Timelines In The United States And European Union
Year one is the wrong time to improvise reportability decisions. In the United States, manufacturers generally report deaths, serious injuries, and certain malfunctions within 30 calendar days under FDA Medical Device Reporting rules. A 5-day report applies when an event requires remedial action to prevent an unreasonable risk of substantial harm to public health.
Under the European Union Medical Device Regulation, serious incident timelines are shorter in some cases. A serious public health threat must be reported within 2 days. Death or unanticipated serious deterioration in a person’s state of health must be reported within 10 days, and other serious incidents must be reported within 15 days.
Your year-one tracking system should record the event awareness date, triage date, reportability assessment, reporting decision, submission deadline, actual submission date, investigation status, and any follow-up report requirements. This protects you from missed deadlines and gives inspectors or notified body reviewers a clear audit trail. A simple date-driven tracker can prevent many avoidable findings.
Trend Analysis And Signal Detection: When Data Becomes Action
Trend analysis turns scattered feedback into decisions. In year one, you usually won’t have years of baseline data, so your thresholds need to be practical and documented. Compare current complaint rates against launch assumptions, risk acceptability criteria, similar products, prior validation findings, and early production volumes.
Track repeated failure modes, rising complaint rates, regional clusters, training-related errors, servicing patterns, customer support themes, and returns. A single serious incident may trigger immediate reporting, but a repeated non-serious issue can still signal a design, labeling, or manufacturing problem. Don’t wait for harm to occur before you evaluate a pattern.
Define escalation rules before the data arrives. A trigger can be a rate increase, repeated complaints tied to one failure mode, recurrence after corrective action, a new hazard, unexpected severity, or a mismatch between real-world use and the risk file. Your records should show what was reviewed, what decision was made, and why that decision was reasonable.
Post-Market Clinical Follow-Up In The First 12 Months
Post-market clinical follow-up (PMCF) is part of the clinical evidence cycle, not a separate paperwork exercise. In year one, it should help you confirm clinical performance, verify safety assumptions, detect rare or longer-term issues, and close evidence gaps that remain after launch. Under the European Union Medical Device Regulation, Annex XIV Part B covers PMCF plans and PMCF evaluation reports.
Your PMCF plan should define the objective, target population, data sources, endpoints, sample expectations, follow-up schedule, data collection methods, and evaluation method. For a newly launched device, useful sources can include registry data, clinical user feedback, surveys, observational data, literature, complaint data, and data from planned clinical follow-up activities. Choose methods that answer a real question rather than collecting data because a template asks for it.
Track PMCF enrollment, data completeness, protocol deviations, missing follow-up, adverse events, performance measures, and clinical evaluation impacts. If early clinical data conflicts with your expected performance or safety profile, you need a path for escalation. That path should connect clinical affairs, regulatory affairs, risk management, and quality assurance.
Risk Management File Updates And CAPA Integration
Your risk management file should not sit frozen after launch. ISO 14971 expects production and post-production information to feed back into risk management. In year one, that means complaints, serious incidents, trend signals, servicing data, manufacturing feedback, user feedback, and PMCF findings should be reviewed against known hazards, hazardous situations, harms, risk estimates, and risk controls.
Track whether each signal relates to a known risk, changes the estimated probability or severity, reveals a new sequence of events, exposes a new hazard, or shows that a risk control is not working as intended. Labeling changes, training changes, design changes, manufacturing controls, servicing changes, and field safety actions can all flow from that review. The record should show the connection between the post-market data and the risk decision.
Corrective and preventive action (CAPA) should be reserved for issues that require structured root cause investigation and effectiveness checks. Not every complaint needs CAPA, but repeated issues, serious events, systemic failures, failed controls, and recurring trends often do. Track CAPA initiation date, root cause, containment, correction, corrective action, preventive action, due dates, closure, and effectiveness evidence.
Building The First PSUR Or PMS Report Without Scrambling
If your device is sold under the European Union Medical Device Regulation, your reporting output depends on device class. Class IIa devices require a Periodic Safety Update Report at least every 2 years. Class IIb and Class III devices require one at least annually. Class I devices do not require a PSUR, but they still require a post-market surveillance system and suitable reporting outputs.
Don’t wait until the report is due to reconstruct the year. Build the report structure early, then feed it during routine reviews. Your working file should include sales or usage estimates, complaint summaries, serious incident summaries, trend analysis, benefit-risk conclusions, CAPA links, PMCF findings, risk file updates, and any preventive or corrective actions.
A good year-one report does more than repeat data tables. It explains what changed, what didn’t change, what was investigated, which signals were rejected, which actions were taken, and whether the device benefit-risk profile remains acceptable. That makes the report useful for management review, notified body review, and internal decision-making.
Common Year-One Post-Market Surveillance Mistakes And How To Prevent Them
One common mistake is treating “no complaints” as proof that the device is performing well. You need to confirm that complaint intake channels work, distributors understand reporting obligations, service teams route feedback properly, and customer support knows what counts as a potential complaint. Silent data streams deserve investigation, especially after launch.
Another mistake is collecting too much data without assigning decision criteria. Big spreadsheets can create a false sense of control. Your system needs defined thresholds, escalation paths, reportability review, risk file linkage, and CAPA criteria, or the data won’t lead anywhere useful.
Teams also get into trouble when post-market surveillance, complaint handling, PMCF, risk management, and CAPA operate in separate lanes. The same signal may touch every one of those processes. If your records don’t show how information moved between them, an auditor may see gaps even when the team did the work.
Year-One Tracking Checklist For Medical Device PMS
- Complaint rates and severity
- Reportable events and deadlines
- Trend signals and root causes
- PMCF progress and data quality
- Risk file, labeling, and CAPA updates
What To Keep Watching After The First Year
Post-market surveillance works best when year one creates a repeatable pattern: collect the right data, review it on schedule, act on signals, and document the decision trail. Your strongest tracking areas are complaints, serious incidents, adverse event timelines, trend signals, PMCF progress, risk updates, CAPA status, and required reports. Keep the system lean enough to run and disciplined enough to defend. If you can explain what you tracked, why it mattered, what changed, and what you did about it, your post-market surveillance process is doing its job.
References
- FDA Postmarket Requirements For Devices
- FDA Medical Device Reporting
- FDA Postmarket Surveillance Under Section 522
- European Union Medical Device Regulation 2017/745
- Medical Device Coordination Group Guidance Documents
- ISO 20416:2020 Medical Devices — Post-Market Surveillance For Manufacturers
- ISO 13485:2016 Medical Devices — Quality Management Systems
- ISO 14971:2019 Medical Devices — Application Of Risk Management To Medical Devices.
Maurizio Chiriva Internati (DBSc, PhDs) is a cancer immunologist and biotech entrepreneur with 20+ years in immuno-oncology. Co-founder and former CEO of Kiromic BioPharma (NASDAQ: KRBP), he has led AI-driven target discovery and translational programs, and has served on faculty at MD Anderson and Texas Tech.
