EUDAMED production onboarding: assemble the actual Playground testing proof
The acquired help asks for a single PDF containing Playground actor/SRN and Party ID plus successful M2M request/response evidence. Device-upload services also need the successfully registered Basic UDI-DI/UDI-DI and corresponding exchange files. A successful local XML parse alone is not that proof.
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
request-the-use-of-a-new-ap / HTML p [45]
The Proof of testing is required to set-up an AP in Production. Its purpose is to confirm that the prerequisite of a successful AP access/link in Playground is fulfilled by getting concrete information on the successful data exchange in Playground in order to assess whether the Actor can have an active AP in Production. [1]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-a-new-ap / HTML p [46]
There is no template. However, it should contain the information listed below in a single PDF document: [2]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-a-new-ap / HTML li [47]
Your Actor ID / SRN and Party ID in Playground. [3]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-a-new-ap / HTML li [49]
The XML request and response files that prove successful upload and/or download via M2M in Playground environment. [4]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-a-new-ap / HTML p [51]
In case you request the upload of Legacy/Regulation Device/ SPP ( Basic UDI-DI and UDI-DI ) service, please also provide: [5]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-a-new-ap / HTML li [52]
The Basic UDI-DI and UDI-DI of a successfully registered device in Playground. [6]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-a-new-ap / HTML li [54]
The XML request and response files that prove that you have successfully registered this specific device (see point 1 above) via M2M in Playground. [7]
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 production onboarding 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.
Identify the tested environment and actor
Record the Playground actor/SRN and Party ID used for each relevant service.
Useful evidence: An environment/identity sheet, without exposing security tokens in the public brief.
Collect successful application outcomes
Retain the actual XML request and response for upload/download; for device-upload scope, reconcile the registered Basic UDI-DI and UDI-DI with the exchange.
Useful evidence: Correlated test files and the relevant registration evidence.
Assemble the proof package
Ask the provider to assemble one PDF with the required evidence and identify unresolved failures before the Production request.
Useful evidence: A reviewed proof PDF, operation coverage and an unresolved-test list.
Work packages and dependencies
Conditional: EUDAMED production onboarding: assemble the actual Playground testing proof — 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.
