FAQ item index

Search every question across sub-FAQs

Find the exact question, open the source answer card, and copy a direct link to the anchored sub-FAQ response.

Indexed coverage
40of40items
Across 12 modules • Updated Jul 31, 2026
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 31, 2026
Custom-made medical devices under the EU MDR

What counts as a custom-made device under the EU MDR?

The definition turns on patient-specific design and prescription control. The device must be made in accordance with a written prescription from a person authorised by national law, the prescription must give specific design characteristics under that person's responsibility, and the device must be intended solely for one particular patient to meet that patient's individual conditions and needs.

Annex XIII uses broader statement wording: it asks the manufacturer to identify the particular patient or user by name, acronym, or numerical code. That statement field does not remove the patient-specific test in Article 2(3), so a manufacturer should not treat ordinary user customization as enough for custom-made status.

The exclusion matters: a mass-produced device that is only adapted to a professional user's requirements is not a custom-made device. A device mass-produced by industrial manufacturing processes under written prescriptions is also outside the custom-made definition.

  • Keep the prescription and evidence that the prescriber was authorised under national law.
  • Identify the patient or user by name, acronym, or numerical code in the Annex XIII statement.
  • Record why the device is not a mass-produced adaptable device or an industrially mass-produced prescription device.

What evidence is needed for custom-made medical devices under the EU MDR?

Keep the written prescription, authorised prescriber details, patient or user identifier, device identification data, Annex XIII statement, design and manufacturing documentation, GSPR conformity rationale, manufacturing controls, PMS or PSUR records where applicable, vigilance reports, and corrective-action records.

Are mass-produced adaptable devices custom-made devices under the EU MDR?

No. The MDR definition excludes mass-produced devices adapted to a professional user's requirements and devices mass-produced by industrial processes in accordance with authorised written prescriptions.

Citations
Custom-made medical devices under the EU MDR

What statement and documentation must the manufacturer keep?

Before placing a custom-made device on the market, the manufacturer must follow Annex XIII and draw up the required statement. Article 21 also requires the device to be accompanied by that statement, made available to the identified patient or user.

Annex XIII requires documentation that lets competent authorities understand the design, manufacture, and performance of the device, including expected performance, so they can assess conformity. The manufacturer must keep the statement for at least 10 years after placing the device on the market, or at least 15 years for implantable devices.

  • Retain manufacturer and manufacturing-site details, authorised representative details where applicable, and device identification data.
  • Include the prescription-specific characteristics, the authorised prescriber and health institution where applicable, and the identified patient or user.
  • State conformity with Annex I general safety and performance requirements, and explain any requirements not fully met.
Citations
Custom-made medical devices under the EU MDR

How is conformity assessment different?

Custom-made devices do not follow the standard class I, IIa, IIb, or III conformity assessment routes used for non-custom-made devices. Article 52(8) points custom-made-device manufacturers to Annex XIII and the Annex XIII statement before placing the device on the market.

There is an added rule for class III custom-made implantable devices: in addition to Annex XIII, the manufacturer must undergo a conformity assessment under Chapter I of Annex IX or may choose Part A of Annex XI.

  • Do not use the custom-made route for ordinary configurable or adaptable catalogue devices.
  • Confirm whether the device is class III and implantable before deciding whether notified-body conformity assessment is required.
  • Keep the route decision with the prescription, classification rationale, Annex XIII statement, and manufacturing documentation.
Citations
Custom-made medical devices under the EU MDR

What PMS and vigilance evidence should be retained?

Annex XIII requires the manufacturer to review and document post-production experience, including PMCF where applicable, and to apply necessary corrective action. Serious incidents and field safety corrective actions must be reported under Article 87 when the manufacturer learns of them.

For class IIa, IIb, and III custom-made devices, Article 86 and MDCG 2022-21 treat the PSUR as part of the Annex XIII documentation. MDCG 2022-21 also states that custom-made-device PSURs may cover device groups or families if the manufacturer justifies the grouping.

  • Retain complaint, incident, field safety corrective action, PMCF, corrective-action, and benefit-risk review records.
  • For class IIa, IIb, and III custom-made devices, keep the PSUR with the Annex XIII documentation and justify any grouped PSUR family.
  • Link PMS conclusions back to the prescription characteristics, design rationale, risk management file, and manufacturing controls.
