Post-Market Surveillance (PMS) is not an annual archival chore for Notified Body audits—it is the living feedback loop that drives continuous safety refinement and design evolution. PMX OS ingests real-world complaints, service tickets, and clinical registries, turning disparate field signals into verifiable closed-loop CAPA and requirement updates.
Under European Union Medical Device Regulation (EU MDR 2017/745), Articles 83 through 86 establish stringent expectations for Post-Market Surveillance (PMS) plans and Periodic Safety Update Reports (PSUR). Manufacturers of Class IIa, IIb, and III devices must systematically collect, record, and analyze real-world data regarding quality, performance, and clinical safety throughout the device’s expected lifetime. This PMS loop directly informs the continuous Clinical Evaluation Plan (CEP) and Post-Market Clinical Follow-up (PMCF) under Annex XIV Part B.
Simultaneously, under United States FDA regulations (21 CFR Part 803 for Medical Device Reporting and 21 CFR 820.198 for Complaint Files), manufacturers must execute rigorous reportability triage within strict legal windows: 30 days for events that may have caused or contributed to a serious injury, and 5 days for events necessitating remedial action to prevent substantial harm.
In legacy MedTech enterprises, customer service representatives transcribe unstructured clinician phone calls or patient support emails into free-text fields. These narrative notes sit unanalyzed in siloed customer relationship management (CRM) software until monthly or quarterly quality meetings.
PMX OS deploys dedicated clinical Natural Language Processing (NLP) models tuned on the International Medical Device Regulators Forum (IMDRF) adverse event terminology. Incoming text streams—such as *"Patient reported stinging warmth and mild redness after wearing the sensor on the chest for 30 hours"*—are automatically parsed, classified, and indexed under:
A0104 (Device Overheating).E0812 (Burn / Erythema).C0101 (Component Resistance Drift).By continuously correlating complaint frequency with Device History Record serial numbers and deployed firmware telemetry, PMX OS detects statistically significant spikes weeks before they breach traditional Shewhart control limits.
| Event Severity | Clinical Manifestation | Regulatory Timeline | PMX OS Automated Action |
|---|---|---|---|
| Death or Serious Deterioration | Deep dermal second/third-degree burn requiring hospitalization | Immediate / 2 to 5 Days (FDA / EUDAMED) | Auto-draft eMDR Form 3500A & trigger Executive Safety Alert |
| Malfunction (Reportable) | Sensor overheating trip suppressed; potential for burn if unremoved | 30 Days (FDA) | Assign to Quality Engineer for root cause & DHF hazard review |
| Non-Reportable Trend | Mild contact adhesive pruritus without tissue burn | Trend Review in Annual PSUR | Log to PMCF registry and monitor statistical baseline |
Periodic Safety Update Report covering 18,400 active deployed units. Summary risk-benefit ratio remains favorable following deployment of firmware patch v3.8.2.
Automated multi-factor correlation revealed that 84% of thermal complaints occurred in devices that combined Firmware 3.8.0 high-frequency polling with Sensor S-18 Lot #Y-2026-084.
Inspect Correlation Graph →Analyze monthly post-market complaint volumes from Jan 2026 to Aug 2026. Toggle filters to isolate how the June 2026 thermal spike correlates with Firmware 3.8.0 rollout and S-18 component variance.
Multi-variable regression analysis demonstrates that the 760% increase in complaint frequency during June 2026 was caused by the combined presence of Firmware v3.8.0 (which increased sensor polling frequency from 50Hz to 100Hz, raising baseline internal dissipation) and thermistor Lot #Y-2026-084 (+3.2% resistance shift).
How a post-market complaint traverses the entire medical product lifecycle: from signal detection to CAPA, risk matrix re-evaluation, requirement amendment, and Notified Body notification.
PMX OS AI agent ingests 38 complaints in June. NLP classifies 29 cases under IMDRF E0812 (Erythema) and 8 under reportable malfunction 21 CFR 803.
Signal SIG-2026-06Engineering isolates root cause: FW 3.8.0 polling duty cycle exacerbates S-18 lot resistance drift, under-reporting skin contact temperature by 1.8°C.
CAPA-2026-044Risk probability of occurrence for cutaneous thermal injury is escalated from P1 (improbable) to P3 (remote). Risk control mitigation deemed necessary.
RSK-0044 Rev GDesign input REQ-0184 is amended: device firmware must execute adaptive polling throttling if casing temperature rises faster than 0.2°C per 10 minutes.
REQ-0184 Rev 2.536-hour continuous bench stress test executed with adaptive throttling enabled. Thermal limit verified <40.2°C across all operating conditions.
V-0183 Passed (100%)Technical Documentation Annex II and PSUR updated. Change notification submitted to Notified Body TÜV SÜD. FDA Letter-to-File logged in DHF.
MDR Tech File Rev 4