- Supports checking whether changed UDI/device information must be reflected in EUDAMED registration data.
"submit in EUDAMED the UDI/Device information"
Review this workflow before releasing a medical device change that may affect design, software, intended purpose, manufacturing, QMS, clinical evidence, PMS, UDI data, classification, or the conformity assessment route.
The output is a documented release decision: what changed, whether the change is significant, what MDR files need updates, whether notified-body involvement is needed, and what evidence is retained.
Structured answer sets in this page tree.
Cited legal and guidance references.
EU MDR change assessment should start from the proposed change, not from a generic compliance checklist. Capture the device and Basic UDI-DI affected, compare the change with the approved intended purpose, design, software, QMS, risk, clinical, PMS, and UDI baseline, then decide whether it is a and whether the device can proceed under the existing conformity position or needs review, certificate action, or a new MDR conformity assessment step.
Open one change record for the device family, model, Basic UDI-DI, certificate or declaration of conformity, software version, manufacturing site, supplier, label, IFU, risk file, clinical evaluation, PMS plan, and technical documentation affected by the proposal.
Compare the proposed change with the baseline that was assessed for conformity. For using MDR transitional provisions, Regulation (EU) 2023/607 keeps the no-significant-change condition focused on design and intended purpose, while MDR PMS, vigilance, and registration obligations still apply.
Treat significance as a documented technical and regulatory judgement. MDCG 2020-3 Rev.1 is guidance for relying on the Article 120 transition; it is not the change-approval procedure for an MDR-certified device. For a legacy device, first ask whether the change concerns design or intended purpose, then apply the relevant intended-purpose, design, software, substance/material, and sterilisation questions. If any applicable branch reaches , do not release the changed device in reliance on that transition.
Do not treat every administrative or supplier change as significant. A manufacturer name, address, authorised-representative, site, supplier, material number, or process-validation change can be outside design or intended purpose when the device specifications and certified conditions remain controlled. The assessment still needs evidence and, where a agreement requires it, notification or prior approval.
After the significance screen, rerun classification for the changed device. Annex VIII classification is governed by intended purpose, combination use, software that drives or influences another device, duration of use, invasiveness, active-device function, and the highest applicable rule when multiple rules apply.
Then confirm whether the current conformity route still fits. Class I devices may generally follow manufacturer responsibility, subject to the limited role for sterile devices, measuring devices, and reusable surgical instruments. Class IIa, IIb, and III devices require notified-body involvement. For an MDR-certified device, follow the applicable Annex IX, X, or XI change provision and the notified-body contract: substantial QMS or device-range changes and changes that could affect an approved device's safety, performance, or conditions of use may require assessment, a certificate supplement, or a new conformity assessment.
Do not close the change assessment until the affected MDR files have been updated or a reason for no update is recorded. Annex II and Annex III technical documentation should stay aligned with the changed device, including design and manufacture information, GSPR evidence, benefit-risk analysis, risk management, verification and validation, PMS plan, and PMS outputs.
Clinical and PMS files need a separate impact check. MDR requires risk management and clinical evaluation to be aligned and regularly updated; PMCF is a continuous process that updates clinical evaluation and feeds risk management when new preventive or corrective measures are needed.
Use Sorena to assemble the change baseline, significant-change rationale, classification impact, notified-body path, and updated MDR evidence pack before approving release.
The release decision should be inspectable without reconstructing the assessment from meetings. Keep the change request, baseline comparison, significance rationale, classification memo, conformity-route decision, correspondence, updated file list, residual assumptions, and final release or escalation approval together.
For , retain the evidence showing why a change is not significant in design or intended purpose, because MDR transition eligibility depends on that condition. For MDR-certified devices, retain the decision path when the change affects an approved QMS, design, type, intended use, claims, or relevant incorporated substance.
"submit in EUDAMED the UDI/Device information"
"third-party intervention is required"
"potential impact of any changes"
"outcome of the assessment should be documented"
"misidentification of the device"
"procedures for management of modifications to the devices covered by the system"
"no significant changes in the design and intended purpose"