Skip to content

Mevion S250 recallZ-0410-2017 · Mevion Medical Systems, Inc. · initiated Oct 21, 2016

Class II Terminated All recalls posted in November 2016

Is my device affected?

  1. Compare the model, catalog and lot or serial numbers on your device or its packaging with the code information below. A recall usually covers only specific models or lots.
  2. If yours is listed, follow the instructions from Mevion Medical Systems, Inc. or your healthcare provider. The company's action is summarized under what the company is doing.
  3. Do not stop using a prescribed or implanted device on your own — talk to your healthcare provider first.

Where to find your model and lot numbers · What recall classes and statuses mean

Why it was recalled

Recovery of Incorrect Isocenter -operational change

FDA root cause category: Software Design Change

What the company is doing

Mevion issued an User Notice letter on October 24, 2016 to their customers. The letter identified the affected product, problem and actions taken. Customers were informed that Mevion will be updating software when it is released. For further clarification or assistance, please contact Rob Cessac by email at [email protected] or by phone at (978) 540-1501.

Recall details

Recall number
Z-0410-2017
Recall class
Class II
Status
Terminated
Initiated by the company
Oct 21, 2016
Posted by the FDA
Nov 15, 2016
Recalling firm
Mevion Medical Systems, Inc.
Quantity
6 units
Product code
MUJ
FDA submissions
K120676
Distribution
US Nationwide Distribution in the states of FL, MO, NJ, OH and OK,

Product description

MEVION S250 Product Usage: Proton Radiation Therapy System

Code information (models, lots, serial numbers)

Serial Number: S250-0001 through S250-0006

Other devices under the same FDA submission

1 device cleared under K120676 — the recall does not name any of them by identifier. One submission often covers many models, so they may or may not be affected.

Sources and updates

How recalls are matched to devices · Editorial policy · Report an error on this page