Topic archive

Philips

MedTech Current publications and recall entries tagged Philips.

Device RecallsRecall Brief

Philips Lumify Class I Recall Addresses Loss of Scanning

Philips is correcting Lumify use instructions after unexpected transducer re-registration and unstable USB connections could prevent or interrupt scanning. FDA's October 19 communication confirms Class I recall status; the correction does not involve removing devices.

Device RecallsRecall Brief

Health Canada Classifies Philips Lumify Ultrasound Recall as Type I

Health Canada has classified the recall of Philips Lumify portable ultrasound systems as Type I after software-related transducer re-registration failures and unstable USB connections were found to prevent or interrupt scanning and delay patient care.

Device RecallsFDA Class II Recall Watch: 28 September–4 October 2026

Philips recalls Spectral CT 7500 over Bolus Tracking issue and potential additional radiation

The software failure can change radiation delivered during a scan, beyond disrupting system availability. Imaging departments must manage the affected workflow while the correction is arranged. For software-quality teams, it shows how failure to stop a scan sequence can become a radiation-control problem.

Device RecallsFDA Class II Recall Watch: 28 September–4 October 2026

Philips recalls Spectral CT systems over image, slice-thickness, and motion software issues

Image artifacts and wrong slice thickness can affect interpretation; unintended motion also concerns system behavior. Radiology, clinical engineering, and software change-control teams need the instructions for this event. It remains separate from the Bolus Tracking recall because its failure modes and corrective instructions differ.

Device RecallsFDA Class II Recall Watch: 14–19 September 2026

Philips recalls EPIQ Elite systems over Doppler sample-location error

Doppler measurements can influence vascular and hemodynamic assessment, so a mismatch between displayed and actual sample location has direct diagnostic relevance. The correction also illustrates how a software-design change can alter measurement interpretation while the device remains usable under specific interim restrictions communicated to clinical users.

Device RecallsFDA Class II Recall Watch: 30 August–5 September 2026

Philips recalls four CT product families over unintended radiation issue

A radiation-related field correction across several CT platforms has broad relevance for imaging departments, service organizations, and device quality teams. The shared software-correction approach also makes grouping appropriate: readers can understand one underlying field action without losing the individual model families, recall numbers, or source records.

Device RecallsFDA Class II Recall Watch: 16–22 August 2026

Philips recalls Incisive CT systems over Bolus Tracking scan-trigger issue

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.

Device RecallsFDA Class II Recall Watch: 9–15 August 2026

Philips recalls Azurion software versions over imaging and geometry failures

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.

Device RecallsFDA Class II Recall Watch: 9–15 August 2026

Philips recalls Allura Xper systems over potential loss of geometry movements

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.