Free trial — 30 days 50 UDI-DIs, all modules, no credit card. Check your XML on the playground before production. Terms of use EUDAMED deadline end of November 2026: what must be registered →

MDR · IVDR · Legacy — EUDAMED data

Your Excel,
checked before EUDAMED.

Upload your file: every issue is reported with its row, its column and the rule that found it. Fix, then download an XML validated against the official schema, ready for bulk upload.

30 days · 50 UDI-DIs · every module · no credit card · account opened immediately

XLSXFichier_Transfert_MDR.xlsxStructured data
Basic UDI-DIClassSRNStatus
BASIC-UDI-EXEMPLE-01IIaFR-MF-[…]Complete
BASIC-UDI-EXEMPLE-02IIbDE-MF-[…]Review
BASIC-UDI-EXEMPLE-03IIIIT-MF-[…]Complete

The team completes a readable template; every row remains identifiable during checks.

XLSXFile analysis247 rows analyzed
  • R-004Row 27 · Risk_ClassMissing or unauthorized value
  • R-030Row 89 · Package_DICode_2Status and quantity required
  • WarningRow 112 · Manufacturer_SRNContact details will be ignored

2 blocking errors · Fix before generation

XMLexport_MDR.xmlFile ready to download
<device:MDRBasicUDI>
  <basicudi:riskClass>IIb</basicudi:riskClass>
  <basicudi:identifier>
    <commondevice:DICode>04056…0012</commondevice:DICode>
  </basicudi:identifier>
  <basicudi:MFActorCode>FR-MF-[…]</basicudi:MFActorCode>
</device:MDRBasicUDI>

Check report retained · The XML and findings remain linked to the generation.

EUDAMED modules covered
7MDR, IVDR, Legacy, Procedure Packs, vigilance, updates and Pull Requests.
Generation scenarios
31Creation, linking, updating and extraction according to the selected operation.
Validation rules
56Each one identified, dated and tied to its source.
Entities per XML file
300Cap set by the EUDAMED schema: beyond it, batching is automatic.

Regulatory calendar

End of November 2026: devices already on the market must be registered.

The UDI/Devices module has been mandatory since 28 May 2026. For devices placed on the market before that date and still marketed, MDR, IVDR and legacy alike, the grace period ends at the end of November 2026.

Who is affected, with sources

How it works

Three steps. The check in the middle.

  1. 01

    Fill in the template

    One Excel template per EUDAMED operation, with the expected value lists and a dictionary that explains every column.

  2. 02

    Fix what blocks

    The file is analysed before anything is generated. Every issue gives the row, the column, the reason and the rule identifier.

  3. 03

    Download the XML

    The XML is validated against the official XSD. Beyond 300 entities per message, it is split into batches automatically.

What is checked

56 validation rules, each identified, dated and sourced.

An issue with no rule to cite is not a check. Every issue in your report carries the identifier of the rule that detected it, and that identifier is never reassigned: an archived report stays readable years later.

See all 56 checks, named
  • Required fields and formats

    Checks are applied only when the data or condition requires them.

    R-001 · R-007
  • Formats and allowed values

    Each column is checked against its format and expected value list.

    R-003 · R-018
  • Value dictionaries

    Languages, classes, countries, warnings, storage conditions and other lists.

    R-004
  • Conditional rules

    A field that is required “depending on the case” is checked in its real context, row by row.

    R-008 · R-015
  • Cross-field consistency

    Packages, SRNs, manufacturers, markets and dependent fields.

    R-026 · R-030 · R-031
  • Schema structure and version

    The generated XML is validated against the selected XSD schema, whose version is displayed.

    R-017 · R-023 · R-024
  • Duplicate identifiers

    The same UDI-DI repeated in the file is flagged as a warning; a repeated Basic UDI-DI, on the other hand, is normal.

    R-019
  • Exportable Excel report

    A compliance record that can be shared with quality and regulatory teams.

  • 36
    EUDAMED behaviour A rejection observed on the registry becomes a rule, reused by every later deployment.
  • 11
    XSD schema What the official schema requires: fields, types, enumerations, dependencies.
  • 6
    File Guardrails on the file itself: readability, duplicates, broken formulas.
  • 3
    Regulation What MDR, IVDR and MDCG guidance require beyond the schema.

