--- title: PMS for Multi-Market Devices: Coordinating Surveillance Across EU Member States description: PMS for a device sold across multiple EU Member States needs coordination across competent authorities. Here is how to design it under MDR. authors: Tibor Zechmeister, Felix Lenhard category: Post-Market Surveillance & Vigilance primary_keyword: PMS multi-market EU coordination canonical_url: https://zechmeister-solutions.com/en/blog/pms-multi-market-coordinating-eu source: zechmeister-solutions.com license: All rights reserved. Content may be cited with attribution and a link to the canonical URL. --- # PMS for Multi-Market Devices: Coordinating Surveillance Across EU Member States *By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.* > **PMS multi-market EU coordination means running a single post-market surveillance system under MDR Articles 83 to 86 that simultaneously satisfies the reporting, language, and authority-interaction obligations of every EU Member State where the device is placed on the market. The MDR is a single Regulation, but the competent authorities are national, the languages are national, and the complaint channels are national. Eudamed, the electronic system established under Article 92, is the central spine that holds the cross-border picture together. A multi-market PMS system works when one plan describes how data from every country flows into one analysis, one report, and one coordinated corrective action.** **By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.** --- ## TL;DR - A CE-marked device can be placed on the market in all 27 EU Member States under one Regulation, but PMS obligations touch 27 competent authorities, multiple languages, and country-specific complaint and incident-reporting channels. - The PMS plan required by MDR Article 84 and Annex III must describe how data from every market where the device is sold is collected, routed, and analysed as one coherent system. - Eudamed, established under MDR Article 92, is the central electronic system for vigilance reports, PSURs for Class III and implantable devices, and field safety notices. It is the single point of cross-border visibility. - Field safety corrective actions under Article 89 that affect devices in more than one Member State must be coordinated so that every affected authority receives consistent information on the same timeline. - MDCG 2025-10 (December 2025) is the operational guidance notified bodies apply when assessing whether a multi-market PMS system actually runs rather than only existing on paper. --- ## Opener — one device, many doorways A startup that sells its CE-marked device in five EU Member States has one Regulation governing it, one notified body reviewing it, one technical file describing it, and one set of MDR obligations applying to it. That is the clean picture. The less clean picture is the one that emerges the first time something goes wrong in one country at 08:00 on a Tuesday. A distributor in one Member State receives a complaint in the local language. A healthcare professional in a second Member State reports a suspected incident to their national competent authority directly. A third country's authority sends a routine post-market questionnaire to the manufacturer with a 30-day response window. None of these three inputs arrive in the same format, through the same channel, or in the same language. All three belong to the same PMS system. The PMS plan either describes how that system handles all three, or it does not — and if it does not, the fourth call of the day is usually from the notified body asking why. Multi-market PMS is not a separate framework under the MDR. It is the ordinary PMS framework applied with deliberate coordination across borders. The Regulation does not give startups a pass because they sell in five countries instead of one. It expects the system to scale. ## The multi-market PMS challenge MDR Article 83 requires every manufacturer to plan, establish, document, implement, maintain, and update a PMS system proportionate to the risk class and appropriate for the type of device. Article 83(2) requires the system to actively and systematically gather, record, and analyse relevant data on the quality, performance, and safety of the device throughout its entire lifetime. The words "actively and systematically" carry the multi-market weight. A system that collects data well in the home market and passively in four other markets is not active and systematic across all five. It is active in one and reactive in the rest. The challenge has three axes. First, data sources differ by country. Complaint volumes, healthcare system structures, distributor maturity, and user populations are not uniform. Second, regulatory interfaces differ by country. Each Member State has its own competent authority, with its own preferred communication channels, its own interpretation of borderline vigilance cases, and often its own national forms. Third, languages differ. A complaint written in Italian and a complaint written in Polish describing the same failure mode must end up in the same analysis bucket, not two unrelated files in two different folders. A multi-market PMS system is therefore a coordination problem as much as a data problem. The Regulation is harmonised; the execution is not. The plan has to bridge that gap. ## Language and reporting differences across Member States The MDR does not prescribe one operating language for manufacturers. It does, however, expect manufacturers to communicate with competent authorities, users, and patients in languages those parties understand. Instructions for use must be provided in the official languages of the Member States where the device is made available, as specified by each Member State under Article 10(11). The same pragmatic reality applies to PMS inputs. A complaint in German from Austria and a complaint in French from Belgium cannot be ignored because the PMS system runs in English. Three practical consequences flow from this for multi-market startups. **Complaint intake must accept local languages.** The distributor, the local user, the healthcare professional, the patient — none of them is obligated to complain in English. The PMS plan must describe how non-English inputs are received, translated if needed, and logged in a way that preserves the original language source for traceability. **Reports to competent authorities may need to be submitted in the national language.** Some Member States accept English for manufacturer communications; others require the official national language for formal submissions, particularly for field safety notices directed at users. Field safety notices distributed to users under Article 89(8) are generally expected in the languages of the affected Member States. The plan must know which countries require which languages and budget for translation turnaround within the vigilance timelines of Articles 87 and 88. **Trend analysis must pool data across language boundaries.** A PMS system that produces one trend dashboard per country is not producing a trend analysis of the device — it is producing a trend analysis of one market at a time. Annex III requires methods to identify any statistically significant increase in frequency or severity of incidents. Statistical significance requires pooled data. Pooled data requires translation and normalisation before analysis, not after. None of this is optional. It is the practical price of placing a device on more than one national market under a single Regulation. ## Eudamed as the central electronic system Eudamed is the European Database on Medical Devices, established under MDR Article 33 and operationalised through the electronic system referenced in Article 92. For multi-market PMS, Eudamed is the one place where the cross-border picture is designed to live. Article 92 of the MDR establishes the electronic system on vigilance and on post-market surveillance. Through that electronic system, manufacturers submit vigilance reports on serious incidents and field safety corrective actions under Articles 87 to 89, and Periodic Safety Update Reports for Class III and implantable devices under Article 86(2). Competent authorities of all Member States access this information. The notified body involved in the conformity assessment accesses and evaluates the PSURs for Class III and implantable devices and adds its evaluation to the electronic system. Commission Implementing Regulation (EU) 2021/2078 lays down the detailed rules for the application of Regulation (EU) 2017/745 as regards Eudamed, including registration, access, data ownership, functioning, and information security. For a multi-market manufacturer, Eudamed is therefore not "yet another portal." It is the system through which a single vigilance report reaches every competent authority that needs to see it, without the manufacturer having to submit the same report to each authority in parallel. That is the efficiency the Regulation intends. Two practical reminders matter for startups. First, Eudamed module rollout has been staged over time, and manufacturers should check the current operational status of each module against the latest Commission updates before designing a process that assumes full availability. Second, Eudamed does not replace national reporting routes in every case — until a specific module is fully mandatory, parallel national submissions may still be required. MDCG 2025-10 (December 2025) is the current operational guidance that reflects the state of play manufacturers should plan against. ## Country-specific complaint channels Even with Eudamed in the centre, national complaint channels are not disappearing. Competent authorities in each Member State maintain their own incident-reporting systems for healthcare professionals, patients, and users who want to report directly to the national regulator rather than through the manufacturer. Manufacturers learn about those complaints when the competent authority forwards them, queries them, or references them in a routine post-market exchange. A multi-market PMS plan must therefore describe two parallel intake flows. The first is the manufacturer's own intake — the channel the user, the distributor, and the healthcare professional use to contact the manufacturer directly. The second is the authority-mediated intake — the channel where a competent authority contacts the manufacturer about a complaint that reached them first. The two flows produce the same type of data but on different timelines and with different metadata. A complaint that reaches the manufacturer first allows the manufacturer to assess it, decide on vigilance reporting under Article 87 if thresholds are met, and respond. A complaint that reaches the authority first arrives at the manufacturer already framed by the authority's interpretation, often with a deadline for response. Both flows must converge in the same PMS database, be analysed together, and feed the same PSUR or PMS Report under Article 85 or Article 86. Startups often underestimate how much of their PMS load will come through authority-mediated channels once they are active in five or six Member States. The plan that prepared only for direct complaints is the plan that gets behind. ## Coordinated field safety corrective actions Article 89 of the MDR governs field safety corrective actions. When a manufacturer determines that an FSCA is required — a recall, a field modification, a safety notice, or any other action to reduce a risk of death or serious deterioration in health — the action must be reported through the Article 92 electronic system. For a device sold in multiple Member States, an FSCA is almost never a one-country action. Coordination requirements flow from Article 89(8), which addresses field safety notices. The manufacturer issues a field safety notice to users and, in general, to the competent authorities of the affected Member States. The notice must be consistent across countries — the same facts, the same corrective action, the same timeline — while respecting national language requirements. An FSCA that tells Austrian users one thing and Italian users a slightly different thing because the translations drifted is an FSCA that has already failed. The coordination discipline has three elements. First, one authoritative master version of the field safety notice, drafted and approved in one language, before any translation begins. Second, a controlled translation workflow that locks the master version and produces national-language versions as derivatives rather than as independent rewrites. Third, a synchronised dispatch so that all affected Member States receive the notice within a tight window, not over a rolling period where early countries know and late countries do not. MDCG 2025-10 addresses the operational side of how competent authorities expect manufacturers to communicate in cross-border situations. Reading it before the first multi-market FSCA is cheaper than learning the expectations under the pressure of an active action. ## Common mistakes startups make with multi-market PMS **Treating the home market as the default and other markets as exceptions.** This produces a PMS plan that works for one country and creaks under load for every other. The plan should be country-neutral at the process layer and country-specific only where the Regulation or national rules require it. **Assuming a distributor will handle PMS locally.** Distributors are not the manufacturer. Article 83 places the PMS obligation on the manufacturer. Distributors can be contractual partners in data collection, but the system and the accountability stay with the manufacturer. **Running separate spreadsheets per country.** Trend analysis requires pooled data. Separate files per country produce separate analyses per country, which is not what Annex III asks for. **Ignoring language timelines in vigilance deadlines.** The clock for a serious-incident report under Article 87 does not pause for translation. If the plan assumes translation happens in the same business day the complaint arrives, the plan needs a translation capability sized accordingly. **Designing around Eudamed as if every module were fully live.** Build the process against the current operational state of Eudamed and keep the plan updated as modules become mandatory. A process built against an assumed future state is a process that fails today. ## The Subtract to Ship angle The [Subtract to Ship framework for MDR](/blog/subtract-to-ship-framework-mdr) applied to multi-market PMS produces a simple design rule: one PMS system, one plan, one analysis pipeline, one report — with country-specific layers only where the Regulation or national law demands them. Everything else is duplication. The test is the same one the framework applies everywhere. For every country-specific element in the PMS documentation, name the specific article, annex, MDCG 2025-10 section, or national legal requirement that forces the distinction. If the trace exists, keep the country-specific element. If the trace does not exist, merge it into the single shared process. Most startups that run the test discover that 70 per cent of their per-country variation is habit, not obligation. The 30 per cent that survives the test is the real coordination surface — and the effort that used to be spread thin across 100 per cent of a duplicated system can now be concentrated on the 30 per cent that actually matters. The shared core is the Article 83 system, the Article 84 plan against Annex III, the Article 85 PMS Report or Article 86 PSUR, and the Eudamed submission pipeline under Article 92. The country-specific layers are language management for user-facing documents, national complaint-channel intake, national-language field safety notices under Article 89, and any residual national reporting still required until Eudamed modules reach full mandatory status. That is the whole map. ## Reality Check — Where do you stand? 1. List every EU Member State where your device is currently placed on the market. Does your PMS plan name each one explicitly and describe how data flows from it into the central analysis? 2. If a complaint arrived today in the official language of a country where you have no in-house speaker, how many hours would it take to log, translate, and assess against your vigilance thresholds? 3. Does your PMS database pool complaints from every market into one trend analysis, or do you have per-country silos that are analysed separately? 4. Is your Eudamed registration current for every module that is operationally live, and do you have a defined person responsible for submitting vigilance reports and PSURs through the Article 92 electronic system? 5. For Class III or implantable devices, is your PSUR submission route to the notified body via Eudamed actually tested, or is it theoretical? 6. Do you have a locked master template for field safety notices under Article 89, with a controlled translation workflow ready to produce national-language versions on demand? 7. Have you mapped, country by country, which competent authorities still require parallel national submissions alongside Eudamed, and on what timelines? 8. Does your distributor agreement, for each market, name the PMS data the distributor must forward to you and the maximum delay allowed? 9. Have you read MDCG 2025-10 specifically for the sections on cross-border PMS coordination and multi-Member-State vigilance? 10. For every country-specific element in your PMS documentation, can you name the article, annex, or national rule that requires it? ## Frequently Asked Questions **Do I need a separate PMS plan for each EU Member State where I sell?** No. MDR Article 84 requires a PMS plan as part of the technical documentation, and one plan covers the device. The plan must describe how data from every Member State where the device is placed on the market is collected, analysed, and reported. A separate plan per country is not what the Regulation asks for and creates coordination problems rather than solving them. **Is Eudamed the only channel for vigilance reporting in a multi-market situation?** Eudamed is the central electronic system under MDR Article 92 for vigilance reports, PSURs for Class III and implantable devices, and field safety corrective actions. However, module availability has been staged, and until specific modules are fully mandatory, parallel national submissions may still be required in some Member States. Check the current operational status against the latest Commission communications and MDCG 2025-10 before designing the process. **Who is responsible for PMS when a distributor sells the device locally?** The manufacturer. MDR Article 83 places the PMS obligation on the manufacturer regardless of distribution arrangements. Distributors can be contractually required to forward complaints and field data to the manufacturer on defined timelines, but the PMS system, the plan, and the accountability remain with the manufacturer. **Do field safety notices need to be issued in every national language?** Field safety notices under Article 89(8) are directed at users and are generally expected in languages the users understand in each affected Member State. A manufacturer running a cross-border FSCA needs a controlled translation workflow from a single master version to national-language derivatives, dispatched in a synchronised way so that all affected countries receive the notice consistently. **Does a Class I device sold in multiple Member States need a different PMS approach than a Class I device sold in one market?** The class-specific requirements are the same — the Article 85 PMS Report still applies. The multi-market layer adds coordination obligations around language, national complaint channels, and cross-border FSCA handling. The plan grows in coordination complexity even though the class-specific content requirements do not change. **What does MDCG 2025-10 say about multi-market PMS specifically?** MDCG 2025-10 (December 2025) is the current operational guidance on PMS for medical devices and in vitro diagnostic medical devices. It describes how the PMS system should work in practice, including how PMS interacts with vigilance and how authorities expect manufacturers to communicate in cross-border situations. It is the document notified bodies use when assessing whether a multi-market PMS system actually runs and is the single highest-leverage document to read before a cross-border audit. ## Related reading - [What is post-market surveillance under MDR?](/blog/what-is-post-market-surveillance-mdr) — the pillar post on the PMS framework this article extends. - [MDR Articles 83 to 86 — the PMS framework explained](/blog/mdr-articles-83-86-pms-framework) — the article-by-article walkthrough of the core PMS obligations. - [The PMS plan under MDR Annex III](/blog/pms-plan-mdr-annex-iii) — the plan content specification that a multi-market plan must satisfy. - [PSUR for Class IIa, IIb, and III devices under MDR](/blog/psur-class-iia-iib-iii) — the higher-class report mechanics and Eudamed submission. - [Field safety corrective actions under MDR Article 89](/blog/fsca-mdr-article-89) — the FSCA mechanics that multi-market coordination builds on. - [Vigilance reporting timelines under Article 87](/blog/vigilance-reporting-timelines-mdr) — the deadlines that drive multi-market coordination. - [Eudamed modules and the vigilance electronic system](/blog/eudamed-vigilance-electronic-system) — the operational state of Eudamed for multi-market reporting. - [PMS documentation structure for lean teams](/blog/pms-documentation-structure-lean) — the document architecture that keeps multi-market PMS manageable. - [The Subtract to Ship framework for MDR compliance](/blog/subtract-to-ship-framework-mdr) — the methodology applied across every MDR chapter, including multi-market PMS. ## 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 84 (post-market surveillance plan), Article 85 (post-market surveillance report), Article 86 (periodic safety update report), Article 87 (reporting of serious incidents and field safety corrective actions), Article 88 (trend reporting), Article 89 (analysis of serious incidents and field safety corrective actions), Article 92 (electronic system on vigilance and on post-market surveillance), and 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. Medical Device Coordination Group, December 2025. 3. Commission Implementing Regulation (EU) 2021/2078 of 26 November 2021 laying down rules for the application of Regulation (EU) 2017/745 as regards the European Database on Medical Devices (Eudamed). Official Journal L 426, 29.11.2021. 4. EN ISO 13485:2016 + A11:2021 — Medical devices — Quality management systems — Requirements for regulatory purposes. 5. EN ISO 14971:2019 + A11:2021 — Medical devices — Application of risk management to medical devices. --- *This post is part of the Post-Market Surveillance & Vigilance series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. A device that is sold in five Member States lives under one Regulation and five national realities at the same time — the PMS system that treats that fact as a design input rather than a surprise is the one that survives both audit and field.* --- *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).*