IMMULITE® 2000 Systems PTS PSA 10706281Recalls & reported problems
Siemens Healthcare Diagnostics Products Ltd · PTS PSA Kit 200 Test · Class 3
All models of IMMULITE 2000 Systems PTS PSA (2)
Data updated Oct 18, 2026 from official FDA records · Editorial policy
1 open recall names this device. See the recall details and contact the manufacturer or your healthcare provider.
- Adverse event reports
- 1
- Deaths reported
- 0
- Injuries reported
- 0
- Recalls naming it
- 1
Summary
The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 00630414982212), received between May 2, 2018 and May 2, 2018 — classified as 1 malfunction.
1 FDA recall record name this device's identifier, 1 still open.
6 other recalls cover devices cleared under the same FDA submission (P930027); they may or may not involve this specific model.
Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 18, 2026.
Recalls naming this device
- Sep 30, 2024Class IIOpen, Classified
The IMMULITE 2000 PSA assay for use on the IMMULITE 2000 and IMMULITE 2000 XPi analyzers did not meet the High-dose Hook Effect claim as stated in the Instructions for Use (IFU).
Z-0464-2025 · Root cause: Under Investigation by firm · Recall details · FDA record ↗
Most reported problems
Device problems
- Adverse Event Without Identified Device or Use Problem1
Patient problems
- No Known Impact Or Consequence To Patient1
Recent adverse event reports
The 1 most recent of 1 reports, in the reporter's own words as published by the FDA.
MalfunctionMay 2, 2018Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
A DISCORDANT, FALSELY LOW PROSTATE SPECIFIC ANTIGEN (PSA) RESULT WAS OBTAINED ON ONE PATIENT SAMPLE ON AN IMMULITE 2000 INSTRUMENT. THE DISCORDANT RESULT WAS REPORTED TO THE PHYSICIAN(S) AND WAS QUESTIONED. THE SAME SAMPLE WAS REPEATED ON THE SAME INSTRUMENT, RESULTING HIGHER. A NEW BLOOD DRAW WAS TAKEN FROM THE SAME PATIENT ON A DIFFERENT DATE AND WAS RUN ON THE DAY IT WAS DRAWN ON THE SAME IMMULITE 2000 INSTRUMENT AS THE PREVIOUS SAMPLE. THE RESULTS OF THE REPEAT OF THE INITIAL SAMPLE AND THE NEW BLOOD DRAW MATCHED. THERE ARE NO KNOWN REPORTS OF PATIENT INTERVENTION OR ADVERSE HEALTH CONSEQUENCES TO THE PATIENT DUE TO THE DISCORDANT FALSELY LOW PSA RESULT.
Patient problems: No Known Impact Or Consequence To Patient
MAUDE report 7481067 ↗
Recalls under the same FDA submission
These recalls involve devices cleared under P930027. One submission often covers many models, so check the product and lot details in each record.
- Z-1120-2017 · Dec 21, 2016 · TerminatedIMMULITE/IMMULITE 1000 Systems, Third Generation PSA, Catalog Number/REF LK3PS1, SMN 10706293 (US Kit Catalog) Product Usage: For in vitro diagnostic use with the IMMULITE and IMM
- Z-1119-2017 · Dec 21, 2016 · TerminatedIMMULITE/IMMULITE 1000 Systems, Third Generation PSA, Catalog Number/REF LKUP1, SMN 10380956 (OUS Kit Catalog) Product Usage: For in vitro diagnostic use with the IMMULITE and IMM
- Z-0885-2017 · Nov 18, 2016 · TerminatedIMMULITE 2000/IMMULITE 2000 XPi Systems Prostate-Specific Antigen (PSA) Assay, REF/Catalog Number L2KPTS2, SMN 10706281 and REF/Catalog Number L2KPTS6, SMN 10706282 (US); REF/Catal
- Z-0884-2017 · Nov 18, 2016 · TerminatedIMMULITE/IMMULITE 1000 Systems Prostate-Specific Antigen (PSA) Assay, REF/Catalog Number LKPTS1, Siemens Material Number (SMN) 10706279 (US); Catalog Number LKPS1, SMN 10380960 and
- Z-2047-2013 · Jun 26, 2013 · TerminatedPSA Assays for use in the IMMULITE/IMMULITE 1000 Systems Analyzers, Catalog Numbers LKPS1, LKPS5 and LKPTS1(D); and in the IMMULITE 2000/2000XPi Systems Analyzers, Catalog Numbers
- Z-2090-2008 · May 21, 2008 · TerminatedCOAT-A-COUNT PSA IRMA kit (IKPS1, 2, 5, X). The device is intended as an aid in monitoring patients for disease progress or response to therapy.
Other Total,Prostate Specific Antigen(Noncomplexed&Complexed) For Detection Of Prostate Cancer devices
- IMMULITE® 2000 Systems PTS PSA 10706282Siemens Healthcare Diagnostics Products Ltd · Total,Prostate Specific Antigen(Noncomplexed&Complexed) For Detection Of Prostate Cancer1 recall0 reports
- Elecsys total PSA 08791732190Roche Diagnostics GmbH · Total, prostate specific antigen (noncomplexed & complexed) for detection of prostate cancer48 reports
- Dimension Vista® System TPSA Flex® Reagent Cartridge 10445090Siemens Healthcare Diagnostics Inc. · Total,Prostate Specific Antigen(Noncomplexed&Complexed) For Detection Of Prostate Cancer36 reports
- Dimension® clinical chemistry system TPSA Flex® reagent cartridge 10444889Siemens Healthcare Diagnostics Inc. · Total,Prostate Specific Antigen(Noncomplexed&Complexed) For Detection Of Prostate Cancer12 reports
- Elecsys Total PSA 09744860190Roche Diagnostics GmbH · Total, prostate specific antigen (noncomplexed & complexed) for detection of prostate cancer4 reports
- Elecsys total PSA 08791686160Roche Diagnostics GmbH · Total, prostate specific antigen (noncomplexed & complexed) for detection of prostate cancer3 reports
- Elecsys total PSA 07027966190Roche Diagnostics GmbH · Total, prostate specific antigen (noncomplexed & complexed) for detection of prostate cancer3 reports
- Access Hybritech PSA 37200Beckman Coulter, Inc. · Total,Prostate Specific Antigen(Noncomplexed&Complexed) For Detection Of Prostate Cancer3 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026 · each recall links to the FDA recall notice
- Page last rebuilt: Oct 18, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page