Citations
EU MDR significant changes FAQ: legacy-device transition and notified-body review

Which MDR changes need significant-change screening?

For an MDR legacy device, MDCG 2020-3 Rev.1 frames the test around two questions: does the change concern design or intended purpose, and if so is it significant under Article 120(3c), point (b). A significant design or intended-purpose change prevents continued placing on the market under the AIMDD/MDD transition route for that changed device; the manufacturer would need to place the changed device under the MDR route instead.

This screening does not extend the transition period. Eligible class III and certain class IIb implantable legacy devices can use Article 120 only until 31 December 2027, while other covered class IIb, class IIa, and relevant class I sterile or measuring devices can use it only until 31 December 2028, and only while every applicable transition condition remains satisfied.

Screen intended-purpose changes, design or performance specification changes, software changes, substance and material changes, and sterilisation or sterile-packaging changes. Administrative changes, manufacturing-site moves, supplier changes that keep the same specification, and some QMS or process changes may be outside design or intended purpose, but they still need documentation and any agreed notified-body notification.

  • Intended purpose: except for changes related to corrective actions assessed and accepted by the competent authority of the Member State in which the manufacturer or its authorised representative has its registered place of business, extensions, new indications, new patient or user populations, and new clinical applications are significant; limitations of the existing intended purpose can be non-significant when aligned with the original certification.
  • Design and performance: changes that alter control mechanisms, operating principle, source of energy, alarm systems, safety, performance, usability, or risk-benefit can be significant.
  • Software: major operating-system, architecture, algorithm, closed-loop, medical-feature, data-presentation, or interoperability changes can be significant; bug fixes, security updates, UI appearance changes, and operating-efficiency changes may be non-significant when they do not affect diagnosis, therapy, usability, or risk-benefit.
  • Materials and substances: changes involving long-contact implants, surgically absorbed materials, human or animal origin materials, medicinal substances, or higher biological or toxicological risk can be significant.
  • Sterilisation and packaging: changing terminal sterilisation method, sterile status, sterility assurance, seal integrity, stability, or unvalidated shelf-life can be significant.

Which changes can affect EU MDR transition status or require notified body review?

For a legacy device, intended-purpose extensions, new patient or user populations, new clinical uses, design or performance changes that affect safety or performance, major software changes, higher-risk material or substance changes, and sterilisation or sterile-packaging changes can be significant under MDR Article 120. If the device is covered by an AIMDD/MDD certificate or approved QMS route, follow the agreed notified-body change-notification procedure; in case of doubt, ask the notified body before implementing the change.

Does every QMS, supplier, or manufacturing change end MDR legacy-device transition status?

No. MDCG 2020-3 Rev.1 says administrative changes, manufacturing-site changes, supplier changes within the same specification, and QMS changes generally do not concern design or intended purpose when the certificate conditions remain maintained. They still need evidence, updated documentation, and any notification required by the agreed notified-body procedure.

Citations
EU MDR significant changes FAQ: legacy-device transition and notified-body review

What is the notified-body and certificate impact?

MDCG 2020-3 Rev.1 says new AIMDD/MDD certificates are not issued under the transition route. For non-significant changes, the certificate should not be amended, but the notified body may provide written confirmation that the proposed change is not a significant design or intended-purpose change and that the related certificate remains valid if the Article 120 conditions are met.

Regulation (EU) 2023/607 also ties the transition route to continued compliance with AIMDD/MDD, absence of significant design or intended-purpose changes, no unacceptable risk, a QMS under MDR Article 10(9), formal MDR conformity-assessment application, written agreement with a notified body, and transfer or continuation of appropriate surveillance as applicable.

  • Keep the notified-body change submission or rationale, the notified-body written confirmation or decision, and any numbered confirmation letters with the certificate record.
  • For approved MDR devices, Annex IX requires notifying the issuing notified body when planned changes to the approved device could affect safety, performance, or conditions of use.
  • Do not treat written confirmation for a non-significant legacy-device change as a supplemented AIMDD/MDD certificate.
Citations
EU MDR significant changes FAQ: legacy-device transition and notified-body review

What evidence should be retained?

