Linking an existing EUDAMED access point: Party ID and service ownership
The acquired existing-AP workflow validates a Party ID and displays AP information that the requesting actor cannot edit. Its third-party agreement remains specific to each environment. Validate the intended AP and responsibility split before linking it.
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-an-existing-ap / HTML li [16]
Enter the Party ID of the Access Point that you want to use and click on the Validate AP button: [1]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-an-existing-ap / HTML li [18]
You will be able to view information regarding the AP with the specified Party ID. You will not be able to edit that information: [2]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-an-existing-ap / HTML p [24]
The 3rd Party Agreement document is to confirm that a company (either a 3rd party provider or another Actor registered in EUDAMED having already an AP ) agrees to act as 3rd party service provider for the Actor organisation that submits the request for the purposes of M2M DTX with EUDAMED. [3]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-an-existing-ap / HTML p [25]
This document will be used to assess the validation of the AP access/link request and must be provided for each environment where an AP access/link is requested (Playground and Production). [4]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
request-the-use-of-an-existing-ap / HTML p [26]
This document must identify clearly the two parties (Actor and 3rd party service provider) and must be signed by both parties for confirming the agreement from the 3rd party service provider toward the Actor. [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 Linking an existing EUDAMED access point 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.
Validate the intended AP
Obtain the AP Party ID from its owner and verify the displayed information in the intended environment.
Useful evidence: An AP-owner confirmation and reviewed Party ID/environment record.
Prepare the environment agreement
Document actor and third-party responsibilities and have both parties sign the correct environment agreement.
Useful evidence: The signed link agreement and ownership/contact matrix.
Check current service assignments
Ask which services can be assigned to this link and how existing routing will be preserved during cutover.
Useful evidence: A service-routing and migration plan with explicit owner approvals.
Work packages and dependencies
Conditional: Linking an existing EUDAMED access point: Party ID and service ownership — 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.
