How Smarteeva Automates PMCF Reporting Under EU MDR Requirements

What PMCF Means Under EU MDR Article 61

Post-Market Clinical Follow-up (PMCF) is the ongoing collection and review of clinical data on a CE-marked device once it is in everyday use. Under the EU Medical Device Regulation (EU MDR), PMCF is a continuous duty. Article 61 and Annex XIV Part B set the rules. Manufacturers must keep confirming the clinical safety and performance of their devices across the whole product lifecycle.

PMCF is a running programme, not a one-time study after launch. Its findings feed back into three places: the clinical evaluation, the risk management file, and the periodic safety reports (PSUR for Class IIa and above, PMSR for Class I).

Article 61 sets three things: when PMCF is required, what data it must produce, and how often the clinical evaluation must be updated. Implantable and Class III devices are updated in the PSUR every year. Class IIa and IIb devices follow longer cycles. Even so, the PMCF data must stay current between those cycles.

Treating PMCF as a periodic deliverable is where teams get caught, because gaps then show up at the next notified body audit. The audit-ready approach is to run PMCF as one connected workflow. That means continuous data intake, signal monitoring, and evaluation reports that update on their own.

‍

PMCF Compliance Mapped to EU MDR Article 61

Each Article 61 duty maps to a specific Smarteeva capability inside the connected PMCF workflow.

1. Continuous clinical evaluation. Connected real-world data feeds the clinical evaluation file all the time. No manual schedules. No batch refreshes.
2. PMCF plan inside the PMS plan. AI-generated PMCF plans link straight to the post-market surveillance plan in the same data model. The PMCF plan inherits device class, risk profile, and indication scope from the parent PMS plan.
3. PMCF evaluation report. The report refreshes on its own whenever new real-world data comes in. A clinical reviewer approves each update before it joins the regulatory submission package.
4. Real-world safety and performance data. Data intake covers electronic health records, patient registries, connected device telemetry, and field service data. Every data point keeps its source and timestamp.
5. Risk-benefit checks. Continuous signal monitoring flags a risk-benefit shift the moment the data crosses a set threshold. Each signal shows the supporting data, the statistical confidence, and the recommended action.
6. Spotting previously unknown risks. Signal detection runs across the whole device population and finds new risk patterns before they become PSUR findings. The model reads the connected dataset, not one complaint at a time.
7. Documented PMCF activities. The audit trail records every data source, signal, PMCF plan update, and report version, with timestamps and reviewer names. Auditors can trace any finding back to the underlying real-world data.

Why PMCF matters beyond compliance

The compliance case is clear. EU MDR requires PMCF, and letting it lapse puts your market authorization at risk. But PMCF data does more than satisfy a regulation.

Real-world data from PMCF also guides product decisions. If a device behaves differently in certain patient groups or clinical settings, that data shapes the next design change, label update, or instructions-for-use (IFU) revision. Teams who treat PMCF as a checkbox miss this product insight.

PMCF data speeds up future submissions too. Strong, well-documented follow-up data gives you a better evidence base for line extensions, new indications, and new markets. Regulators read a thorough PMCF programme as a sign that you take post-market responsibility seriously, and that can shape review timelines and approvals.

PMCF also adds the clinical layer that complaint tracking cannot. A complaint tells you something went wrong. PMCF data tells you whether the device's clinical performance is drifting in ways that need action before complaints pile up.

‍

Why Manual PMCF Reporting Fails

The PMCF activities a manufacturer runs depend on the device's risk class, its clinical history, and the gaps found in the original clinical evaluation.Common activities include:

• User surveys and questionnaires that collect structured feedback from clinicians using the device.
• Patient registries that track long-term outcomes across defined populations.
• Systematic literature reviews that monitor published evidence on the device or equivalent devices.
• Adverse event tracking that captures and analyzes safety signals from post-market reporting.
• New clinical investigations, in some cases, for high-risk Class III devices or implantables, built to answer questions the pre-market data left open.

Lower-risk devices lean more on existing data: complaint records, literature, and adverse event databases. Higher-risk devices may need active data collection through registries or prospective studies. In every case, the data must be documented, analyzed, and reported in a format regulators can review.

This is where the load falls hardest on quality and regulatory teams. Each activity produces data in a different format, from a different source, on a different timeline. Pulling it into one clear analysis and a structured report is manual and slow, and it repeats for every device and every reporting cycle.

‍

How Smarteeva Automates PMCF End-to-End

Smarteeva's PMCF workflow runs on the same infrastructure the platform already uses for PSURs, MIRs, MDRs, and risk management. So teams do not adopt a separate tool for clinical follow-up. They extend workflows they already run.

Data aggregation from existing sources

The platform pulls PMCF data from the systems where it already lives: complaint records, adverse event reports, literature feeds, clinical study data, and risk management files. There is no need to search five systems by hand and export into a spreadsheet. Smarteeva brings the inputs into one view, filtered by device, time period, and data type.

AI-powered analysis

Once the data is together, Smarteeva's AI layer analyzes it. It spots trends across complaint and adverse event data. It flags clinical signals that may point to a shift in the device's benefit-risk profile. It summarizes findings in language that matches regulatory reporting needs. The AI does not replace clinical judgment. It prepares the groundwork so your PMS staff can spend their time on interpretation and decisions, not data assembly.

One-click report generation

With the data gathered and analyzed, Smarteeva builds the PMCF report. You set it up by choosing the device, reporting period, and report type. The system pulls the content together, including data summaries, trend analyses, risk assessments, and literature findings, into a structured document formatted for submission. The draft then goes to PMS staff for review and approval.

Automated distribution

After review, the platform can send completed PMCF reports to the right regulatory authorities by email. That closes the loop from data collection to submission, with no manual packaging or sending.

‍

Frequently Asked Questions About PMCF Automation

1. What is the difference between PMCF and PMS under EU MDR? Post-Market Surveillance (PMS) is the broader programme covering all post-market activities. PMCF is the clinical data workstream inside PMS. It confirms the safety and performance of a CE-marked device through real-world clinical use. Article 84 governs PMS. Article 61 and Annex XIV Part B govern PMCF.
2. How often does a PMCF evaluation report need to be updated? Class III and implantable devices update the PMCF evaluation report as part of the annual PSUR cycle. Class IIa and IIb devices update when significant new evidence appears. Notified body audits expect PMCF to run as a continuous workflow. Most Smarteeva customers keep a rolling PMCF evaluation report that updates as new data arrives.
3. What data sources count toward PMCF under EU MDR? Electronic health records, patient registries, connected device telemetry, post-market clinical investigations, literature reviews, and structured customer feedback all count. The notified body looks for breadth across sources and a clear trace back to the clinical questions in the PMCF plan. Smarteeva supports intake from each of these source types through structured APIs.
4. Can PMCF be automated under EU MDR Article 61? Yes. Article 61 sets what PMCF must produce, not how the data must be collected or processed. Smarteeva automates data intake, signal detection, PMCF plan generation, and PMCF evaluation report production. A clinical reviewer stays in the approval loop for every output.
5. How does Smarteeva help with notified body audits on PMCF? Every PMCF activity on Smarteeva carries a full audit trail: data source, intake timestamp, signal detection logic, reviewer sign-off, and final report version. Auditors can trace any finding in a PMCF evaluation report back to the underlying real-world data in minutes, not days.

‍