Skip to content
Lower risk Medical device recall · FDA · Published April 29, 2024

Verathon GlideScope Core 15-inch FHD Software v1.7 Recalls Image Degradation Risk

Verathon recalls GlideScope Core 15-inch FHD monitors with software v1.7 and earlier due to potential image loss or degradation when connected to other devices. Affected units may require software updates to prevent issues.

🇺🇸 FDA recall #Z-2022-2024Medical deviceVerathon ›
Take action

Contact the company

Recalling firmVerathon, Inc.20001 N Creek Pkwy · Bothell, WA 98011-8218
✎ GovInfoNow plain-language explainer

What happened, in plain English

Verathon is recalling GlideScope Core 15-inch FHD monitors with software version v1.7 and earlier because they can lose or degrade images when connected to other devices. This could affect medical imaging systems where clear visuals are critical. Read more at govinfonow.com/recall/55296-verathon-glidescope-core-15-inch-fhd-software-v1-7-recalls.

Source Summary by GovInfoNow · govinfonow.com/recall/55296-verathon-glidescope-core-15-inch-fhd-software-v1-7-recalls · Updated August 18, 2026 · FDA enforcement record: FDA #Z-2022-2024

Cite this page

“Verathon GlideScope Core 15-inch FHD Software v1.7 Recalls Image Degradation Risk.” GovInfoNow, updated August 18, 2026. https://govinfonow.com/recall/55296-verathon-glidescope-core-15-inch-fhd-software-v1-7-recalls. Based on FDA recall #Z-2022-2024 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2022-2024%22&limit=1).

Why it’s dangerous

The software issues can cause image loss or degradation when the monitor connects with other devices. This might lead to unclear medical images, but it does not cause physical harm or system failure.

Who’s affected

Healthcare providers using GlideScope monitors with software versions v1.7 and earlier are most at risk, particularly those in settings where image clarity is essential for diagnosis.

How to tell if you have this one

Check for the model number 0570-0437 and software version v1.7 or earlier on the monitor. The product was sold with a unique identifier starting with 00879123008596.

  • Brand
    Verathon
  • Category
    Medical device
FDA recall event · 2 products

All 2 products in this recall

FDA lists each product line separately under one recall event. Check your product description, lot or code numbers against each row. Every row shares the hazard and remedy on this page.

  • Classification
    Class II
  • Status
    Ongoing
  • Distribution
    US: AK AL AR AZ CA CO CT DC FL GA HI IA ID IL IN KS KY LA MA MD ME MI MN MO MS MT NC ND NE NH NJ NM NV NY OH OK ON OR PA QLD RI SC SD TN TX UT VA VIC WA WI WV WY OUS: Hong Kong, Indonesia, Saudi Arabia
Recall numberProduct, codes & lotsQuantity
Z-2021-2024Brand Name: GlideScope Core 15-inch Monitor Model/Catalog Number: 0570-0404 Product Description: Serialized Monitor; Software Version: v1.9 and earlier/ UDI: UDI/DI: 008791230066392568 devices
Z-2022-2024Brand Name: GlideScope Core 15-inch FHD Model/Catalog Number: 0570-0437 Software Version: Core 15 FHD v1.7 and earlier Product Description: Serialized Monitor; Software versions: v1.7 and earlier/UDI/DI: 008791230085961706 devices
Based on the official FDA remedy

What to do — step by step

  1. Check Software Version

    Verify the software version on your monitor; affected units have v1.7 or earlier.

Where it went and when

Where it was distributed

Distributed in 48 states and D.C., and outside the U.S.

Alaska: yesAKMaine: yesMEVermont: not listedVTNew 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: not listedDEArizona: yesAZNew Mexico: yesNMKansas: yesKSArkansas: yesARTennessee: yesTNNorth Carolina: yesNCSouth Carolina: yesSCDistrict of Columbia: yesDCOklahoma: yesOKLouisiana: yesLAMississippi: yesMSAlabama: yesALGeorgia: yesGAHawaii: yesHITexas: yesTXFlorida: yesFL

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

States: Alabama, Alaska, Arizona, Arkansas, California, Colorado, Connecticut, District of Columbia, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, 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 44 days after the firm started it.

1. Firm started the recall: Apr 29, 202412. FDA classified it Class II: Jun 4, 202423. Published in FDA’s Enforcement Report: Jun 12, 202432024
  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-2022-2024 (April 29, 2024) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-2022-2024 to see it in context.
  • Plain-language summary written by qwen3:4b on August 18, 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