Retain enough evidence for a competent authority, notified body, or decision owner to see the exact change, the pre-change certified state, the Article 120 or MDR provision applied, and why the conclusion follows. MDR Article 10 also requires manufacturers to keep technical documentation up to date and to retain technical documentation, declarations of conformity, and relevant certificates for the required retention period.

For clinical and technical impact, update the technical documentation, risk management file, clinical evaluation or PMCF rationale, verification and validation evidence, usability evidence, supplier/material specifications, sterilisation validation, labels and IFU, PMS or vigilance inputs, and QMS change-control records as applicable.

  • Change description: product, model, Basic UDI-DI where relevant, current certificate or declaration route, affected markets, and release version.
  • Significance assessment: intended purpose, design/performance, software, material/substance, sterilisation, clinical evidence, and risk-benefit checks against MDCG 2020-3 Rev.1.
  • Approval trail: regulatory owner, quality owner, notified-body submission or rationale, written confirmation or decision, release gate, and trigger for reassessment.
  • Documentation updates: technical documentation, QMS change record, clinical evaluation or PMCF inputs, PMS/vigilance links, supplier evidence, validation reports, labelling, and authority or notified-body correspondence.
Citations
EU MDR SSCP: Devices and Requirements

Which devices need an SSCP?

First check whether the device is implantable. Article 2(5) covers a device intended to be introduced completely into the body, or to replace an epithelial surface or the surface of the eye, by clinical intervention and remain after the procedure. It also covers a device introduced partially by clinical intervention that is intended to remain for at least 30 days. Implantable devices can be class IIa, IIb, or III, and all three groups need an SSCP.

If the device is not implantable, check whether it is class III. The manufacturer classifies the device from its intended purpose and the rules in Annex VIII. When several rules or sub-rules apply, the one producing the highest class controls. The technical documentation must record the selected rule and the reason it applies.

Class III routes include certain devices used in direct contact with the heart, central circulatory system, or central nervous system; active implants and devices that control or monitor them; breast implants and surgical meshes; total or partial joint replacements; spinal disc replacements and implants that contact the spinal column; diagnostic or therapeutic decision software whose output could lead to death or irreversible deterioration; devices that incorporate a medicinal substance with an ancillary action; certain tissue-derived, nanomaterial, and systemically absorbed substance-based devices; and active therapeutic devices such as closed-loop systems or automated external defibrillators. Annex VIII contains the complete rules.

Examples in MDCG classification guidance include prosthetic heart valves, vascular stents, cochlear implants and their accessories, breast implants, surgical meshes, total or partial joint replacements, software used to make treatment decisions for acute stroke, antibiotic bone cement, automated external defibrillators, and automated closed-loop insulin-delivery systems. Classification still depends on the intended purpose and applicable rule for the specific device.

Under Rule 8, some ancillary joint or spinal components, including certain screws, wedges, plates, and instruments, remain outside class III. The component still needs an SSCP if it meets the definition of an implantable device.

The SSCP gives the public an updated summary of the device's clinical data, safety, and clinical performance. The instructions for use, implant card, and advice from a healthcare professional remain separate, and the SSCP must be free of promotional claims.

  • Manufacturer: prepare the SSCP from the current technical documentation, keep it accurate, manage translations, and confirm that the required versions are available before placing the device on a Member State market. For updates containing new or changed information other than strictly editorial modifications, MDCG guidance says the manufacturer should submit the updated SSCP to the notified body with the required PSUR.
  • Notified body: independently assess the device for conformity with the MDR, validate the SSCP against the required content and current technical documentation, and complete the upload step assigned to it under the applicable EUDAMED transition process.
  • EUDAMED: make the SSCP public and link it to the Basic UDI-DI, the identifier used to connect the SSCP to the relevant device group. As of 23 July 2026, the first four EUDAMED modules have been mandatory since 28 May 2026. MDCG 2026-4 sets temporary SSCP upload arrangements while new functionality is introduced, so teams should record who must upload each version and whether the published revision has been validated.

Which devices need an SSCP under the EU MDR?

An implantable or class III device needs an SSCP unless it is custom-made or investigational. First, determine whether the device meets the EU MDR definition of an implantable device; an implantable class IIa or IIb device still needs an SSCP. For a non-implantable device, apply the Annex VIII classification rules and prepare an SSCP if the rules place it in class III.

What does the EU MDR mean by an implantable device?

