Master-data ownership
Define which approved system owns device identifiers, descriptions, packaging levels, templates and issuing-agency data.
Controlled identity across the device lifecycle
Connect approved device and production identifiers to label or direct marking, code verification, packaging levels, production genealogy and controlled business data.
Practical definition
It turns controlled device master data and production identifiers into the correct human- and machine-readable identity on the correct device or packaging level.
A complete production workflow can control the UDI-DI and relevant UDI-PI data, choose the approved template and carrier, apply the code, verify content and quality, manage rejects or rework, preserve packaging relationships and return approved events to enterprise or regulatory-data processes.
Device identification
The code is the visible outcome of a wider data process. Every field should have an approved source, format, packaging level and lifecycle rule.
Define which approved system owns device identifiers, descriptions, packaging levels, templates and issuing-agency data.
Create or receive lot, serial, manufacture-date, expiry-date or software identifiers where the applicable rule set requires them.
Print a label, mark packaging or apply a suitable permanent identity directly to the device when the specification calls for it.
Confirm code presence, content, readability and human-readable information before the device or pack continues.
Maintain the correct identity at each packaging level and connect unit, carton, case or logistic-unit relationships where needed.
Link device identity to manufacturing lots, components, inspections and release status, then exchange controlled records.
Verification and exceptions
The system should know which physical device was inspected and whether a failure was removed, reworked, destroyed or authorised for another action. It should also manage duplicate identifiers, template mismatch, no-read, partial batches and network recovery.
Regulatory data boundary
Great Britain, Northern Ireland, the European Union and export markets can require different identifiers, data submissions and implementation timing.
Use the latest official guidance when scoping the project. The UK government publishes its medical-device regulation implementation updates, while the European Commission explains the EU UDI system. Oxford Traceability supplies production technology and integration; regulatory interpretation and compliance remain the manufacturer's responsibility.
Frequently asked questions
These answers help define the production boundary while recognising that current official market requirements must be checked separately.
A unique device identifier is a standardised numeric or alphanumeric identity for a medical device. It normally separates a device identifier for the manufacturer and model from production identifiers such as lot, serial, manufacture date or expiry date where applicable.
The UDI-DI identifies the manufacturer and specific device model or version. The UDI-PI carries production information such as a lot or batch, serial number, manufacture date, expiry date or software identification where the applicable rules require it.
Direct marking may be required or useful for some reusable devices, subject to the applicable rules and device risk. Feasibility depends on material, geometry, mark life, cleaning, readability and any effect of the marking process on the device.
Yes. A system can control approved UDI data, apply it to the correct label or pack, verify machine- and human-readable content and manage the identities required at different packaging levels.
Yes, where approved interfaces are available. A practical design defines which system owns device master data, production identifiers, packaging relationships and submission records, then exchanges only controlled information.
No. Great Britain, Northern Ireland, the European Union and export markets can follow different regulatory routes and implementation dates. Manufacturers should confirm current official requirements for each target market before the production system is specified.
Start with device, market and data
Share the device, target markets, packaging levels, data carrier, production identifiers, line speed, existing equipment and systems to connect. We will help define the production architecture.
Talk to Oxford TraceabilityStart with the application
Tell us what you need to identify, verify and connect. We will help define a practical route from line-level hardware to usable production data.