---
title: PMS and Labeling Updates: When Post-Market Data Requires IFU Changes
description: When PMS data shows a new risk, the IFU has to change. Here is how to decide between an IFU update, an FSN, and an FSCA under MDR.
authors: Tibor Zechmeister, Felix Lenhard
category: Post-Market Surveillance & Vigilance
primary_keyword: PMS labeling updates IFU changes MDR
canonical_url: https://zechmeister-solutions.com/en/blog/pms-labeling-updates-ifu-changes
source: zechmeister-solutions.com
license: All rights reserved. Content may be cited with attribution and a link to the canonical URL.
---

# PMS and Labeling Updates: When Post-Market Data Requires IFU Changes

*By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.*

> **Post-market surveillance under Article 83 of Regulation (EU) 2017/745 is not a reporting exercise. It is a feedback loop that has to change the device file when the data says so. When PMS data reveals a new hazard, a new use error pattern, a changed residual risk profile, or a signal that meets the Article 88 trend-reporting threshold, the Instructions for Use and the label often have to change with it. The decision tree is: update the risk file first, then decide whether an IFU or label change is the correct response, then decide whether that change also requires a Field Safety Corrective Action under Article 89 with a Field Safety Notice to users. Cosmetic edits go through normal change control; safety-driven changes go through FSCA.**

**By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.**

---

## TL;DR

- Article 83 of Regulation (EU) 2017/745 requires a PMS system that actively feeds back into risk management, clinical evaluation, and — where applicable — the Instructions for Use and labels. PMS that never changes the IFU is PMS that is not working.
- The trigger for an IFU update is a change in the Annex I General Safety and Performance Requirements baseline: a new residual risk, a reclassified use error, a new contraindication, a new warning, or a new user-training requirement. The source of each change traces to the ISO 14971 risk file update first.
- Article 88 trend reporting is a distinct PMS obligation: a statistically significant increase in the frequency or severity of non-serious incidents or expected undesirable side-effects that could have a significant impact on the benefit-risk analysis must be reported, and often triggers a parallel IFU or label change.
- An IFU change that addresses a safety risk already on the market typically requires a Field Safety Corrective Action under Article 89, communicated through a Field Safety Notice. A pure editorial IFU change does not.
- Every PMS-driven IFU or label change is a Notified Body notification question. Significant changes to the design or intended purpose require prior notification; changes implementing an FSCA have their own communication pathway. Get this wrong and you either block your own shipment or miss a mandatory notification.

---

## Why PMS-driven IFU changes are where audits get sharp

The audit pattern is consistent. A Notified Body auditor sits down with the PMS file and the IFU revision history side by side. They look for three things: does the PMS plan under Annex III match what the team is actually doing, do the PMS outputs show up as inputs into the risk file, and do the risk file updates show up as IFU or label changes where they should. If the PMS file is full of complaint data but the IFU has not moved in three years, the auditor's next question writes itself. If the risk file has a new residual risk from Q2 and the IFU still says what it said last January, that is a finding.

Founders get caught here because PMS feels like a reporting lane — data goes to Eudamed, a PSUR gets written, life continues. It is not. PMS is a control loop. The loop closes when the data changes the device file, which includes the IFU and the label. A PMS system that collects data and never changes the file is a compliance theatre exhibit, not a surveillance system.

The other reason this sharp edge exists: the IFU and the label are the only parts of the technical documentation the end user ever sees. When PMS data reveals that users are making a use error that could harm someone, the intervention has to happen where the user reads — on the label, in the warnings section, in the contraindications. Nowhere else in the file reaches them.

## What Article 83 actually demands

Article 83 of Regulation (EU) 2017/745 requires manufacturers to plan, establish, document, implement, maintain and update a post-market surveillance system proportionate to the risk class and appropriate for the type of device. (Regulation (EU) 2017/745, Article 83.) The PMS system is an integral part of the manufacturer's quality management system and has to actively and systematically gather, record and analyse relevant data on the quality, performance and safety of the device throughout its entire lifetime.

