Medical devices, healthcare technology and the business of care
FDA RECALL RECORD · Z-1392-2025

Origin Data Management software versions 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1 Recall

Origin Data Management software versions 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1

FDA recall Class II

Ongoing

FDA lists this Class II recall for Origin Data Management software versions 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-1392-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Feb 10, 2025
FDA report date
Mar 26, 2025
Quantity in commerce
N/A
Distribution
See key details
FDA cause
Software design

What is being recalled?

Origin Data Management software versions 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1

The retrieved code information does not contain explicit model/GTIN pairs that this publication can reliably map.

Search FDA identifier text

Search a model, catalog, lot or UDI value exactly as printed in FDA’s product description or code information.

This search checks only the FDA product description and code information displayed on this page. It does not decode a UDI, normalize GTIN lengths or establish a relationship between separately listed codes.

FDA code information

Origin Data Management software version 3.1 is 04056481145118; Origin Data Management software version 3.2 is 04056481146078

View the original FDA recall notice

Why was this product recalled?

Under certain circumstances, it can occur that patient records from unrelated individuals are automatically merged into one patient record without user notification.

What actions did Brainlab AG take?

An URGENT FIELD SAFETY NOTICE / PRODUCT NOTIFICATION letter was sent to customers beginning 2/10/25. User Corrective Action: According to our records, at least one of the affected software versions is installed at your site. Therefore, when handling patient data intended to be used with Brainlab Software, adhere to the following instructions: Sequence 1 (Gender) " Do not edit only the Gender field of any already merged/edited patient record. (In the Patient Selection application, such a patient record is displayed with a Restore button next to it.) " For patient records that have not already been merged/edited, adapt all necessary fields including Gender in one single operation using Edit. Only then can you merge additional patient records to the edited patient record, if applicable. (In the Patient Selection application, such a patient record does not have a Restore button next to it.) Sequence 2 (ID) " Do not edit a Patient ID to a value that was the original ID of a previously merged/edited unrelated patient record. To verify whether a Patient ID has been previously used, perform the following steps before making any edits that affect Patient ID: 1. Search for the Patient ID that you want to use as the target ID in the search field in Patient Selection (do not use the Advanced Search). 2. If entries with the Restore button are shown in the patient list, - AND the searched Patient ID is not displayed - AND the Patient Name does NOT correspond to the individual intended to be treated, do not proceed with editing or merging and contact Brainlab support. For merges/edits originating externally from a Hospital Information System (HIS) that is connected to the above-listed versions of Brainlab ODM software: " Contact your HIS administrator (for the ADT interface) and clarify whether ADT A40 (merge patient) messages are used to edit Patient IDs in the system. If Patient IDs are changed via ADT A40 messages, contact Brainlab support so that we can verify whether our s

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA notice posted

  3. FDA classification recorded

  4. FDA enforcement report date

Related FDA submissions

No submission number with an exact verified relationship is linked in the retrieved recall notice.

FDA’s notice explicitly links the submission numbers shown here. Read each filing for its own recorded device and scope.

Source and update history

  1. FDA enforcement data

    First stored snapshot of this source.

  2. FDA device-recall notice

    First stored snapshot of this source.

The history starts with the versions held by MedtechLedger. Earlier source changes are not reconstructed. Official dates and recorded status come from FDA; page summaries describe the source information.

Our data sources and methodology