33 of these 56 rules do not come from the initial core: they were born from a conformity audit against the official schema, from internal qualification, or from a client deployment. The library grows with every difficult case.

Both ways

To EUDAMED, and back.

Excel → XML

From Excel to XML, with checks at the right stage.

Register, link, update, report: one template and one XML per operation, across 31 scenarios.

Modules

XML → Excel

EUDAMED answers in XML. We hand it back to you in Excel.

Your devices are already registered in EUDAMED? Drop the registry's response here: it becomes an Excel template again, ready to be corrected and resubmitted.

  1. Request your data Generate a request with the “Pull Request” module and submit it to EUDAMED.
  2. Collect the response EUDAMED returns an XML file containing your devices.
  3. Drop it here We turn it back into an Excel template: one row per device, with the usual lists and checks.
  4. Correct and resubmit Change what needs changing, then generate the update from the matching module.

The values come from EUDAMED itself, so non-updatable fields are echoed unchanged — which avoids the “… is not updatable” rejection on update.

Functional coverage

One platform for very different EUDAMED workflows.

One Excel template, a rule set and an XML file per operation.

Supported XSD version3.0.30EUDAMED playground: XSD 3.0.36.1

Classic Medical Devices (MDR Regulation)

Creation and update of UDI-DI / Basic UDI for classic medical devices.

  • Full Import (Creation)Use this for the very first declaration of a device: creates the Basic UDI-DI (parent) AND its first UDI-DI (child) in one operation.
  • Master UDI-DI (Création)À utiliser pour déclarer un Master UDI-DI MDR avec ses propriétés spécifiques, sans passer par une intégration M2M.
  • Import linked to an existing Basic UDIUse this when the Basic UDI-DI (parent) already exists in EUDAMED and you're adding a new variant (new UDI-DI) to that same model — e.g. a new size in the same range.
  • Child Update (UDI-DI)To correct or complete the information of an already-registered UDI-DI (status, packaging, warnings...) without touching the parent Basic UDI-DI.
  • Parent Update (Basic UDI)To correct or complete the information shared by the whole device family (risk class, certificates, original designer...).

Procedure Packs and Systems (MDR)

Management of procedure packs and systems.

  • Full Import (Creation)First declaration of a procedure pack: creates the Basic UDI-DI and its first UDI-DI at once.
  • Import linked to an existing Basic UDIAdds a new UDI-DI (variant) to a procedure pack whose Basic UDI-DI already exists.
  • Child Update (UDI-DI)Corrects the information of an already-registered variant (UDI-DI).
  • Parent Update (Basic UDI)Corrects the information shared by the whole procedure pack range (Basic UDI-DI).

In Vitro Diagnostic Devices (IVDR Regulation)

Creation and update of in vitro diagnostic devices.

  • Full Import (Creation)First declaration of an IVD device: creates the Basic UDI-DI and its first UDI-DI at once.
  • Import linked to an existing Basic UDIAdds a new variant (UDI-DI) to an IVD device whose Basic UDI-DI already exists.
  • Child Update (UDI-DI)Corrects the information of an already-registered IVD variant (UDI-DI).
  • Parent Update (Basic UDI)Corrects the information shared by the whole IVD range (risk class, certificates...).

Legacy Devices (MDD / AIMDD / IVDD Directives)

