> ## Documentation Index
> Fetch the complete documentation index at: https://docs.withdovetail.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Post-Market Surveillance Plan

> Establish systematic monitoring approach ensuring ongoing device safety and regulatory compliance.

## Summary

The Post-Market Surveillance Plan establishes your systematic approach to **monitoring device safety and performance** after market release. This plan defines data collection methods, analysis procedures, and reporting requirements to ensure ongoing compliance with regulatory obligations and patient safety.

## Why is Post-Market Surveillance Plan important?

Post-market surveillance exists because **real-world device performance** often differs from controlled testing environments. Regulatory authorities require manufacturers to **continuously monitor** their devices to identify previously unknown risks, confirm expected performance, and detect emerging safety issues. This proactive monitoring protects patients, maintains regulatory compliance, and provides valuable data for device improvements. Without a structured surveillance plan, you risk missing critical safety signals that could lead to patient harm, regulatory enforcement actions, or costly device recalls.

## Regulatory Context

<Tabs>
  <Tab title="FDA">
    Under **21 CFR Part 820** (Quality System Regulation) and **21 CFR Part 803** (Medical Device Reporting):

    * Post-market surveillance is **mandatory** under Section 820.100 (Corrective and Preventive Actions)
    * Must establish procedures for **data collection and analysis** from various sources
    * **Medical Device Reporting (MDR)** requires reporting of deaths, serious injuries, and malfunctions
    * **Periodic reporting** may be required for certain device types

    <Warning>
      **Special attention required for:**

      * Software medical devices requiring **cybersecurity monitoring** (FDA Guidance 2022)
      * Class III devices with **enhanced post-market study requirements**
      * Devices with **FDA-mandated post-market studies** as condition of approval
      * **Unique Device Identification (UDI)** integration for traceability
    </Warning>
  </Tab>

  <Tab title="MDR">
    Under **EU MDR 2017/745**:

    * Post-market surveillance system is **mandatory** under Article 83
    * Must comply with **Annex III requirements** for systematic data collection
    * **Post-Market Surveillance Report** required annually for Class I devices, others as specified
    * Integration with **EUDAMED database** for incident reporting

    <Warning>
      **Special attention required for:**

      * **Post-Market Clinical Follow-up (PMCF)** requirements for higher-risk devices
      * **Periodic Safety Update Reports (PSUR)** for implantable devices and Class III devices
      * **Vigilance reporting** within specified timeframes (Article 87)
      * **Trend reporting** for statistically significant increases in incidents
    </Warning>
  </Tab>
</Tabs>

## Guide

Your Post-Market Surveillance Plan must establish **systematic procedures** for collecting, analyzing, and acting on post-market data. The plan serves as your roadmap for ongoing device monitoring and regulatory compliance.

### Data Collection Sources

**Define comprehensive data inputs** that will provide visibility into device performance. Your plan must specify how you'll collect information from **vigilance databases**, including FDA MAUDE, BfArM, and Swissmedic systems. Establish **search keywords** specific to your device type and intended use to ensure relevant incident identification. Include procedures for monitoring **complaints and feedback** from users, distributors, and healthcare providers.

**Establish complaint management integration** by defining which complaints require logging in your quality management system versus general customer support issues. Focus on complaints related to **device performance, safety concerns, or unexpected behaviors** that could indicate emerging risks.

**Plan for literature and registry monitoring** by identifying relevant medical journals, conference proceedings, and device registries that may contain safety information about your device or similar products. This includes monitoring **competitor recalls** and **field safety notices** that might indicate industry-wide issues.

### Analysis and Trending Methodology

**Implement statistical trend analysis** using appropriate methods such as the **Mann-Kendall test** for identifying significant increases in incident frequency or severity. Define your **significance thresholds** (typically p-value \< 0.05) and establish procedures for investigating positive trends.

**Calculate complaint rates** by comparing complaint volumes against device sales or installation numbers. This provides context for determining whether complaint levels represent normal variation or concerning trends requiring investigation.

**Establish risk assessment integration** by defining how post-market findings will trigger updates to your risk management file. Include procedures for determining when new risks require immediate reporting versus inclusion in periodic reports.

### Reporting and Documentation Requirements

**Define reporting timelines** based on your device classification and regulatory requirements. Specify when you'll generate **Post-Market Surveillance Reports**, **Periodic Safety Update Reports**, or other required documentation.

