Skip to content

Public FDA record

Z-0345-2012: Odyssey A radiation treatment planning system

Recall record Z-0345-2012 for PerMedics, Inc.. View source facts, labeled dates, and the original FDA record.

FDA identifier
Z-0345-2012
Company in FDA record
PerMedics, Inc.
FDA classification date
Dec 1, 2011
First observed by MedTech Watch
Nov 16, 2026
Latest observed content change
Nov 17, 2026
Recall classification
Unknown — no matched enforcement classification

Reason stated in the source

Anomaly 1 - Invalid Export of Beam Table and or Collimator Angle for DICOM RT Ion, DICOM Image and RTP Link export files: During PerMedics' internal code reviews for lEC 61217 compliance verification, an issue was identified by PerMedics engineers in three export files: D1COM RT Ion Plan, D1COM RT Image and RTP Link. In some cases, this issue can result in table and/or collimator angle values t

Source facts

Action
PerMedics sent an Odyssey TPS URGENT NOTICE OF CORRECTION letter dated November 4, 2010, to all affected customers. The letter identified the product, the problem, and the action to be taken by the customer. Customers were instructed to: Anomaly 1 User Corrective Action: Install the mandatory new version correcting the software as soon as it is available (see PerMedics Corrective Action below). In the meantime, the following recommendations were provided if they planned to use Odyssey RT Ion Plan, DICOM RT Image, and/or RTP Link export: Workaround for the invalid exported table and/or collimator angle errors: If, prior to the software correction, any of these affected file types were exported from Odyssey, manually verify that the table and collimator angles are correct. Additionally, apply appropriate changes to any angles deemed incorrect that were obtained from Odyssey's DICOM RT Ion Plan, DICOM RT Image, and/or RTP Link files. Only those machines with table and/or collimator angles that increase in the clockwise direction will have the incorrect angles. Anomaly 2 User Corrective Action: Install the mandatory new version correcting the software as soon as it is available (see PerMedics Corrective Action below). In the meantime, the following recommendations are provided if the user - Changes the patients scheduled start date prior to the software correction: Workaround for Incorrect Monitor Unit Values when Changing Treatment Start Date: If, prior to the software correction, the user changes the patient's treatment start date on any fully-computed IMRT plan, IMAT plan or plan containing a "Region DVH" prescription, the user should force a full recommendation oft hose patient plans prior to fixing and exporting the plan. The following procedure can be used to force a full re-computation of the plan: - Open the patient's plan worksheet - Change the algorithm type of the plan - Change the algorithm type back to its original value - Close t
Initiated
2010-11-04
Root cause
Device Design
Terminated
2012-03-02
Distribution
Worldwide Distribution - USA including NY, GA, CA and the countries of Hungary, Brazil, China, India, Italy, and Mexico
Recall number
Z-0345-2012
Recall status
Terminated
CDRH record ID
104018
FDA classified
2011-12-01
Recall event number
59934

Source facts and excerpts are reproduced for research. Dates retain their source meanings. “First observed” describes collection, not FDA publication or product launch.

Recall classification is supplied only when the recall number matches an enforcement record. Recall class and device class are different fields. Several recall records may belong to one recall event.

Useful context

Device classifications

FDA dataset:

Last successful check: Nov 22, 2026

Source classifications may change.

510(k) clearances

FDA dataset:

Last successful check: Nov 22, 2026

FDA publishes this dataset monthly.

Recall records

FDA dataset:

Last successful check: Nov 22, 2026

FDA publishes this dataset weekly.

Keep this research moving.

Follow ten competitors and ten product codes. Get matching changes in your dashboard and a weekly brief, for $49/month.

Start a 14-day free trial ↗