EUDAMED M2M acknowledgements: DELIVERED does not establish application acceptance
In the acquired pull example, DELIVERED acknowledges receipt by the EUDAMED access point. A separate application response correlates with the request. Retain both results; transport delivery alone does not prove a valid record or successful registration.
Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.
Sourced criteria · EU · EUDAMED
What changes the service scope?
Decision or task
What the source describes
What to prepare
pull / HTML li [11]
messageID: A unique identifier, issued by the requester [1]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
pull / HTML li [13]
correlationID: An identifier that will correlate the request to the response or to the acknowledgements, issued by the requester [2]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
pull / HTML li [45]
The EUDAMED eDelivery AP sends an Acknowledge message ( ack1 ) to the organisation’s eDelivery AP which implies that request2 was successfully received by the EUDAMED eDelivery AP . The status of the message is now DELIVERED. [3]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
pull / HTML li [55]
correlationID: The same as correlationID from the request message [4]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
m2m-data-exchange-architecture / HTML p [8]
EUDAMED Backend : Is responsible for the data exchange message requests, including the security, access control and reliability aspects, and for constructing the messageresponses. [5]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Dated technical/help evidence, not a complete legal duty set or live EUDAMED response. Current target-environment release, business rules, permissions and actual buyer records remain unresolved. Blank dictionary flags are unknown; occurrence and update notes keep their stated conditions. No credentials, registration deadline or completed production exchange is inferred.
Prepare the EUDAMED M2M acknowledgements work package
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.
Retain request identifiers
Generate and preserve message/correlation IDs for the actual transaction.
Useful evidence: A request log with timestamps and identifiers.
Separate transport and business outcomes
Record the delivery acknowledgement independently from the correlated backend response and reported result.
Useful evidence: A transaction status model with separate transport/application states.
Investigate unresolved exchanges
Ask how missing responses, negative results and safe retries are handled without duplicating records.
Useful evidence: A reconciliation/error-handling procedure and representative test traces.
Work packages and dependencies
Conditional: EUDAMED M2M acknowledgements: DELIVERED does not establish application acceptance — Review the actual current records and target-environment requirements; complete the specific mapping/onboarding or maintenance task with source/version and acceptance evidence.
Questions for providers
How will you resolve the specific field/identity or state dependencies shown here for our actual records?
Which current environment release, permissions and business rules support the proposed operation?
What mapping, unresolved-error and acceptance evidence will you hand over, and who owns each correction?
Sources and data dates
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
