Skip to content
Lower risk Medical device recall · FDA · Published February 2, 2022

Philips StentBoost Live R2.0: Incorrect Configuration Causes Acquisition to Continue

Philips recalls StentBoost Live R2.0 software for Azurion systems with R2.x software due to incorrect EPX database configuration causing acquisition to continue after 40 images instead of stopping automatically.

🇺🇸 FDA recall #Z-0737-2022Medical devicePhilips Healthcare ›
Take action

Contact the company

Recalling firmPhilips Healthcare3000 Minuteman Rd · Andover, MA 01810-1032
✎ GovInfoNow plain-language explainer

Philips is recalling StentBoost Live R2.0 software for use with Azurion systems running R2.x software. The issue causes imaging to continue after 40 images instead of stopping automatically, which could lead to incomplete scans or unnecessary radiation exposure. Read more at govinfonow.com/recall/61186-philips-stentboost-live-r2-0-incorrect-configuration-causes-acquisition-to.

Source Summary by GovInfoNow · govinfonow.com/recall/61186-philips-stentboost-live-r2-0-incorrect-configuration-causes-acquisition-to · Updated August 19, 2026 · FDA enforcement record: FDA #Z-0737-2022

Cite this page

“Philips StentBoost Live R2.0: Incorrect Configuration Causes Acquisition to Continue.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/61186-philips-stentboost-live-r2-0-incorrect-configuration-causes-acquisition-to. Based on FDA recall #Z-0737-2022 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-0737-2022%22&limit=1).

The FDA announced on Feb. 2, 2022, that Philips Healthcare recalled the StentBoost Live R2.0 application used with Philips Azurion systems due to a configuration error preventing automatic image acquisition stoppage. This defect poses a risk of excessive radiation exposure during procedures.

How to tell if you have it

  • Philips StentBoost Live R2.0 application
  • Philips Azurion with software release R2.x
  • Azurion R2.1

The hazard

An incorrect configuration setting in the EPX database causes acquisition to continue as long as the cine pedal is pressed, rather than stopping after 40 images. The on-screen message instructs users to press the pedal until acquisition stops, but the system fails to halt automatically.

Context

GovInfoNow's records show Philips Healthcare has issued six other recalls since June 11, 2018. Other recent recalls of similar products include Philips Azurion System Software R3.1 May Cause Imaging Loss (Dec. 12, 2025), Philips Azurion Systems R3.0 Software Issues: Risk of Image Loss and System Failures (Dec. 8, 2025), and Philips Azurion 7 B20 X-ray System May Not Start Properly (March 3, 2026).

How to tell if you have this one

Check if you have Philips StentBoost Live R2.0 software installed on Azurion systems with R2.x software. The affected software version is identified by the Azurion R2.1 update.

  • Brand
    Philips Healthcare
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Check Software Version

    Verify your Azurion system software version and StentBoost Live application version to confirm if you are affected.

Where it went and when

Where it was distributed

Distributed nationwide.

Alaska: yesAKMaine: yesMEVermont: yesVTNew Hampshire: yesNHWashington: yesWAIdaho: yesIDMontana: yesMTNorth Dakota: yesNDMinnesota: yesMNIllinois: yesILWisconsin: yesWIMichigan: yesMINew York: yesNYRhode Island: yesRIMassachusetts: yesMAOregon: yesORNevada: yesNVWyoming: yesWYSouth Dakota: yesSDIowa: yesIAIndiana: yesINOhio: yesOHPennsylvania: yesPANew Jersey: yesNJConnecticut: yesCTCalifornia: yesCAUtah: yesUTColorado: yesCONebraska: yesNEMissouri: yesMOKentucky: yesKYWest Virginia: yesWVVirginia: yesVAMaryland: yesMDDelaware: yesDEArizona: yesAZNew Mexico: yesNMKansas: yesKSArkansas: yesARTennessee: yesTNNorth Carolina: yesNCSouth Carolina: yesSCDistrict of Columbia: yesDCOklahoma: yesOKLouisiana: yesLAMississippi: yesMSAlabama: yesALGeorgia: yesGAHawaii: yesHITexas: yesTXFlorida: yesFL

FDA distribution: “US Nationwide distribution.” States read from FDA’s own wording; “not listed” means the notice does not name it.

Distributed nationwide.

Recall timeline

FDA terminated this recall 2.8 years after the firm started it.

1. Firm started the recall: Feb 2, 202212. FDA classified it Class II: Apr 5, 202223. Published in FDA’s Enforcement Report: Apr 13, 202234. FDA terminated the recall: Nov 5, 2024420222024
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report
  4. FDA terminated the recall

Dates from the agency record only; steps without a date are left out.

Similar recalls

Latest medical device recalls

Keep exploring

Where this comes from

The facts (hazard, remedy, dates, manufacturer) are pulled from the official FDA recall record. The plain-language summary and step-by-step checklist are written by GovInfoNow to make the official notice easier to act on — they don’t replace it.

  • Official source: FDA Recall #Z-0737-2022 (February 2, 2022) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-0737-2022 to see it in context.
  • Plain-language summary written by qwen3:4b on August 19, 2026, from the official record above. Not reviewed by a person — if it conflicts with the FDA notice, the notice is correct. Report an error on this page.
  • GovInfoNow is an independent service and is not a government agency. We republish official FDA recall data; we don’t issue, amend or administer recalls.
GovInfoNow is an independent guide. We are not FDA or any government agency. Always confirm details with the official recall.Data: CPSC · FDA · NHTSA · USDA