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

mint Lesion, Software Versions: 3.10.0 and 3.10.1. Recall

mint Lesion, Software Versions: 3.10.0 and 3.10.1.

FDA recall Class II

Ongoing

FDA lists this Class II recall for mint Lesion, Software Versions: 3.10.0 and 3.10.1.. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-0710-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Nov 15, 2024
FDA report date
Dec 25, 2024
Quantity in commerce
18 units (7 US, 11 OUS)
Distribution
See key details
FDA cause
Software design

What is being recalled?

mint Lesion, Software Versions: 3.10.0 and 3.10.1.

Affected model & UDI checker

Search the exact identifiers published for Z-0710-2025.

The lookup covers structured identifiers listed on this page. A full UDI may also contain lot or serial information; a GTIN match alone does not check those conditions.

Affected products

Model / catalog numberProductLot scope reportedUDI / GTIN
Not specifiedmint Lesion, Software Versions: 3.10.0 and 3.10.1.Check source notice04260495883106
FDA code information

Software Versions: 3.10.0 and 3.10.1; UDI-DI: 04260495883106;

View the original FDA recall notice

Why was this product recalled?

Some software versions have a malfunction where they may show incorrect orientation labels for a specific subset of DICOM images.

What actions did Mint Medical GmbH take?

On 11/13/2024 and 11/15/2024 "URGENT FIELD SAFETY NOTICE" letters were emailed to customers. US customers on 11/13/2024 and OUS customers on 11/15/2024. Actions to be taken by the user: Please read this information carefully and assess whether you are using an affected product version and if DICOM series with differing patient orientation may be used in your organization (Note: mint Lesion" shows a notice above the images when multi-frame images are displayed (see Figures 1 and 2). If that is the case, the malfunction may occur in your system. Please be aware that displayed orientation markers may indicate a wrong patient orientation. Verify the patient orientation based on anatomical landmarks that you can see in the images, when you rely on patient orientation for reporting findings (e.g., "anomaly in left kidney"). If possible, do not assess DICOM data that may lead to the malfunction with mint Lesion" . If you suspect that your organization uses DICOM files with the described parameters and that they have already been read using mint Lesion" , you can contact Mint Medical support (support@mint-medical.com) to request analysis of your mint Lesion" instance. If you believe that this failure could have occurred in past use of mint Lesion", please review the potentially affected radiological reports in your reporting application and take the necessary steps to correct them. Please inform Mint Medical if this may have led to any patient harm in your organization. Actions being taken by the manufacturer The error will be corrected with a software update. Mint Medical Support will contact you when the update is available to schedule the installation of the update on your system. If you have any questions, email: incidents@mint-medical.com or call (+49) 6221 32 18018.

Read the manufacturer action recorded by FDA

Recall timeline

  1. Recall initiated by firm

  2. FDA classification recorded

  3. FDA notice posted

  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