MDRC logo
Explore
← Articles

Post-market surveillance · MDR · CE marking

CE marking is the start of the evidence cycle

Post-market surveillance must show what happens when the device leaves the controlled pre-market environment and enters routine use.

An MDR-compliant PMS system does more than collect complaints. It actively searches for information, detects change, tests the benefit-risk conclusion and turns evidence into controlled action.

pms.signal.monitor Live evidence · controlled decisions
01

Complaint rate

Within threshold
02

New literature signal

Review required
03

Service failure mode

Trend rising
System question

Does new evidence change safety, performance or benefit-risk?

Applies to

Every MDR device, including class I

Operating mode

Continuous, systematic and proactive

Technical file

PMS plan plus PMS report or PSUR

Main output

Evidence-based action, not data storage

The operating model

PMS is a closed evidence loop

Collection has no regulatory value unless the information is assessed, connected to the device’s existing evidence and converted into a documented decision.

01 Plan

Define what to monitor

Set sources, frequencies, responsibilities, methods, denominators, indicators and action thresholds.

02 Collect

Actively seek information

Gather device-specific experience and relevant external evidence instead of waiting for complaints.

03 Analyse

Test signals and trends

Use meaningful exposure data, severity, expected rates and predefined statistical or qualitative methods.

04 Act

Control the consequence

Update risk, clinical evidence, design, labelling, CAPA, PMCF or regulatory reporting where needed.

05 Verify

Confirm effectiveness

Check whether the action reduced the issue and feed the result into the next PMS cycle.

The cycle does not wait for the reporting date

A PSUR or PMS report summarises the work already performed. A safety signal, reportable incident or unacceptable risk must be handled when identified, not held until the next scheduled report.

Article 85 or Article 86

Choose the device class to see the reporting route

The PMS system applies to every class. What changes is the report, minimum update frequency and route for making the result available.

PMS report · Article 85

Summarise the data, conclusions and preventive or corrective actions

Update the report when necessary in accordance with the PMS plan. Keep it within the technical documentation and make it available to the competent authority on request.

Minimum cycle

Defined in the PMS plan

Earlier update

Whenever new evidence requires it

Availability

Competent authority on request

Do not reduce the obligation to a calendar reminder

The stated frequencies are minimums. New information can require immediate assessment, regulatory reporting, corrective action or an earlier report update.

Proactive collection

Build the source map before data arrive

For each source, define ownership, access, frequency, coding rules, denominator, analysis method and the decision that a threshold can trigger.

PMS

One controlled dataset

01

Complaints and incidents

Failure mode, harm, severity, cause, batch and reportability

02

Sales and exposure

Units, procedures, patients, use time and market distribution

03

Service and returns

Repairs, diagnostics, replacement parts and recurrent faults

04

Users and economic operators

Surveys, training feedback, importer and distributor information

05

Clinical and scientific evidence

PMCF, registries, studies, literature and state of the art

06

Production and suppliers

Nonconformities, yield, incoming controls and supplier changes

07

Similar devices

Public safety notices, recalls, literature and comparable technology

08

Regulatory intelligence

Authority communications, standards, guidance and new requirements

The denominator problem

Counts do not show whether risk is changing

Ten complaints can mean very different things. The interpretation depends on how many devices were used, for how long, in which population and under which conditions.

complaint rate

validated complaintsrelevant exposure

01

Units sold or actually used?

02

Unique devices, procedures or patients?

03

Installed base or time at risk?

04

Comparable markets and reporting behaviour?

From signal to action

One data point can enter several regulatory processes

Select an example to see the parallel questions the team should answer. The routes are connected and may all apply to the same event.

Example input

A user reports an unanticipated serious deterioration in health

Do not wait for root-cause certainty before starting vigilance assessment. The awareness date controls the reporting clock.

Vigilance

Assess serious-incident criteria and reporting deadline immediately.

Risk management

Check whether the hazard, sequence and severity were identified correctly.

CAPA or FSCA

Determine containment, affected population and field action.

Clinical evaluation

Assess whether the event changes clinical safety or benefit-risk.

2 days

Serious public health threat

10 days

Death or unanticipated serious deterioration