The Article 83 list of PMS purposes is specific. The system has to serve to update the benefit-risk determination and improve the risk management, to update the design and manufacturing information, the Instructions for Use and the labelling, to update the clinical evaluation, to update the summary of safety and clinical performance where applicable, to identify needs for preventive, corrective or field safety corrective action, to identify options to improve the usability, performance and safety of the device, and to contribute to the PMS of other devices where applicable.

Two of those purposes name the IFU and the labelling directly. The regulation is explicit: the PMS system exists, among other reasons, to change the IFU and the label when the data says so. MDCG 2025-10 on post-market surveillance reinforces the same point — PMS is a closed loop that feeds design, risk, clinical evaluation, IFU and labelling updates, not a data-collection lane that ends at a report. (MDCG 2025-10, Guidance on post-market surveillance of medical devices and in vitro diagnostic medical devices, December 2025.)

## The Annex III PMS plan as the specification

Annex III of the MDR lays out the technical documentation on the post-market surveillance system that the manufacturer has to draw up. (Regulation (EU) 2017/745, Annex III.) The PMS plan — the document at the centre of Annex III — has to specify the methods and tools to investigate complaints, keep track of non-serious incidents and expected undesirable side-effects, use the trend-reporting mechanism of Article 88, communicate effectively with competent authorities, Notified Bodies, economic operators and users, and — critically for this post — the methods and protocols to manage the events subject to the trend report, including methods to establish any statistically significant increase, and the methods and protocols to communicate with users and to implement corrective actions.

Translation: the PMS plan has to pre-specify how the team will decide when PMS data requires an IFU or label change. The trigger thresholds, the escalation path, and the change-control route all belong in the plan before the first post-market complaint arrives. A team that makes those decisions ad hoc each time either over-reacts and burns money on unneeded FSCAs or under-reacts and misses mandatory ones.

## The triggers that move from PMS data to IFU change

Not every PMS signal requires an IFU update. The triggers that do are specific and each one traces to a clause in Annex I, the risk file, or the clinical evaluation.

- **New residual risk identified.** A hazard shows up in complaints or incident data that was not in the risk file. ISO 14971 requires updating the risk analysis; if the control strategy for the new residual risk includes information for safety, the IFU gets a new warning. (EN ISO 14971:2019+A11:2021.)
- **Frequency or severity of a known residual risk increases.** A risk that was accepted at a certain frequency now occurs more often, or the harm is worse than the original estimate. The risk file is re-evaluated; if the new residual risk level requires stronger information-for-safety measures, the IFU changes.
- **Use-error pattern emerges.** PMS data shows users are consistently misunderstanding a step. The use specification and the usability file are updated; the IFU wording, step sequence, or warnings are revised accordingly.
- **New contraindication emerges from clinical data.** Post-market clinical follow-up reveals a patient group where outcomes are worse. The clinical evaluation is updated and a new contraindication is added to the IFU.
- **New interaction or compatibility finding.** A previously unidentified interaction with another device, drug, or environment is observed. The IFU's compatibility and warnings sections change.
- **Article 88 trend-reporting threshold crossed.** A statistically significant increase in non-serious incidents or expected undesirable side-effects is detected. Article 88 reporting is triggered, and the same data usually drives an IFU or label change in parallel.

Every trigger runs through the risk file first. The IFU is never the place where a new risk is declared — it is the place where a risk already recorded in the file is communicated to the user. Going directly from PMS signal to IFU edit without updating the risk file is a traceability break and a guaranteed audit finding.

## Article 88 trend reporting — the signal that often forces a label change

Article 88 of Regulation (EU) 2017/745 requires manufacturers to report, by means of the electronic system referred to in Article 92, any statistically significant increase in the frequency or severity of incidents that are not serious incidents or that are expected undesirable side-effects that could have a significant impact on the benefit-risk analysis and which have led or may lead to risks to the health or safety of patients, users or other persons that are unacceptable when weighed against the intended benefits. (Regulation (EU) 2017/745, Article 88.)

