Philips Medical Systems, Inc.

How does FDA spell Philips Medical Systems, Inc.?

FDA publishes this company under 9 different spellings across its datasets. Every figure on this page counts all of them as one company, which is why the totals here are higher than a search for any single spelling would give you.

Showing 8 of 9.

Merges are measured against a hand-labelled sample and held above 98% precision. Pairs the matcher is unsure of are queued for a person rather than merged, because two genuinely different firms with similar names is the error that would corrupt every count on this page.

Which product codes does Philips Medical Systems, Inc. file in?

53 product codes, ranked by how much they file in each.

Showing the 25 they file in most, of 53.

Median review is elapsed calendar days between date received and decision date, as published by FDA. It is not FDA review days — the two differ whenever the agency stops the clock for an additional information request.

Source: openFDA device/510k · retrieved 2026-08-11T14:48:53Z

Has Philips Medical Systems, Inc. had a recall?

openFDA lists 179 recall records naming this company across its whole history, of which 7 were opened in the last 12 months and are not yet marked terminated. A recall record covers one firm's corrective action and may span many device lots.

• Z-2650-2026Open, ClassifiedJAK11 June 2026

  The clinical CT scan may not automatically trigger after the Bolus Tracking scan and may need to be triggered manually. Additional Bolus Tracking shots may occur. This may result in the clinical acquisition being inadequate for diagnosis, causing a potential for patient rescan and receiving additional radiation.

• Z-2651-2026Open, ClassifiedJAK11 June 2026

  The clinical CT scan may not automatically trigger after the Bolus Tracking scan and may need to be triggered manually. Additional Bolus Tracking shots may occur. This may result in the clinical acquisition being inadequate for diagnosis, causing a potential for patient rescan and receiving additional radiation.

• Z-2652-2026Open, ClassifiedJAK11 June 2026

  The clinical CT scan may not automatically trigger after the Bolus Tracking scan and may need to be triggered manually. Additional Bolus Tracking shots may occur. This may result in the clinical acquisition being inadequate for diagnosis, causing a potential for patient rescan and receiving additional radiation.

• Z-1825-2026Class IIOpen, ClassifiedJAK7 March 2026

  Philips has identified three software issues: 1. During a continuous CT (CCT) scan, there is the potential that the Gantry could remain at the current scan position after pressing Go. 2. Potential where the message of Previous Surview Exists Select Previous Surview? or should display but does not appear. 3. After performing Surview and planning the Brain Helical acquisition by setting Brain Area DoseRight Index to increase the dose, there is the potential that the Define Head Area option in the context menu is grayed out.

• Z-0375-2026Class IIOpen, ClassifiedJAK25 September 2025

  Issue 1: The potential for unintentional continued gantry/couch movement when a specific button series is used requiring use of manual stop. Issue 2. When performing a helical/Axial scan with ORI (Dose Right index)/ DOM (Dose Modulation), the WED (Water Equivalent Diameter) value might set itself to zero, and this may lead to an insufficient dose setting after the surview. If operator misses the insufficient dose and the WED value in User Interface and continues with the subsequent helical/Axial scans, then the obtained images will be noisy due to low dose setting. Issue 3: Due to a software failure, the ECG wave file is not saved. As a result, the cardiac offline image reconstruction fails due to the missing ECG wave file, and the user might rescan the patient. Issue 4: This issue is software fault in which the patient orientation will be changed to NULL under specific random scenarios resulting in radiation being delivered from the wrong orientation (surview scan) or in the wrong position (clinical scan) and will generate incorrect and undiagnosable surview/clinical images. Patients may be rescanned for surview and/or clinical images. Issue 5: During scanning, the preview image display is not consistent, the images are not arriving at a fixed rate, skipping images from time to time during scanning. The obtained images might not support making the clinical diagnosis and the user might decide to re-scan the patient. Issue 6: If a user presses the left and middle/right mouse buttons together or afterwards in a short time, both commands are executed and an incorrect auto ROI is created. This ROI coordinates won t be assigned as the object is empty. As a result, the threshold of contrast level will not be reached in the UI and this will prevent the system from automatically triggering the subsequent clinical scan. There is potential safety risk identified for additionally tracker shots and/or rescan of a patient when the clinical scan is not triggered. This issue only affects the manual ROI process.

Showing the 5 most recently initiated of 179.

Recall class comes from openFDA's enforcement endpoint, which does not carry every recall — where it is missing, none is shown rather than guessed. Recall class I is the most serious kind of recall; device class I is the least risky kind of device, and the two are never mixed here.

Source: openFDA device/recall · retrieved 2026-08-11T14:48:53Z

What has Philips Medical Systems, Inc. cleared recently?

Source: openFDA device/510k · retrieved 2026-08-11T14:48:53Z