Skip to content
Lower risk Medical device recall · FDA · Published June 12, 2017

Invuity PhotonBlade REF PB1 Recall: Possible Tissue Damage Risk

Invuity recalls PhotonBlade REF PB1 devices due to possible unintended energy discharge causing tissue damage. All units are affected.

🇺🇸 FDA recall #Z-2778-2017Medical deviceInvuity ›
Take action

Contact the company

Recalling firmInvuity, Inc.444 De Haro St · San Francisco, CA 94107-2347
✎ GovInfoNow plain-language explainer

What happened, in plain English

Invuity is recalling all PhotonBlade REF PB1 devices after reports of possible unintended energy discharge that could cause tissue damage. This risk affects patients during use of the device. Read more at govinfonow.com/recall/73882-invuity-photonblade-ref-pb1-recall-possible-tissue-damage-risk.

Source Summary by GovInfoNow · govinfonow.com/recall/73882-invuity-photonblade-ref-pb1-recall-possible-tissue-damage-risk · Updated September 23, 2026 · FDA enforcement record: FDA #Z-2778-2017

Cite this page

“Invuity PhotonBlade REF PB1 Recall: Possible Tissue Damage Risk.” GovInfoNow, updated September 23, 2026. https://govinfonow.com/recall/73882-invuity-photonblade-ref-pb1-recall-possible-tissue-damage-risk. Based on FDA recall #Z-2778-2017 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2778-2017%22&limit=1).

Why it’s dangerous

The device may discharge energy unexpectedly during use, potentially damaging patient tissue. This issue is reported in a small number of customer observations.

Who’s affected

Patients using the Invuity PhotonBlade REF PB: All units are affected. The risk is low as it involves only a small number of customer observations.

How to tell if you have this one

Check for the Invuity PhotonBlade REF PB1 model. All lot numbers are affected, so no specific model or lot number is safe.

  • Brand
    Invuity
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Check Device Model

    Look for the Invuity PhotonBlade REF PB1 model on the device.

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: “nationwide” States read from FDA’s own wording; “not listed” means the notice does not name it.

Distributed nationwide.

Recall timeline

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

1. Firm started the recall: Jun 12, 201712. FDA classified it Class II: Jul 27, 201723. Published in FDA’s Enforcement Report: Aug 2, 201734. FDA terminated the recall: Jun 28, 2023420172023
  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-2778-2017 (June 12, 2017) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-2778-2017 to see it in context.
  • Plain-language summary written by qwen3:4b on September 23, 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