Two things matter for IFU and label decisions. First, the threshold is statistical, not anecdotal — the PMS plan has to specify how the trend is detected (control chart, baseline ratio, whatever method is appropriate and justified). MDCG 2023-3 Rev.2 provides the Q&A interpretation of vigilance terms and concepts including the trend-reporting mechanism. (MDCG 2023-3 Rev.2, January 2025.) Second, a trend that crosses the Article 88 threshold almost always reveals information that should be communicated to users — otherwise the risk profile on the label and in the IFU no longer matches reality. Article 88 reporting and IFU revision are parallel actions driven by the same data.

## When an IFU change also requires an FSCA

This is the decision that trips up startups. An IFU update for a next-generation device batch on the production line is different from an IFU update that addresses a risk on devices already in clinical use. Devices already in the field cannot be reached by updating the master IFU file. The users holding the old IFU have to be actively notified.

Article 89 of Regulation (EU) 2017/745 defines field safety corrective actions and the manufacturer's obligations to report them and to communicate them to users through Field Safety Notices. (Regulation (EU) 2017/745, Article 89.) The test is straightforward: if the IFU change addresses a risk to health that applies to devices already in use, the corrective action is an FSCA and the users get an FSN. If the change is editorial — a typo, a clarification that does not change the risk profile, a structural reorganisation — it is not an FSCA and goes through normal change control.

The grey zone is "clarification of an existing warning." If the clarification is cosmetic — rephrasing for readability with the same content — it is not an FSCA. If the clarification adds information a user would need to avoid harm that the original warning did not convey clearly enough, it is. MDCG 2023-3 Rev.2 and the project's [Field Safety Corrective Actions under MDR](/blog/field-safety-corrective-actions-fscas-mdr) post walk through the decision in more detail.

## The change control playbook

A PMS-driven IFU or label change runs through a specific sequence. Skipping steps is how things go wrong.

1. **PMS signal is logged and triaged.** The complaint, incident, PMCF observation, or trend-monitoring output enters the PMS data set with a timestamp and a source.
2. **Risk file is opened.** The signal is evaluated against the existing hazard list. New hazard, changed frequency, or changed severity — all three are captured in the ISO 14971 risk file update. If nothing in the risk file changes, the signal does not drive an IFU change.
3. **Clinical evaluation is consulted.** If the signal touches clinical performance, indications, or contraindications, the clinical evaluation is updated in parallel.
4. **Annex I GSPR baseline is re-checked.** Does the new situation still satisfy the general safety and performance requirements? If not, the control strategy changes — and information for safety is one of the control options.
5. **The IFU or label change is drafted.** The change traces back to a specific clause in the updated risk file, the clinical evaluation, or the usability file. No free-floating edits. The new text is checked against Annex I Chapter III Section 23.4 for completeness. (Regulation (EU) 2017/745, Annex I, Chapter III, Section 23.4.)
6. **Usability validation is run where required.** A warning that users cannot follow is not a warning. EN 62366-1 summative evaluation applies to the revised IFU content for any change that affects use safety.
7. **FSCA determination is made.** Is this change addressing a risk on devices already in the field? If yes, Article 89 FSCA machinery is triggered — risk assessment, FSN drafting, competent authority notification, user communication, effectiveness check.
8. **Notified Body notification is made where required.** Significant changes to the intended purpose or the device design that affect the IFU claims or warnings may require prior NB notification under the applicable conformity assessment route. FSCAs have their own notification obligations. A change that hits both pathways has to satisfy both.
9. **Document control closes the loop.** The IFU revision, the label revision, the risk file update, the clinical evaluation update and the PMS plan update all carry the same traceable change reference under EN ISO 13485:2016+A11:2021 document control.
10. **Translations follow.** Every language version of the IFU has to be updated, validated and re-shipped under the same change reference. Translation drift at the post-market update stage is a classic finding.

