Custom UDI integration development
Appfront builds integrations for UDI, the unique identification of medical devices under the MDR and the IVDR. Manufacturers register their devices with UDI data in EUDAMED, the European database, and its UDI module has been mandatory for new devices since 28 May 2026. We connect your own product management to EUDAMED and to your labels, so your UDI data is correct in one place and never entered by hand.
What is a UDI integration?
Under the European regulations for medical devices, the MDR and the IVDR, devices receive a unique identifier, the UDI. It consists of a fixed part for the model or version, the UDI-DI, and a part for production, such as a lot number or serial number. There is also a Basic UDI-DI for the product group. The UDI appears on the label and packaging, and the data is registered in EUDAMED, the European database.
The UDI module of EUDAMED has been mandatory since 28 May 2026: new devices must be registered before they are placed on the market, and a transition period applies to devices already on the market. In practice, product data sits in an ERP or a product information system, and is entered into EUDAMED by hand or uploaded via a file. A change to a product does not always result in a new UDI-DI where one should have been issued.
We build custom solutions because companies differ: how many devices you have, where the product data is kept, which issuing entity you use, and how labels are produced. Which data you must register, and when, follows from the MDR, the IVDR and the European Commission's guidance; if in doubt, check with your regulatory affairs specialist or adviser.
From your product management
UDI data in one place, in your own product management or ERP, instead of in separate lists.
To EUDAMED
Registration and updates in the UDI module, with checks for missing or incorrect data.
On the label
The same UDI on label and packaging, with changes that require a new UDI-DI flagged.
How we build your UDI integration
We start with your devices: how many, where the product data is kept, which issuing entity, how labels are produced, and how registration works today. Often not all the data EUDAMED requires is already in your own system. We map that out, so it is clear what needs to be added and by whom.
Your products, data, issuing entity, labels and systems.
Basic UDI-DI, UDI-DIs and attributes in your product management.
Registration in EUDAMED, and the same UDI on the label.
Alerts when something changes, and ongoing maintenance afterwards.
What a UDI integration actually does
The components below appear in almost every UDI integration. Which ones you need depends on your role.
UDI data
Basic UDI-DI, UDI-DI and attributes.
Allocation
According to your issuing entity.
Registration
In the UDI module of EUDAMED.
Validation
Missing or incorrect data.
Label
The same UDI on label and packaging.
Changes
Alert when a new UDI-DI is needed.
Who we build a UDI integration for
The integration is intended for anyone who assigns, registers or records UDIs.
Manufacturers
Many devices and versions. Registration is the core.
Importers
Devices from outside the EU. Verification matters most.
Distributors
UDIs in the supply chain. Scanning is what you need.
Hospitals
Implants in the patient. Recording is the core.
Technology and integrations
This page is about UDI and EUDAMED. For the technical file, see our page on an MDR technical file with PMS, for in vitro diagnostics our page on an IVDR file system, and for implants our page on an implant register. You can read about our approach on custom software development.
If you also want to assign GTINs for your medical devices from your own systems and record them in MijnGS1, take a look at our GS1 GTIN integration.
Why Appfront for your UDI integration?
A UDI that differs in EUDAMED from what's on the label is a problem at every inspection. That's what we build against: data in one place, registration without manual work, and the same UDI everywhere.
One source
UDI data in your own system.
Less manual work
Registration without retyping.
Consistent everywhere
EUDAMED and label match.
Security and privacy in a UDI integration
The integration works with product data and access to EUDAMED on behalf of your organisation. Credentials are stored encrypted and used only by the integration, and every registration is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a UDI integration
Questions manufacturers ask before getting started.
The unique identification of a medical device under the MDR and the IVDR. It consists of a fixed part for the model or version, the UDI-DI, and a part for production, such as the lot or serial number. There is also a Basic UDI-DI for the product group.
The European database for medical devices, set up by the European Commission. It consists of modules, including one for UDI and devices. That module has been mandatory for new devices since 28 May 2026.
Yes, a transition period applies. Which period applies to your devices follows from the regulations and the European Commission's guidance; you should confirm this with your regulatory affairs specialist or adviser.
Through the methods EUDAMED offers for submitting data, such as files or a machine-to-machine connection. Which route suits your volumes and systems is something we look at in the first step.
For certain changes to a device, such as a different version or packaging. The software flags changes that may require a new UDI-DI so you can assess whether that is the case. What exactly counts follows from the regulations.
Yes. A hospital can scan the UDIs of devices and implants and record them in its own system, for example during an implantation. This makes it possible to trace later which device was used for which patient.
For manufacturers and importers with many devices or versions, for anyone who wants to keep product data in their own system, and for hospitals and distributors who want to record UDIs in their own systems.
UDI data that is correct everywhere?
Tell us how many devices you have, where the product data is stored and how you register today. We'll show you what the integration with EUDAMED and your labels would look like.