Topic archive
MedTech Current publications and recall entries tagged FDA Class II Recall.
These circuits support neonatal and infant respiratory care, so a connector failure can create both immediate clinical-management needs and broad inventory work. The recall also illustrates how one failure mode may span several FDA product classifications and catalog families while still representing a single underlying field action.
This event directly connects assay precision to treatment decisions and makes prior-result review part of the field response.
The defect is notable because a software import can silently change laboratory calculation logic rather than producing an obvious system failure. Laboratories determine whether predefined rules were modified and whether results need retrospective review.
A machining nonconformance in an implant component can become consequential at the point of surgery, where proper screw engagement is part of fixation. The response also requires removal of affected unused product from implant sets and consignment inventory, making traceability and inventory control important beyond the manufacturing site.
Measurement errors in a diagnostic imaging workstation can affect interpretation even when source images remain available. The mitigation combines retrospective study identification, cross-checking against modality measurements, and a software update.
The event shows how one component-level nonconformance can propagate into many finished surgical-kit configurations and product classifications. For hospitals and manufacturers, the response depends on tracing affected kits, quarantining inventory, applying warning over-labels, removing the affected component before kit use, and notifying downstream customers when products were redistributed.
Bolus Tracking coordinates contrast enhancement with CT image acquisition, so failure to trigger the clinical scan can disrupt an imaging workflow at a critical step. The event also demonstrates a software correction handled under radiation-product requirements, making it relevant to both imaging-service operations and regulatory teams responsible for radiological systems.
The underlying failure is comparatively simple, but the large quantity and broad distribution create substantial inventory and replacement work. The defect requires coordinated field action and downstream notification.
False-negative molecular respiratory results can directly affect diagnostic decision-making, making this recall particularly relevant to laboratories and IVD manufacturers. The failure also shows how a reagent-manufacturing error can escape normal controls while control assays still pass, creating a significant result-integrity and quality-system lesson.
Azurion systems support image-guided interventional procedures, so software failures affecting both imaging and equipment movement can create immediate procedural and workflow consequences. Grouping the two FDA records also illustrates why product-version records with substantially identical failure modes and corrective instructions should be treated as one editorial event.
A potential sterilization underdose in products used to administer fluids into the vascular system has direct clinical and operational significance. The event also creates broad inventory work because facilities must locate specified lots across storage and use locations, discontinue affected product, and manage destruction, quarantine, replacement, and downstream notification.
This event shows how one supplier-component problem can propagate across many finished procedural kits and generate multiple FDA records. For hospitals and supply-chain teams, the operational burden extends beyond a single SKU because affected components must be identified inside kits, clinicians notified, warning labels applied, and downstream customers addressed.
This recall connects a manufacturing-process deviation directly to the reliability of a diagnostic result used in acute kidney injury assessment. It is relevant to IVD quality teams because the FDA record links the non-validated rework to potential downstream diagnostic, treatment, and monitoring consequences rather than a purely administrative nonconformity.
The event combines a physical device-design hazard with a software field correction, making it relevant to both hardware and software quality teams. Its nationwide scope and representative-installed software also create operational work for facilities while the FDA record permits continued use under existing warnings and instructions until correction.
Loss of geometry movement in an interventional fluoroscopic system can disrupt procedure workflow even when imaging remains available. The event is relevant to hospitals because the permanent correction is a future software installation, requiring users to retain and post interim instructions, recognize the failure mode, and use the specified restart process meanwhile.
An incorrect component inside a procedure kit can create a mismatch at the point of use even when the outer product identity appears correct. The event is relevant to vascular-device manufacturers and hospitals because it illustrates the importance of kit-component verification, inventory isolation, and downstream traceability for distributed procedural products.