Device 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.
Z-2332-2012
Product summary
- Event
- Event 62768
- Status
- Terminated
- Classification
- Class II
- Quantity
- 126 sites
- Official record key
device-enforcement:Z-2332-2012
Official wording
Reason: 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
Code information: Version versions 6.1.0125 through 6.1.0139, 6.2.1, 6.2.2, 7.0, and 7.0.1
Distribution pattern: Worldwide distribution: USA (nationwide) and countries of: England, United Kingdom and United Arab Emirates.
Derived failure modes
-
Unknown
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