## A worked scenario — what "PMS changes the IFU" looks like in practice

A small startup ships a Class IIa diagnostic device to 140 hospital customers across six Member States. At month nine of commercial availability, PMS data starts showing a pattern: two complaints in month seven, four in month eight, seven in month nine. All of them describe the same use error — operators skipping a calibration step because the IFU wording was ambiguous about whether it was required daily or only at first installation.

The team opens the risk file. The calibration step was controlled by information for safety, and the residual risk was accepted at a low frequency. The data now shows the frequency is higher than assumed and rising. That is a frequency change in the residual risk profile. The team updates the risk file, re-evaluates the residual risk level, and concludes the control strategy needs to be strengthened. The IFU wording for the calibration step is rewritten — unambiguous, one instruction per line, a new warning box at the top of the section.

Before the edit ships, the team runs the Article 88 trend-reporting analysis. The rise in complaints about the calibration step is statistically significant against the baseline established in the PMS plan. Because the use error could lead to an incorrect diagnostic result, the impact on benefit-risk is not negligible. The team files an Article 88 trend report through the electronic system referenced by Article 92.

Next question: is this an FSCA? Devices are already in the field with the old IFU. The use error has real patient-safety implications — a missed calibration can produce a wrong result. The team determines this is an FSCA under Article 89, drafts a Field Safety Notice, notifies the competent authorities, and communicates to all 140 hospital customers. The FSN references the revised IFU section and asks users to replace the old IFU with the new version and to confirm receipt.

The Notified Body is informed of the FSCA through the Article 89 pathway. The IFU revision itself — because it does not change the intended purpose or the device design, only the calibration wording driven by a post-market safety signal — does not require a separate prior significant-change notification. The team documents that determination in the change record so the next audit can see the reasoning.

Three months later, PMS data shows the calibration complaint rate has dropped to zero. The FSCA effectiveness check passes, the PMS plan records the closed loop, and the PSUR for the next cycle includes the full trace from complaint to risk update to IFU revision to FSCA to verified effectiveness. That is what Article 83 means by a PMS system "actively" feeding back into the file.

## Reality Check — Where do you stand?

1. Does your PMS plan under Annex III specify the thresholds and methods that will trigger an IFU or label change, or is that decision ad hoc each time?
2. When was the last time a PMS signal caused your IFU or label to change? If the answer is "never," is that because the data genuinely shows no reason, or because your loop does not close?
3. For every IFU revision in your document history, can you trace the trigger back to a specific risk file update, clinical evaluation update, or usability file update?
4. Does your team know how to tell an editorial IFU change from a safety-driven one, and does your change-control procedure route them differently?
5. Does your Article 88 trend-reporting method exist on paper with a defined statistical threshold, or is it an informal judgement call?
6. When a PMS-driven IFU change is an FSCA, does your procedure cover FSN drafting, competent authority notification, user communication, and effectiveness verification?
7. Are every language version of your IFU and every market you ship to covered by the same change-control reference when a PMS-driven update ships?

## Frequently Asked Questions

**Does every PMS signal require an IFU update?**
No. Most PMS data confirms the existing risk profile and requires no change. An IFU update is triggered when PMS data changes the risk file — a new residual risk, a changed frequency or severity of a known risk, or a use-error pattern that requires new or revised information for safety. Signals that do not change the risk file do not drive IFU changes. (Regulation (EU) 2017/745, Article 83.)

**What is the difference between an IFU update and a Field Safety Corrective Action?**
An IFU update is a document change. An FSCA under Article 89 is a corrective action taken in the field to address a risk on devices already in use. If the IFU change addresses a safety risk on marketed devices, it is the mechanism by which the FSCA reaches users, and a Field Safety Notice has to be issued. If the IFU change is purely for new production or is editorial, it is normal change control.

