MEDTECH CONSULTING · UDI & SAP

UDI consulting for medical device manufacturers

Turn UDI requirements into a practical data, system and submission concept — tailored to your target markets, product structures, SAP/ERP landscape and internal responsibilities.

  • Understand your data
  • Clarify your processes
  • Plan implementation
A meeting with documents as an illustration of UDI consulting
Bringing business teams and IT together
Our consulting approach in detail

Europe IT Consulting supports medical device manufacturers in the functional and technical design of their UDI processes. The focus is not just on which data a regulatory target system expects. Data origins, responsibilities, validation rules, approvals, transmission frequency and the decision between a project-based process, a portal solution and SAP-integrated UDI data management are equally important.

Consulting can start with an initial UDI assessment or focus on improving an existing process. Together, we examine the relevant target systems, product and UDI structures, existing Excel, SAP, ERP or database sources and the desired operating workflow. The result is a clear target model for data maintenance, validation, approval and transmission to authorities.

Europe IT Consulting combines UDI expertise with experience in SAP and data processes. This enables consulting to go beyond a general requirements description and lead to a concrete implementation roadmap, data preparation or the introduction of a suitable Europe IT solution. The appropriate option is determined by the actual starting situation.

YOUR STARTING POINT

When is UDI consulting useful?

  • New target markets or regulatory databases need to be incorporated into an existing UDI process.
  • Basic UDI-DI, UDI-DI and related product relationships need to be structured or cleaned up.
  • UDI data is spread across SAP, another ERP system, Excel files or multiple databases.
  • Responsibilities across Regulatory Affairs, Quality, master data management, IT and other departments are not clearly defined.
  • Errors only become visible during upload or after submission.
  • Manual entry, XML upload and M2M/Data Exchange need to be assessed for the specific use case.
  • An existing Excel process needs validation, standardisation or migration to a scalable solution.
  • UDI data will be managed and transmitted to target systems directly from the SAP environment.
  • Multiple authorities or target markets need to be served from a shared data foundation.
  • Labelling, barcode and UDI data processes need functional and technical alignment.

CONSULTING AREAS

What does a UDI consulting project clarify?

01

Target systems and scope

Which product areas, entities and target markets are in scope? Which records, authority modules and reporting processes are actually affected?

02

Data model and relationships

How are shared product data, Basic UDI-DI, UDI-DI, authority-specific fields and relationships between records structured?

03

Source systems and responsibility

Where is data created? Which system is authoritative for each field? Which roles maintain, check and approve the information?

04

Data quality and validation

Which formal, structural and business checks are required before approval? How are errors reported clearly and corrected?

05

Solution and transmission method

Is a project-based Excel/XML process, the Global Submission Portal or GUDI suitable? Is manual entry, XML upload or M2M intended for the specific operation?

06

Operations and further development

Is this a one-off transmission, a recurring process, software operation or ongoing project-based support?

THE BASIS FOR YOUR DECISION

Four levels for a sound UDI decision

01

Data source

Where does the data come from and who is responsible for it?

Excel, SAP, ERP, database or other structured source data

02

Europe IT solution

Which solution handles data maintenance, checks or submission control?

GUDI, Global Submission Portal, UDI Excel Cloud Validator or project-based support

03

Technical transmission method

How does approved data reach the relevant target system?

manual entry, XML upload or M2M/Data Exchange

04

Operating model

How is the process organised and operated over time?

one-off or regular transmission, software operation or project support

WORKING TOWARDS IMPLEMENTATION

From your starting point to an actionable UDI roadmap

  1. Establish the starting situation and objectives

    First, we collect information on target markets, affected product groups, existing data sources, current workflows and known problems. We also clarify whether a new process is to be established or an existing solution developed further.

  2. Analyse data and processes

    Together, we examine which UDI data already exists, which relationships and authority-specific additions are needed, and where disconnected workflows, duplicate maintenance or late errors arise.

  3. Define the target model and responsibilities

    The target model describes data ownership, maintenance, validation, approval, transmission and feedback. It shows which tasks belong to the manufacturer, a Europe IT solution and the regulatory target system.

  4. Select a solution and transmission method

    Suitable solution components and technical transmission methods are assessed against the requirements. There is no blanket threshold beyond which XML or M2M must always be used. Data structure, recurrence, quality and the operating model matter just as much as volume.

  5. Prepare and support implementation

    The target model becomes a prioritised roadmap. Depending on the project, this covers data cleansing, mapping, validation rules, roles and approvals, technical implementation, testing, submission preparation and knowledge transfer to the teams involved.

CONCRETE PROJECT DELIVERABLES

Typical outcomes of UDI consulting

  • defined project scope by target market, product area and records
  • overview of existing data sources and authoritative systems
  • business data model with shared and authority-specific information
  • mapping of Basic UDI-DI, UDI-DI and relevant record relationships
  • roles and responsibilities for maintenance, checks and approval
  • validation and error-handling process
  • assessment of suitable Europe IT solutions and transmission methods
  • implementation roadmap with prioritised work packages
  • foundation for implementation, testing, data migration and ongoing operation

The specific scope of services is agreed for each project. Functional and technical consulting supports implementation, but does not replace the manufacturer’s regulatory responsibility or final approval.

FROM CONCEPT TO SOLUTION

Suitable Europe IT solutions following consulting

SAP

GUDI for SAP-integrated processes

When UDI data needs to be maintained, validated and approved in SAP and transmitted directly from GUDI to authorities via M2M, the GUDI SAP UDI Add-on may be the appropriate solution.

PORTAL

Global Submission Portal

For structured data imports, validation and recurring or higher-volume multi-authority workflows, the Global Submission Portal is available.

Understanding UDI-DI, UDI-PI and Basic UDI-DI

UDI stands for Unique Device Identification. In practical data processes, identification and production information must be considered separately:

The information that must be maintained, validated and transmitted depends on the market, product type, data model and specific record. Consulting translates these relationships into the manufacturer’s actual product and system context.

  • UDI-DI: the static Device Identifier for a specific product or packaging level.
  • UDI-PI: the variable production identifiers, such as lot, serial number, manufacturing or expiry date information, where applicable to the product.
  • Basic UDI-DI: the central key in the European system for grouping products within the applicable regulatory framework; it does not appear as a label on the product.
A medical procedure illustrating the UDI topic

GOOD TO KNOW

Frequently asked questions about UDI consulting

Does software need to be selected before UDI consulting?

No. Especially when data sources, target systems, responsibilities and transmission methods have not been finalised, the functional and technical starting situation should be assessed before selecting a product.

Does Europe IT support UDI processes with SAP?

Yes. Consulting can incorporate existing SAP product and material data, roles, validation and approvals. Where an SAP-integrated software process is required, GUDI is the Europe IT solution designed for this purpose.

Can consulting cover several UDI target systems?

Yes. Shared data and authority-specific requirements can be analysed separately. Relevant target systems supported by Europe IT solutions include EUDAMED, swissdamed, FDA GUDID, TGA AusUDID, NMPA China and ÜTS. The specific project scope is defined in advance.

Does UDI consulting guarantee acceptance by an authority?

No. Consulting, data modelling and validation can improve data quality and process reliability, but do not replace the manufacturer’s responsibility or the final processing and decision of the relevant regulatory target system.

THE NEXT STEP

Discuss your UDI starting situation

Would you like to establish or improve your UDI process?

For an initial discussion, information about target markets, product and UDI structures, existing data sources, the current transmission process and key open questions is helpful. This provides a basis for identifying the appropriate next step.

Arrange a discussion about your UDI project.