EUDAMED portfolio operations: choose manual input, XML files or M2M
The acquired data-exchange guide distinguishes manual UI entry, manually uploaded/downloaded XML and automated M2M transmission. That difference changes the operational work: data ownership and checks, XSD validation, upload handling or backend integration. Choose using the actual portfolio and transmission frequency; this comparison does not decide current legal registration timing.
Evidence retrieved 2026-10-06. Source versions and topic-specific limits are listed below.
Sourced criteria · EU
What changes the service scope?
Decision or task
What the source describes
What to prepare
What does the manual UI route require?
The guide describes manual input through the EUDAMED application. [2]
Allocate record preparation, entry, checking and subsequent correction owners; use actual portfolio changes to estimate effort.
What is automated in XML upload?
The guide describes automated file generation but manual upload/download, with XML validated against the provided DTX service/entity-model XSDs. [3]
Separate field mapping and file generation/validation from the manual submission and response-checking task.
When is M2M a separate integration task?
The guide describes external-to-EUDAMED automatic XML transmission and notes infrastructure, security, support and low frequency/volume as cost considerations. [4]
Compare actual frequency, volume, backend readiness and operations before purchasing M2M; no unsupported price estimate is supplied.
How are timing and old guidance kept separate?
The acquired exchange-method page contains historical wording about modules available voluntarily. That wording cannot settle current mandatory applicability. [1][5]
Keep the operational method choice separate from a current law/module/date assessment and review authentic current provisions before quoting a deadline.
The current schema files, actual record relationships, complete validation rules, module/date applicability and buyer system facts remain incomplete. A supported exchange method is not an unrestricted public-registry API.
A scoped evidence and handoff plan
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
What does the manual UI route require?
Allocate record preparation, entry, checking and subsequent correction owners; use actual portfolio changes to estimate effort.
Useful evidence: Portfolio/source-system field map, record/change queue and entry/check ownership.
What is automated in XML upload?
Separate field mapping and file generation/validation from the manual submission and response-checking task.
Useful evidence: Current production XSD versions, generated files, validation results and upload/response procedure.
When is M2M a separate integration task?
Compare actual frequency, volume, backend readiness and operations before purchasing M2M; no unsupported price estimate is supplied.
Useful evidence: Transmission volumes/frequency, system readiness and support/security ownership.
How are timing and old guidance kept separate?
Keep the operational method choice separate from a current law/module/date assessment and review authentic current provisions before quoting a deadline.
Useful evidence: Dated source/version register and a separate current applicability review.
Work packages and dependencies
Conditional: Portfolio field mapping, validation and operational change workflow — For this work package, agree the supported criteria, evidence access, covered entities/products and unresolved facts in the table above. Additional services require their own justified scope.
Optional: Separate automated backend integration if justified — For this work package, agree the supported criteria, evidence access, covered entities/products and unresolved facts in the table above. Additional services require their own justified scope.
Questions for providers
Which exact actor, product or processing facts support the quoted scope, and what is still unresolved?
How will the listed records reach the responsible people, and who owns each change or authority request?
Which tasks and entities are excluded from the agreement, and which additional services need a separate assessment?
Sources and data dates
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
