Skip to content
Use caution Medical device recall · FDA · Published May 31, 2022

Spacelabs Healthcare Xhibit Telemetry Receiver Model 96280: Software Alarm Escalation

Spacelabs Healthcare recalls Xhibit Telemetry Receiver Model 96280 with software version 1.4.0 due to alarm escalation defect after 25 days of use. Caregivers may not detect technical failures.

🇺🇸 FDA recall #Z-1513-2022Medical 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 Xhibit Telemetry Receiver Model 96280 software version 1.4.0 because a software defect causes alarms to stop working after about 25 days of continuous use. This means caregivers might not notice when the device fails, which could lead to missed medical alerts. Read more at govinfonow.com/recall/60571-spacelabs-healthcare-xhibit-telemetry-receiver-model-96280-software-alarm-escalation.

Source Summary by GovInfoNow · govinfonow.com/recall/60571-spacelabs-healthcare-xhibit-telemetry-receiver-model-96280-software-alarm-escalation · Updated August 19, 2026 · FDA enforcement record: FDA #Z-1513-2022

Cite this page

“Spacelabs Healthcare Xhibit Telemetry Receiver Model 96280: Software Alarm Escalation.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/60571-spacelabs-healthcare-xhibit-telemetry-receiver-model-96280-software-alarm-escalation. Based on FDA recall #Z-1513-2022 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1513-2022%22&limit=1).

The FDA announced on May 31, 2022, that Spacelabs Healthcare is recalling the Xhibit Telemetry Receiver, Model 96280. The device has a software defect that may prevent technical alarms from escalating after approximately 25 days of continuous use.

How to tell if you have it

  • Brand: Spacelabs Healthcare
  • Product: Xhibit Telemetry Receiver
  • Model: 96280
  • Software version: 1.4.0
  • UDI-DI: 10841522100246
  • Units affected: 529

The hazard

According to the FDA, a software-related alarm escalation defect occurs after approximately 25 days of continuous use. Technical alarms for signal loss, all leads off, low battery, SpO2 sensor off, and signal interference do not escalate as specified. This may cause caregivers to miss initial technical alarms and remain unaware of continuing technical failures.

Context

GovInfoNow's records show Spacelabs Healthcare has issued 10 other recalls since January 17, 2018. Recent Spacelabs recalls include the Xhibit Central Station Model 96102 audio/video display failures (June 4, 2026), the Ultraview SL Command Module electrical leakage risk (March 26, 2026), and the Multi-parameter Command Module Model 91496 inaccurate cardiac output readings (February 27, 2026). Other recent recalls of similar products include the GE HealthCare ApexPro v6.0 eDelivery Software recall for potential ECG and SpO2 monitoring loss (April 24, 2026), the GE HealthCare CARESCAPE Telemetry Server ARK-2250L recall for potential ECG/SpO2 monitoring loss (April 24, 2026), and the Philips IntelliVue MX70 monitor may not alarm recall (October 31, 2025).

How to tell if you have this one

Check for the model number 96280 with software version 1.4.0. The device has a unique serial number listed in the recall notice (e.g., 6280-001538).

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

What to do — step by step

  1. Check Device Status

    Verify if your Xhibit Telemetry Receiver has software version 1.4.0 and model 96280 by checking the serial number on the device.

  2. Update Software

    Contact Spacelabs Healthcare to get the software update that fixes the alarm escalation issue.

Where it went and when

Where it was distributed

Distributed nationwide and abroad; the notice names 34 states.

Alaska: named in the noticeAKMaine: named in the noticeMEVermont: nationwideVTNew Hampshire: nationwideNHWashington: named in the noticeWAIdaho: named in the noticeIDMontana: named in the noticeMTNorth Dakota: nationwideNDMinnesota: named in the noticeMNIllinois: named in the noticeILWisconsin: nationwideWIMichigan: named in the noticeMINew York: named in the noticeNYRhode Island: nationwideRIMassachusetts: named in the noticeMAOregon: named in the noticeORNevada: nationwideNVWyoming: nationwideWYSouth 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: nationwideCTCalifornia: named in the noticeCAUtah: nationwideUTColorado: named in the noticeCONebraska: nationwideNEMissouri: named in the noticeMOKentucky: named in the noticeKYWest Virginia: nationwideWVVirginia: named in the noticeVAMaryland: named in the noticeMDDelaware: nationwideDEArizona: named in the noticeAZNew Mexico: nationwideNMKansas: named in the noticeKSArkansas: named in the noticeARTennessee: named in the noticeTNNorth Carolina: nationwideNCSouth Carolina: named in the noticeSCDistrict of Columbia: nationwideDCOklahoma: named in the noticeOKLouisiana: named in the noticeLAMississippi: nationwideMSAlabama: named in the noticeALGeorgia: named in the noticeGAHawaii: nationwideHITexas: named in the noticeTXFlorida: named in the noticeFL

FDA distribution: “Worldwide distribution - US Nationwide distribution in the states of NY, AR, CO, FL, NJ, AL, KY, TN, SC, WA, OK, MN, PA, GA, VA, CA, OH, IA, KS, MI, IN, TX, MT, MO, ME, LA, IL, SD, MA, OR, ID, MD, AZ, AK and the countries of MB, ON, FR,…” 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, Florida, Georgia, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Missouri, Montana, New Jersey, New York, Ohio, Oklahoma, Oregon, Pennsylvania, South Carolina, South Dakota, Tennessee, Texas, Virginia, Washington.

Recall timeline

FDA published this recall 3 months after the firm started it.

1. Firm started the recall: May 31, 202212. FDA classified it Class II: Aug 11, 202223. Published in FDA’s Enforcement Report: Aug 17, 202232022
  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-1513-2022 (May 31, 2022) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1513-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