An implantable device is intended to be introduced completely into the body, or to replace an epithelial surface or the surface of the eye, by clinical intervention and remain after the procedure. A device intended to be introduced partially by clinical intervention and remain for at least 30 days also counts as implantable. Implantable devices in class IIa, IIb, or III fall within the SSCP requirement unless they are custom-made or investigational.

What counts as a class III device for the SSCP requirement?

Class III is the highest EU MDR risk class. Apply every relevant Annex VIII rule to the device's intended purpose and characteristics; the rule producing the highest class controls. Examples include prosthetic heart valves, vascular stents, cochlear implants, breast implants, surgical meshes, total or partial joint replacements, specified spinal implants, software used for acute-stroke treatment decisions, antibiotic bone cement, automated external defibrillators, and automated closed-loop insulin-delivery systems. Other class III routes cover certain tissue-derived, nanomaterial, and systemically absorbed substance-based devices. Classification depends on the intended purpose and exact Annex VIII rule, which the technical documentation must identify.

What should an EU MDR SSCP include?

Cover eleven content groups: device and manufacturer identity; Basic UDI-DI; the manufacturer's Single Registration Number, if issued; intended purpose and patient population; device description and relevant variants; risks, undesirable effects, warnings, and precautions; clinical evaluation and PMCF results; diagnostic or therapeutic alternatives; intended-user profile and training; applied harmonised standards and common specifications; and revision history. The detailed checklist below shows what belongs in each group.

Who prepares, validates, and publishes the SSCP?

The manufacturer prepares and maintains the SSCP. A notified body validates it against the MDR requirements and current technical documentation. As of 23 July 2026, MDCG 2026-4 assigns temporary upload steps while new EUDAMED functionality is introduced. For a new certificate registered from 28 May 2026, the notified body uploads the master SSCP with the certificate. For devices placed on the market before that mandatory-use date, manufacturers should upload the applicable SSCPs as soon as the new functionality permits and no later than 27 February 2027. The guidance describes a later move to manufacturer uploads of the master SSCP and translations when the new functionality is available.

How should a manufacturer control SSCP quality and updates?

The manufacturer is responsible for the SSCP and chooses which internal team owns the work. Source the content from current technical documentation, assign the SSCP a unique reference number, and keep it objective, readable, and free of promotional claims. Review it when the post-market clinical follow-up (PMCF) evaluation report and periodic safety update report (PSUR) are updated. Revise any section that is incorrect, incomplete, or out of step with the technical documentation. Record the revision, validation status, and validated language; control translation accuracy through the quality management system; and, for updates containing new or changed information other than strictly editorial modifications, MDCG guidance says the manufacturer should submit the updated SSCP to the notified body with the required PSUR.

Where should users and patients find the SSCP?

Article 32 requires the manufacturer to state on the label or in the instructions for use where the SSCP is available. The public version is linked in EUDAMED through the Basic UDI-DI. The SSCP does not replace the label, instructions for use, implant card, or advice from a healthcare professional.

When does an SSCP need to be updated?

Review the SSCP whenever the PMCF evaluation report and PSUR are updated and whenever new information makes a public statement incorrect or incomplete. Common triggers include changed indications or contraindications, new residual risks or undesirable effects, revised clinical-evaluation conclusions, important vigilance or trend findings, corrective actions, and changes to the device or intended purpose that affect the summary. Record each revision and its validation status. For an update containing new or changed information other than strictly editorial modifications, MDCG guidance says the manufacturer should submit the updated SSCP to the notified body with the required PSUR.

How should SSCP translations be controlled?

Provide the SSCP in the languages required by each Member State where the device is made available. Keep the master and translated versions under document control, verify translation accuracy through the quality management system, identify the validated language, and ensure each public version matches the current validated content. Follow the applicable EUDAMED transition process for uploading the master SSCP and translations.

When does an SSCP need a separate patient-facing part?

The SSCP always needs information for intended users or healthcare professionals. MDCG 2019-9 Rev.1 recommends a separate patient-facing part when the information is relevant to patients, especially for implantable devices supplied with implant cards and class III devices used directly by patients. Eligible Annex XVI devices should also be treated as relevant for patient information. Write the patient part in plain language, explain medical terms, and keep it separate from the professional section so each audience can find the appropriate level of detail.

Citations
EU MDR SSCP: Devices and Requirements