15 days

Other reportable serious incidents

Maximum calendar-day deadlines after awareness. Report immediately when possible and follow the current applicable reporting channel.

The update network

PMS must change the documents it tests

A frequent audit gap is a well-written report whose conclusions never reach the controlled lifecycle documents or operational processes.

01 · Risk

Risk management file

New hazards, occurrence estimates, residual risk, control effectiveness and overall benefit-risk.

02 · Clinical

Clinical evaluation

Clinical safety, performance, claims, state of the art, evidence gaps and continuing acceptability.

03 · Follow-up

PMCF plan and report

Residual uncertainty, long-term effects, underrepresented users and confirmation of clinical performance.

04 · Product

Design and labelling

Design changes, warnings, contraindications, instructions, usability and user training.

05 · Quality

CAPA and nonconformity

Root cause, extent, systemic action, implementation evidence and effectiveness checks.

06 · Operations

Production and suppliers

Process controls, acceptance criteria, supplier monitoring, batch traceability and change control.

07 · Regulatory

Vigilance and field action

Incident reports, trends, FSCAs, safety notices and communication with authorities and users.

08 · Governance

Management review

System effectiveness, unresolved signals, overdue activities, resources and strategic decisions.

Annex III planning test

Eight questions your PMS plan should answer

Use the checklist as a structural test. Device-specific methods, indicators and acceptance thresholds still need a documented rationale.

0 / 8 covered

Common audit findings

Four PMS shortcuts that do not work

The weakness is usually not the absence of data. It is the absence of a planned method for converting data into a timely, controlled conclusion.

“No complaints means no PMS activity”

Proactive PMS must search for information beyond complaints and document why the dataset is sufficient.

“Sales volume is always the denominator”

The denominator must reflect real exposure. A reusable device, implant and single-use accessory need different measures.

“The report can update the risk file later”

A new risk signal must be assessed when detected. The report records the decision; it does not postpone it.

“All devices can share one generic plan”

Grouping is acceptable only when scope, sources, methods and thresholds remain appropriate for every included device.

Practical questions

Questions manufacturers ask about PMS

The plan and report must remain specific to the device, its risk, clinical evidence, market experience and current regulatory route.

Yes. Every MDR device needs a post-market surveillance system and a PMS plan. A class I manufacturer documents the results and conclusions in a PMS report under Article 85, updates it when necessary and makes it available to the competent authority on request.

Make the evidence operational

Need a PMS system that works beyond the report?

MDRC can review your PMS plan, data sources, thresholds, reporting route and links to risk management, clinical evaluation, PMCF, vigilance and CAPA.

Review the PMS system
↑

Discuss your regulatory pathway

Whether you are developing medical software, an AI-enabled healthcare solution, a digital health platform or a software-driven medical device, we can help define the regulatory strategy, evidence requirements and next steps.

→

Where companies need support

Regulatory strategy
Technical documentation
Clinical and performance evidence
Software lifecycle and cybersecurity
Notified Body readiness

Start a discussion

 

Regulatory support for software medical devices, AI health technologies and digital healthcare solutions.


©2026 MDRC - Medical Devices Regulatory Compliance

Useful information

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

How to obtain CE marking for medical software under the EU MDR or IVDR?

Technical documentation for Medical Device Software in the EU

Read more >>


Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.

Send us an email:
info@mdrc-services.com

Or use the contact form below

 

Solutions

EU Authorised Representative (EC REP)

EU PRRC

Technical documentation

Risk management

Clinical evaluation

Notified Bodies

Quality management system

Post-market surveillance

Resources

Medical Device Regulation (MDR) - basics

CE-marking process for medical devices

CE-marking process for in vitro diagnostic medical devices

MDR technical documentation checklist

IVDR technical documentation checklist

Technical documentation checklist for medical device software (MDSW)

MDR-compliant quality system documentation checklist

MDR-compliant quality system documentation checklist for medical device software

Clinical Evaluation Plan checklist

Clinical Evaluation Report checklist

PRRC under MDR or IVDR

Articles

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

More articles >>

Devices

General medical devices and equipment

In vitro diagnostics (IVD)

Medical software

Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.