EUDAMED actor acquisitions: full versus partial scope and manual inactivation
The acquired ACT 2.27.0 dictionary describes full-actor and partial-product-line acquisitions separately. Its inactivation-date description explicitly says the date does not trigger automatic inactivation; the acquiree performs that step manually. Plan actor and device-record responsibilities accordingly.
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
Actor / FLD-ACT-142 / Acquirer
Description: Reference to the Actor initiating the acquisition/merger request (the buying party). | Occurrence: 1 | Updateability: not stated | Referenced rules: not stated | XML mapping: not stated [1]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Actor / FLD-ACT-144 / Acquiree
Description: Reference to the Actor being acquired. Entered by the Acquirer via Actor ID/SRN lookup. | Occurrence: 1 | Updateability: not stated | Referenced rules: not stated | XML mapping: not stated [2]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Actor / FLD-ACT-146 / Type of acquisition
Description: Specifies whether the request covers a Full acquisition of the Actor or a Partial acquisition limited to a specific devices product line. | Occurrence: 1 | Updateability: not stated | Referenced rules: not stated | XML mapping: not stated [3]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Actor / FLD-ACT-147 / Inactivation
Description: Indicates whether the Acquiree Actor should be inactived upon completion of the acquisition.
Only applicable when acquisitionType is Full acquisition of the Actor. | Occurrence: 0..1 | Updateability: not stated | Referenced rules: Only applicable when acquisitionType = Full_Acquisition_Merger | XML mapping: not stated [4]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Actor / FLD-ACT-148 / Inactivation date
Description: The date on which the Acquiree Actor should be set to inactive.
Applicable and required only when acquisitionType = Full acquisition of the Actror AND inactivation = Yes. Not applicable for Partial acquisition of the devices (product line).
Note: does not trigger automatic inactivation. The actual inactivation must be performed manually by the Acquiree. | Occurrence: 0..1 | Updateability: not stated | Referenced rules: Required when inactivation = Yes AND acquisitionType = Full_Acquisition_Merger | XML mapping: not stated [5]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
Actor / FLD-ACT-150 / State
Description: Current workflow state of the acquisition request. System-managed lifecycle.
Values: Submitted | Withdrawn | Approved | Refused | Occurrence: 1 | Updateability: not stated | Referenced rules: not stated | XML mapping: not stated [6]
Apply this source context to the specific tasks below; retain missing facts and review current target-environment compatibility.
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 actor acquisitions 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 parties and acquisition scope
Confirm acquirer/acquiree actor IDs and whether the request covers the full actor or a defined product line.
Useful evidence: An actor-identity and device-line scope inventory.
Review inactivation dependencies
For a full acquisition, review the actual inactivation choice/date and assign the manual action to the responsible acquiree; do not assume a date schedules it.
Useful evidence: An ownership/action checklist and continuity plan.
Track the actual request outcome
Reconcile the system-managed state and affected record ownership before considering the data migration complete.
Useful evidence: A request-state ledger and verified post-change record reconciliation.
Work packages and dependencies
Conditional: EUDAMED actor acquisitions: full versus partial scope and manual inactivation — Review the actual current records and target-environment requirements; complete the specific mapping/onboarding or maintenance task with source/version and acceptance evidence.
Optional: Related preparation or maintenance support — Use only where the mapped records require that additional phase; confirm ownership and deliverables before adding this service.
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.