How do you decide whether a device needs an SSCP?

Work through the trigger in order. Start with the Article 2(5) implantable-device definition because an implantable class IIa or IIb device still needs an SSCP. If the device is not implantable, apply every relevant Annex VIII rule and use the highest resulting class. Then check whether the device is custom-made or investigational, because Article 32 excludes both.

Classify from the intended purpose and device characteristics, then record the duration of use, invasiveness, anatomical site, active or software function, materials, and every rule considered. The worked cases show the reasoning pattern. The manufacturer still needs a device-specific classification rationale.

  • Case 1 - class IIa diagnostic ultrasound system: it is not implantable and Annex VIII does not place it in class III. Result: Article 32 does not require an SSCP.
  • Case 2 - class IIb dental implant: it meets the Article 2(5) implantable-device definition. Result: it needs an SSCP even though it is not class III.
  • Case 3 - class III automated external defibrillator: it is not implanted, but the applicable Annex VIII rule places it in class III. Result: it needs an SSCP.
  • Case 4 - custom-made implantable device: it meets the implantable definition, but Article 32 expressly excludes custom-made devices. Result: Article 32 does not require an SSCP.
  • Case 5 - investigational class III device: its class would ordinarily trigger an SSCP, but Article 32 excludes investigational devices. Result: no Article 32 SSCP is required while that exclusion applies; the clinical-investigation requirements remain separate.
Citations
EU MDR SSCP: Devices and Requirements

What must an SSCP contain?

Use controlled technical documentation for every SSCP statement. MDCG 2019-9 Rev.1 organises the public summary around the content groups below. Keep the wording objective and understandable to the intended user, and leave out promotional claims.

  • Device and manufacturer identity: device and trade names, manufacturer name and address, Single Registration Number if issued, Basic UDI-DI, medical-device nomenclature description, risk class, year of first CE marking, authorised representative when applicable, and notified-body name and identification number.
  • Intended purpose: indications, contraindications, target populations, intended users, and any required training.
  • Device description: operating principles, key components and materials, accessories intended to be used with the device, and relevant previous generations or variants.
  • Risks and safety information: residual risks, undesirable effects, warnings, precautions, and other relevant safety information that remains after risk controls.
  • Clinical evidence: the clinical-evaluation summary, the type and amount of supporting data, both favourable and unfavourable findings, and relevant PMCF results.
  • Therapeutic or diagnostic alternatives: available alternatives and the circumstances relevant to choosing among them.
  • Standards and specifications: applied harmonised standards and common specifications.
  • Revision control: SSCP reference number, issue date, revision description, validated language, notified-body validation status, and the versions and translations made public.
Citations
EU MDR SSCP: Devices and Requirements

What products fall into each EU MDR class?

The MDR does not assign a permanent class to a product name. The manufacturer applies Annex VIII to the device's intended purpose, duration of use, invasiveness, anatomy, materials, software impact, and other characteristics. The examples below show common classifications from MDCG 2021-24 Rev.1; a specific device may classify differently when its intended purpose or characteristics differ.

For this SSCP question, class I devices are outside Article 32. Class IIa and IIb devices need an SSCP only when they meet the definition of an implantable device. Every class III device needs an SSCP, whether implantable or not, unless it is custom-made or investigational.

  • Class I: examples include manual wheelchairs, walking aids, stethoscopes, corrective spectacle frames, simple wound dressings, examination lamps, and software that falls outside the higher Rule 11 categories. These devices do not need an SSCP under Article 32.
  • Class IIa: examples include short-term corrective contact lenses, needles and syringes, infusion tubing, diagnostic ultrasound systems, electrocardiographs, feeding pumps, and X-ray image detectors. Rule 8 also places certain devices intended to be placed in the teeth in class IIa, with MDCG examples including bridges, crowns, dental filling materials, and dental pins. A class IIa device needs an SSCP only if the specific device meets the Article 2(5) implantable-device definition.
  • Class IIb: examples include blood bags, haemodialysers, long-term urinary catheters, apnoea monitors, diagnostic X-ray and computed-tomography systems, and contact-lens disinfectants. Rule 8 examples of class IIb implantable devices include dental implants and abutments, artificial ligaments, shunts, peripheral stents and valves, plates, intra-ocular lenses, non-absorbable sutures, penile implants, and pedicle screws. These implantable class IIb devices need an SSCP.
  • Class III: examples include prosthetic heart valves, central vascular stents and long-term catheters, cochlear implants, implantable pacemakers and defibrillators, breast implants, surgical meshes, total or partial joint replacements, specified spinal implants, software used for acute-stroke treatment decisions, antibiotic bone cement, automated external defibrillators, and automated closed-loop insulin-delivery systems. Every class III device needs an SSCP unless it is custom-made or investigational.