Devices under the former MDD / AIMDD / IVDD directives.

  • Legacy MDD/AIMDD ImportFirst declaration of a &laquo;legacy&raquo; medical device under the MDD or AIMDD directive.
  • MDD/AIMDD Child UpdateCorrects the information of an already-registered Legacy MDD/AIMDD UDI-DI.
  • MDD/AIMDD Parent UpdateCorrects the information shared by the Legacy MDD/AIMDD range (Basic UDI-DI).
  • Legacy IVDD ImportFirst declaration of a &laquo;legacy&raquo; IVD device under the IVDD directive.
  • IVDD Child UpdateCorrects the information of an already-registered Legacy IVDD UDI-DI.
  • IVDD Parent UpdateCorrects the information shared by the Legacy IVDD range (Basic UDI-DI).

Specific Updates (PUT Operations)

Adding market information, packaging or original designer details.

  • Packaging HierarchyDeclares or updates the packaging levels of a UDI-DI (box, carton, pallet...).
  • Original Designer (Product Designer)Provides the device's original designer when it differs from the declaring manufacturer (with or without an SRN code).
  • Market InformationDeclares the countries of commercialisation, the first placed-on-the-market date and, if applicable, the withdrawal date.

Vigilance and Post-Market Surveillance Reports (VIG / MSU Module)

Reporting incidents, corrective actions, safety notices and periodic reports to the authorities.

  • MIR (Manufacturer Incident Report)Reports a single incident (serious or potentially serious) involving a device already on the market. The first link in the vigilance chain: file it without delay after becoming aware of the incident.
  • FSCA (Field Safety Corrective Action)Documents a corrective action decided by the manufacturer on devices already distributed (recall, update, instruction). Usually follows one or more MIRs, or the manufacturer's own internal analysis.
  • FSN (Field Safety Notice)The notice actually communicated to users/customers to inform them of an FSCA. Reference the notice PDF here (name + path in the attached archive) per affected country.
  • PSUR (Periodic Safety Update Report)Periodic safety and performance summary for a device (or family), independent of any specific incident. Frequency to be determined by your device's risk class.
  • MTR (Trend Report)Flags a statistically significant increase in the frequency/severity of non-serious incidents or expected side-effects, detected by the manufacturer through post-market surveillance.

Query Templates (Pull Requests - GET Operation)

Generating download requests (certificates, actor profiles, device data).

  • Pull Request DEVICEQueries the devices database (UDI-DI / Basic UDI-DI) using criteria such as the manufacturer's SRN, country, risk class or status.
  • Pull Request ACTORQueries economic actor profiles (manufacturers, authorised representatives, importers) by actor code, country or actor type.
  • Pull Request SSCPQueries Summary of Safety and Clinical Performance documents by Basic UDI, certificate number or revision number.
  • Pull Request CERTIFICATEQueries certificates issued by notified bodies (by type, status, issue or expiry period).

Commitments

What we stand by, and what we do not promise.

Checks before generation
Every Excel file is analyzed before generation: required fields, formats and the main consistency rules are checked. The XML file is only generated once blocking errors are corrected.
Actionable results
Every identified issue shows the row, the field concerned and the reason for the block or warning, making it easier to correct the data.
Templates and checks kept up to date
Templates and checks are tracked against the supported EUDAMED changes. When a structure, an XSD version or a validation rule evolves, the relevant tools are adapted to keep prepared and generated files consistent.
Never patient data
Fictitious, anonymised or non-confidential data. Never patient or health data.
XSD validation ≠ EUDAMED acceptance
XSD validation attests structural conformity to the schema — never acceptance by EUDAMED nor regulatory compliance. A file that passes these checks is not an accepted file: EUDAMED alone decides what it accepts, and we do not submit anything on your behalf. These rules rule out known, documented causes of rejection — not every possible cause. We will never claim otherwise.
An independent service
Let's EUDAMED is affiliated neither with the European Commission nor with the official EUDAMED portal. You prepare and check your files here, and stay in control of every submission.

30-day free trial

Try it on your own data, today.

30 days · 50 UDI-DIs · every module · no credit card · account opened immediately