**When does Article 88 trend reporting apply?**
Article 88 applies when the manufacturer detects a statistically significant increase in the frequency or severity of non-serious incidents or expected undesirable side-effects that could have a significant impact on the benefit-risk analysis. The threshold must be defined in the PMS plan using a justified statistical method. A trend report does not replace an IFU update — the two often run in parallel. (Regulation (EU) 2017/745, Article 88.)

**Do we need to notify the Notified Body every time we update the IFU?**
Not every time. Editorial changes do not trigger NB notification. Changes that affect the intended purpose, the claims, the indications or contraindications, or that are part of a significant change to design or manufacturing, typically do require notification under the applicable conformity assessment route. FSCAs have their own Article 89 notification pathway. The PMS plan and the change-control procedure should specify the decision criteria.

**Where does the PMS plan say all of this should be handled?**
Annex III of Regulation (EU) 2017/745 requires the PMS plan to specify the methods and protocols for handling trend-reporting events, the communication to users, and the implementation of corrective actions. That is where the IFU-change decision tree belongs — in the plan, before the first signal arrives. MDCG 2025-10 gives the current interpretation of PMS system expectations. (Regulation (EU) 2017/745, Annex III; MDCG 2025-10, December 2025.)

**What happens if we update the IFU but forget the translations?**
A translated IFU that no longer matches the master IFU is a document-control nonconformity under EN ISO 13485, a language-obligation nonconformity under Article 10(11), and — if the translation gap affects safety information — a potential FSCA in the affected Member State. Every PMS-driven IFU update has to propagate through every language version under the same change reference.

## Related reading

- [Instructions for Use Under MDR: How to Write Compliant IFUs](/blog/instructions-for-use-mdr-compliant) — the Section 23.4 baseline every IFU revision has to satisfy.
- [Field Safety Corrective Actions (FSCAs) Under MDR](/blog/field-safety-corrective-actions-fscas-mdr) — the Article 89 mechanism that turns an IFU safety update into a notified action.
- [Trend Reporting Under MDR Article 88](/blog/trend-reporting-mdr-article-88) — the statistical threshold and reporting mechanism for non-serious incident trends.
- [The PMS Plan Under Annex III](/blog/pms-plan-annex-iii-mdr) — how to specify the IFU-change decision tree before the first signal arrives.
- [PSUR and PMS Report Under MDR](/blog/psur-pms-report-mdr) — where PMS-driven changes are documented for the regulator and the Notified Body.

## Sources

1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, Article 83 (Post-market surveillance system of the manufacturer), Article 88 (Trend reporting), Article 89 (Analysis of serious incidents and field safety corrective actions), Annex I Chapter III Section 23.4 (Information in the instructions for use), Annex III (Technical documentation on post-market surveillance). Official Journal L 117, 5.5.2017.
2. MDCG 2025-10, Guidance on post-market surveillance of medical devices and in vitro diagnostic medical devices, December 2025.
3. MDCG 2023-3 Rev.2, Questions and Answers on vigilance terms and concepts as outlined in Regulation (EU) 2017/745 and Regulation (EU) 2017/746, January 2025.
4. EN ISO 14971:2019+A11:2021, Medical devices — Application of risk management to medical devices.
5. EN ISO 13485:2016+A11:2021, Medical devices — Quality management systems — Requirements for regulatory purposes.

---

*This post is part of the Post-Market Surveillance & Vigilance cluster in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. Tibor has watched this loop close and fail on both sides of the Notified Body table — the PMS file that changed the IFU on time, and the one that did not. The difference is almost always whether the PMS plan specified the decision tree before the first complaint arrived, or tried to invent it after.*

---

*This post is part of the [Post-Market Surveillance & Vigilance](https://zechmeister-solutions.com/en/blog/category/pms-vigilance) cluster in the [Subtract to Ship: MDR Blog](https://zechmeister-solutions.com/en/blog). For EU MDR certification consulting, see [zechmeister-solutions.com](https://zechmeister-solutions.com).*