Do all class IIa and IIb devices need an SSCP?

No. A class IIa or IIb device needs an SSCP only when it meets the Article 2(5) definition of an implantable device. For example, a diagnostic ultrasound system may be class IIa and a computed-tomography system may be class IIb, but neither needs an SSCP merely because of that class. Dental implants, intra-ocular lenses, peripheral stents, plates, and other implantable class IIb devices do need one.

Are all products with the same name in the same MDR class?

Classification depends on the device's intended purpose and characteristics. Duration of use, invasiveness, anatomical site, biological effect, absorption, medicinal substances, nanomaterials, and the clinical impact of software can change the applicable Annex VIII rule. Use product examples for orientation, then document the exact rule and rationale for the specific device.

Citations
EU MDR SSCP: Devices and Requirements

What evidence should support the SSCP?

Source the SSCP from the device's technical documentation: the controlled evidence set that shows how the device meets the MDR. Keep a traceable record showing the source for each public statement and confirming that it still matches the current technical documentation.

For the clinical section, retain the clinical evaluation plan and report, the evidence used to support conformity, both favourable and unfavourable clinical data, and the post-market clinical follow-up (PMCF) plan and evaluation report. If the clinical evaluation relies on equivalence to another device, retain the equivalence rationale and evidence showing that the manufacturer has sufficient access to the equivalent device's data.

  • Identification and scope: classification rationale, implantable-status rationale, intended purpose, label and instructions-for-use references, Basic UDI-DI, manufacturer Single Registration Number, notified-body name and identification number, and the SSCP reference number.
  • Safety and clinical evidence: risk management file, design verification and validation reports, clinical evaluation report, post-market surveillance plan, PMCF plan and reports, PSUR inputs, vigilance or trend evidence, and instructions-for-use cross-references.
  • Document control: issue dates, change descriptions, validated language, notified-body validation status, translations sent to the notified body, and checks confirming publication in EUDAMED.
Citations
EU MDR SSCP: Devices and Requirements

How was this guide prepared and reviewed?

Sorena AI assembled this page from Regulation (EU) 2017/745, MDCG 2019-9 Rev.1, MDCG 2021-24 Rev.1, MDCG 2026-4, and the European Commission's EUDAMED overview. Each statement about eligibility, classification, content, evidence, publication, and updates was mapped to those sources. Repeated explanations were combined into standalone answers and worked cases.

AI assisted with source comparison, drafting, and organisation. Readers can use the citations to check each conclusion against the controlling regulation and current Commission guidance. No named human regulatory or clinical reviewer is claimed. For a specific device, confirm the intended purpose, classification rationale, notified-body instructions, applicable Member State language requirements, and current EUDAMED process before acting.

Source review current as of 23 July 2026. This revision added the standalone decision test, class-based worked cases, a scannable SSCP content checklist, translation and lifecycle answers, internal reading paths, and the June 2026 EUDAMED transition guidance. The page date reflects those substantive changes.

Citations
Regulation (EU) 2017/745 on medical devices

Binding source. Article 2 provides definitions, Article 32 governs the SSCP, Article 51 and Annex VIII govern classification, Article 86 governs PSURs, and Annex XIV governs clinical evaluation and PMCF.

EUDAMED overview

Commission source used for EUDAMED purpose, module scope, and mandatory-use date.

How should Basic UDI-DI and UDI-DI be assigned under the EU MDR?

How should Basic UDI-DI and UDI-DI be assigned under the EU MDR?

The manufacturer decides the Basic UDI-DI grouping from its technical knowledge and the issuing entity's rules. Group only devices that share the same intended purpose, risk class, and essential design and manufacturing characteristics. The Basic UDI-DI is the main database and documentation key; it appears in the EU declaration of conformity and, where applicable, product certificates, technical documentation, the summary of safety and clinical performance (SSCP), and the periodic safety update report (PSUR). It is not placed on the device label.

