Skip to content
Use caution Medical device recall · FDA · Published April 12, 2023

Spacelabs Healthcare UVSL Command Module Recall: Missing Alarms May Cause Missed Events

Spacelabs Healthcare recalls UVSL Command Module Model 91496 with software versions 2.03.06 and earlier or 2.04 and later. This may cause clinicians to miss critical events due to missing alarms.

🇺🇸 FDA recall #Z-1503-2023Medical deviceSpacelabs Healthcare ›
Take action

Contact the company

Recalling firmSpacelabs Healthcare, Inc.35301 Se Center St · Snoqualmie, WA 98065-9216
✎ GovInfoNow plain-language explainer

Spacelabs Healthcare is recalling its Ultraview SL Command Module Model 91496 with specific software versions. The recall is because older software versions show waveforms without alarms, and newer versions show no waveforms at all, which could lead clinicians to miss serious medical events. Read more at govinfonow.com/recall/58585-spacelabs-healthcare-uvsl-command-module-recall-missing-alarms-may-cause.

Source Summary by GovInfoNow · govinfonow.com/recall/58585-spacelabs-healthcare-uvsl-command-module-recall-missing-alarms-may-cause · Updated August 19, 2026 · FDA enforcement record: FDA #Z-1503-2023

Cite this page

“Spacelabs Healthcare UVSL Command Module Recall: Missing Alarms May Cause Missed Events.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/58585-spacelabs-healthcare-uvsl-command-module-recall-missing-alarms-may-cause. Based on FDA recall #Z-1503-2023 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1503-2023%22&limit=1).

The FDA announced on April 12, 2023, that Spacelabs Healthcare is recalling Ultraview SL Command Module Model 91496 units because they may display waveforms without alarms or lack waveforms entirely when parameter processing suspends. This malfunction may cause clinicians to miss a potentially catastrophic event.

How to tell if you have it

  • Brand: Spacelabs Healthcare
  • Product: Ultraview SL (UVSL) Command Module
  • Model: 91496
  • Software versions: 2.03.06 and earlier, 2.04 and later

The hazard

Command modules may display waveforms with no alarms (older software versions) or have absent waveforms with no alarms (newer versions) when parameter processing is suspended. This failure may cause clinicians to miss a potentially catastrophic event.

Context

GovInfoNow's records show Spacelabs Healthcare, Inc. has 10 other recalls on record since Jan. 17, 2018. Other recent recalls of similar products include Philips IntelliVue MX100 Patient Monitor Recall (Oct. 31, 2025), Philips IntelliVue MX550 Patient Monitor Recall (Oct. 31, 2025) and Philips IntelliVue MX450 Patient Monitor Recall (Oct. 31, 2025).

How to tell if you have this one

Check if your Ultraview SL Command Module Model 91496 has software version 2.03.06 or earlier, or version 2.04 or later. These specific software versions are part of the recall.

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

What to do — step by step

  1. Check Software Version

    Identify the software version on your Ultraview SL Command Module Model 91496 to determine if it is affected by the recall.

Where it went and when

Where it was distributed

Distributed nationwide; the notice names 47 states.

Alaska: named in the noticeAKMaine: named in the noticeMEVermont: nationwideVTNew Hampshire: named in the noticeNHWashington: named in the noticeWAIdaho: named in the noticeIDMontana: named in the noticeMTNorth Dakota: named in the noticeNDMinnesota: named in the noticeMNIllinois: named in the noticeILWisconsin: named in the noticeWIMichigan: named in the noticeMINew York: named in the noticeNYRhode Island: named in the noticeRIMassachusetts: named in the noticeMAOregon: named in the noticeORNevada: named in the noticeNVWyoming: named in the noticeWYSouth Dakota: named in the noticeSDIowa: named in the noticeIAIndiana: named in the noticeINOhio: named in the noticeOHPennsylvania: named in the noticePANew Jersey: named in the noticeNJConnecticut: named in the noticeCTCalifornia: named in the noticeCAUtah: named in the noticeUTColorado: named in the noticeCONebraska: named in the noticeNEMissouri: named in the noticeMOKentucky: named in the noticeKYWest Virginia: named in the noticeWVVirginia: named in the noticeVAMaryland: named in the noticeMDDelaware: named in the noticeDEArizona: named in the noticeAZNew Mexico: nationwideNMKansas: named in the noticeKSArkansas: named in the noticeARTennessee: named in the noticeTNNorth Carolina: named in the noticeNCSouth Carolina: named in the noticeSCDistrict of Columbia: nationwideDCOklahoma: named in the noticeOKLouisiana: named in the noticeLAMississippi: named in the noticeMSAlabama: named in the noticeALGeorgia: named in the noticeGAHawaii: nationwideHITexas: named in the noticeTXFlorida: named in the noticeFL

FDA distribution: “US Nationwide distribution in the states of SD, KY, MO, WA, OH, NC, CA, OR, TX, GA, IL, OK, SC, PA, AL, KS, FL, ID, MI, MN, IA, NJ, MD, VA, AR, CT, NE, LA, AK, MS, ME, WV, NY, AZ, TN, WY, IN, MA, MT, CO, DE, ND, WI, NV, RI, NH, UT.” States read from FDA’s own wording; “not listed” means the notice does not name it.

Named in the notice: Alabama, Alaska, Arizona, Arkansas, California, Colorado, Connecticut, Delaware, Florida, Georgia, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New York, North Carolina, North Dakota, Ohio, Oklahoma, Oregon, Pennsylvania, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Virginia, Washington, West Virginia, Wisconsin, Wyoming.

Recall timeline

FDA published this recall 28 days after the firm started it.

1. Firm started the recall: Apr 12, 202312. FDA classified it Class II: May 3, 202323. Published in FDA’s Enforcement Report: May 10, 202332023
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report

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-1503-2023 (April 12, 2023) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1503-2023 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