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

Brand Name: TBS Osteo Product Name: TBS iNsight Recall

Brand Name: TBS Osteo Product Name: TBS iNsight Model/Catalog Number: TBS iNsight v3.x / pn: OS-TBSi Software Version: V3.x: (1) V3.1.2, (2) V3.1.1, (3) V3.1.0, (4)V3.0.0 Product Description: TBS iNsight is a class II Medical Device software that is installed on bone densitometers for analysis of bone microarchitecture and bone health management Component: No

FDA recall Class II

Ongoing

FDA lists this Class II recall for Brand Name: TBS Osteo Product Name: TBS iNsight. Review the affected identifiers, reported reason and manufacturer instructions below.

Recall at a glance

Recall number
Z-1250-2025
Recall classification
Class II
Enforcement status
Ongoing
Initiation date
Feb 3, 2025
FDA report date
Mar 12, 2025
Quantity in commerce
2036 units (724 US, 1312 OUS)
Distribution
See key details
FDA cause
Software Design Change

What is being recalled?

Brand Name: TBS Osteo Product Name: TBS iNsight Model/Catalog Number: TBS iNsight v3.x / pn: OS-TBSi Software Version: V3.x: (1) V3.1.2, (2) V3.1.1, (3) V3.1.0, (4)V3.0.0 Product Description: TBS iNsight is a class II Medical Device software that is installed on bone densitometers for analysis of bone microarchitecture and bone health management Component: No

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

UDI-DI: (1) B214OSTBSI3120, (2) B214OSTBSI3110, (3) B214OSTBSIV310, (4) B214OSTBSIV300.

View the original FDA recall notice

Why was this product recalled?

Potential variability in calculations from fast array scans compared to array scans when operating on Hologic Horizon machines.

These are potential consequences described in the source. The recall reason does not establish how many injuries or incidents occurred.

What actions did Medimaps Group take?

On February 5, 2025 URGENT MEDICAL DEVICE CORRECTION letters were sent to customers. Actions to be taken by the user: Follow patient management recommendations. This notice needs to be passed on all organisation where the potentially affected devices have been transferred: the DXA manufacturer (Hologic), direct customers, distributors and field partners. Awareness on this notice and resulting action will be maintained through customer communications for an appropriate period of time until the end of the FSCA to ensure effectiveness of the corrective action. Customers are requested to report problem-related incidents to the manufacturer, distributor or local representative, and the national Competent Authority if appropriate, as this provides important feedback.* Adverse reactions or quality problems experienced with the use of this product may be reported to the FDA s MedWatch Adverse Event Reporting program either online, by regular mail or by fax. Action Being Taken by the Manufacturer: Software upgrade Medimaps will issue a maintenance release of the software by the end of February in the worst case and deploy it progressively in the field. The exact plan will be further communicated to customers. The associated FSCA for strongly recommended software update should be completed in 6 months starting from the release of the update version at the end of February 2025.

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