Assign a UDI-DI to the device model and a separate UDI-DI to each higher packaging level, excluding shipping containers. The UDI-DI is specific to a manufacturer and device. It combines with the production identifier, or UDI-PI, to form the UDI conveyed by the UDI carrier. A Basic UDI-DI may link to one or more UDI-DIs, but each device UDI-DI links to one Basic UDI-DI in EUDAMED.

  • Document why every device in the Basic UDI-DI group has the same intended purpose, risk class, and essential design and manufacturing characteristics; do not use commercial family names as the grouping test.
  • Use UDI-DIs for the device and higher packaging levels; shipping containers are not higher levels of packaging for this purpose.
  • For devices needing notified-body product certificates, MDCG 2022-7 recommends aligning the Basic UDI-DI grouping with the notified body so certificates and supporting regulatory documents reference the right group.
  • Assign the Basic UDI-DI before applying to the notified body when MDR Article 29(3) applies, and assign or verify the required UDI/device data before placing the device on the market.

How should Basic UDI-DI and UDI-DI be assigned under the EU MDR?

The manufacturer groups devices with the same intended purpose, risk class, and essential design and manufacturing characteristics under one Basic UDI-DI. It then assigns a UDI-DI to each specific device model and each higher packaging level other than shipping containers. The UDI-DI combines with the applicable UDI-PI to form the UDI. Use an EU-designated issuing entity's rules, document the grouping rationale, and keep EUDAMED and regulatory records aligned.

Does the Basic UDI-DI go on the label?

No. The Basic UDI-DI is a database and regulatory-document key, not the identifier shown on the label. The UDI carrier conveys the device or packaging UDI through automatic identification and data capture (AIDC) and human-readable interpretation (HRI), subject to the MDR placement rules and exemptions.

Can one Basic UDI-DI cover several device models?

Yes, if the models have the same intended purpose, risk class, and essential design and manufacturing characteristics. The manufacturer decides the grouping from its technical knowledge and the issuing entity's rules. For product certificates, MDCG 2022-7 recommends alignment with the notified body. A shared brand or commercial product family is not enough by itself.

Citations
MDCG 2022-7 - UDI system Q&A

Non-binding MDCG guidance on manufacturer-led Basic UDI-DI grouping, notified-body alignment, the relationship between Basic UDI-DI and UDI-DI, and packaging identifiers.

Regulation (EU) 2017/745 on medical devices

Current consolidated MDR text for Article 27 UDI duties, Article 29 device registration, Annex IV declaration content, Annex VI definitions, packaging rules, and certificate references; EUR-Lex notes that the consolidated text itself has no legal effect.

How should Basic UDI-DI and UDI-DI be assigned under the EU MDR?

How do UDI carriers, labels, and EUDAMED records fit together?

The UDI carrier is the AIDC and HRI representation of the UDI. As a general rule, it is placed on the label or device itself and on higher packaging levels. Annex VI contains exceptions for space constraints, certain individually packaged class I and IIa single-use devices, retail point-of-sale packaging, direct marking, and systems or procedure packs. The UDI requirement does not replace the rest of the MDR labelling requirements.

Manufacturers must submit UDI/device information in EUDAMED for devices subject to the registration requirements. The UDI/Devices module has been mandatory since 28 May 2026. Before placing a device other than a custom-made device on the market, the manufacturer must enter or verify the applicable Annex VI device information and keep it updated. A UDI-DI record does not prove that the device conforms to the MDR.

  • Keep the label artwork, package hierarchy, and UDI carrier specification traceable to the assigned UDI-DI and UDI-PI.
  • Confirm that EUDAMED data matches the Basic UDI-DI, UDI-DI, packaging hierarchy, manufacturer, EMDN code, and device characteristics used in regulatory records.
  • Do not treat the presence of a UDI-DI in the UDI database as proof of MDR conformity; it is an identifier record, not a conformity decision.
Citations
Regulation (EU) 2017/745 on medical devices

Current consolidated MDR text for Annex VI carrier formats and placement, exemptions, packaging, database maintenance, and the rule that registration is not proof of conformity; EUR-Lex notes that the consolidated text itself has no legal effect.

Page 1 of 3
Previous123Next