**Establish escalation procedures** for serious incidents requiring immediate regulatory notification. Include clear criteria for determining reportability and timelines for submission to appropriate authorities.

**Plan for corrective action integration** by defining how surveillance findings will trigger your CAPA system when risks exceed acceptable levels or new hazards are identified.

### Implementation and Review Procedures

**Assign responsibilities** for surveillance activities, including data collection, analysis, and reporting. Ensure personnel have appropriate training and access to necessary databases and systems.

**Establish review frequencies** for surveillance data analysis. While formal reports may be annual, ongoing monitoring should occur more frequently to enable rapid response to emerging issues.

**Plan for surveillance plan updates** as your device evolves, market conditions change, or regulatory requirements are modified. Include procedures for version control and approval of plan revisions.

## Example

**Scenario:** You manufacture a mobile health app that monitors blood glucose levels and provides dosing recommendations. Your Post-Market Surveillance Plan establishes monthly vigilance database searches, quarterly complaint analysis, and annual comprehensive reporting.

### Post-Market Surveillance Plan for GlucoTrack Mobile Health Application

**1. Scope**
This plan describes post-market surveillance activities for GlucoTrack v2.1, a Class II mobile medical device application for diabetes management. The plan addresses data collection from vigilance databases, user complaints, and clinical literature to ensure ongoing device safety and performance monitoring.

**2. PMS Data Inputs**

**2.1 Vigilance Data**
Monthly searches of FDA MAUDE, BfArM, and Swissmedic databases using keywords: "glucose monitoring app," "diabetes software," "insulin dosing error," "hypoglycemic event," "mobile health device malfunction."

**2.2 Complaints Data**
Integration with customer support system to identify complaints related to:

* Incorrect glucose readings or calculations
* App crashes during critical functions
* Dosing recommendation errors
* Data synchronization failures
* User interface confusion leading to medication errors

Complaint rate calculation: Monthly complaints ÷ Active monthly users × 1000

**2.3 Literature Monitoring**
Quarterly review of diabetes technology journals and conference proceedings for reports of similar device issues or emerging safety concerns.

**3. Trend Analysis Methodology**
Mann-Kendall test applied to monthly complaint data with significance threshold p \< 0.05. Positive trends trigger immediate investigation and potential risk assessment updates.

**4. Reporting Schedule**

* Monthly: Internal surveillance data review
* Quarterly: Complaint trend analysis and literature review
* Annually: Comprehensive Post-Market Surveillance Report
* As needed: Serious incident reports within 24 hours of identification

**5. Responsibilities**
Quality Assurance Manager: Database monitoring and trend analysis
Regulatory Affairs Specialist: Report preparation and submission
Clinical Affairs: Literature review and clinical significance assessment

## Q\&A

<AccordionGroup>
  <Accordion title="What is the purpose of post-market surveillance?">
    Post-market surveillance monitors your device after market release to identify safety issues, confirm expected performance, and detect emerging risks that weren't apparent during pre-market testing. It's required to ensure ongoing patient safety and regulatory compliance.
  </Accordion>

  <Accordion title="How should we manage customer feedback and complaints?">
    Log only complaints related to device performance or safety in your complaint management system. General feedback or support issues that can be resolved with instructions don't need formal logging. Focus on complaints that could indicate device malfunctions or safety concerns.
  </Accordion>

  <Accordion title="What should be done if a new risk is identified during vigilance database review?">
    If you identify a new risk during vigilance database review, add it to your risk assessment to ensure all foreseeable risks are accounted for. Update your Risk Management Report and determine if immediate regulatory reporting is required based on the risk's severity and probability.
  </Accordion>

  <Accordion title="How can we handle increased complaint volume effectively?">
    Implement a ticket management system that categorizes medical device-related complaints separately from general support issues. Log all complaints but mark their relevance to device safety and performance. This ensures regulatory compliance while managing workflow efficiently.
  </Accordion>

  <Accordion title="How should complaints be logged and categorized?">
    Maintain a system that categorizes complaints based on their relevance to device safety and performance. Track whether complaints relate to device malfunctions, user errors, or safety concerns. This categorization facilitates trend analysis and regulatory reporting requirements.
  </Accordion>
</AccordionGroup>