Sunquest Laboratory Sunquest Laboratory is intended for use by… — Class II medical device recall Z-2332-2012
Terminated recall by Sunquest Information Systems, Inc., reported 2012-09-19, distributed nationwide. Sunquest is recalling Sunquest Laboratory versions 6.1.0125 through 6.1.0139, 6.2.1, 6.2.2, 7.0, and 7.0.1 bec
| Recall number | Z-2332-2012 |
|---|---|
| Product type | Medical device |
| Classification | Class II |
| Status | Terminated |
| Voluntary or mandated | Voluntary |
| Recalling firm | Sunquest Information Systems, Inc., Tucson, AZ, United States |
| Recall initiated | 2012-03-15 |
| Classified | 2012-09-07 |
| Reported by FDA | 2012-09-19 |
| Terminated | 2012-10-02 |
| Distributed | Nationwide (US) |
| Countries outside the US | AE, GB |
| Quantity | 126 sites |
Product
Sunquest Laboratory Sunquest Laboratory is intended for use by professionals working in a clinical laboratory. Sunquest Laboratory is intended for use only by professionals who have received extensive training in the use of the software. Sunquest Laboratory is controlled via userdefined security levels, which allow the laboratories to manage data security and integrity. The system is marketed as an automated solution for managing laboratory processes, including: " Patient registration " Order entry and order modification " Specimen collection, verification, suitability, and distribution " Quality assurance checking " Workload recording " Billing charge capture " Standards and controls recording " Test order result inquiry and reporting Organism susceptibility and epidemiology records " Microbiology culture direct examination and observation recording " Outreach clients, specimens, and results " Client-specific reporting capabilities " Inbound client service request tracking " Historical data Clients that use the Sunquest Blood Bank system should refer to the intended use statement found in the Blood Bank System Overview Users Guide.
Reason for recall
Sunquest is recalling Sunquest Laboratory versions 6.1.0125 through 6.1.0139, 6.2.1, 6.2.2, 7.0, and 7.0.1 because when the Windows-based merge application is used and the "Event merge across patients" option is used, a receiving system (for example a HIS or CoPath system) may interpret the event merge as a full patient merge. This occurs because a trigger from the Laboratory system for the event
Machine access
This record, with every extracted code, the verbatim FDA record and provenance, is available from the recall API: GET https://api.data.aroqon.com/v1/recalls/Z-2332-2012. Look up any UPC, UDI, NDC or lot with /v1/recalls/lookup?code=…. API docs · free and paid keys.
Source: U.S. Food and Drug Administration enforcement report via openFDA (CC0). Structured by Data Foundry (recall-structuring@2); last changed 2026-09-26. Not affiliated with or endorsed by FDA. Not medical or legal advice.