Skip to content
Recall Observatory FDA recall evidence

Exact FDA event identifier

Event 62344

1 recalled-product record grouped only because every row carries this exact official event ID.

Open FDA event record

Event summary

Timeline bucket
April 28, 2011
Product types
Device
Classifications
Class III
Statuses
Terminated
Recalling firm wording
Sunquest Information Systems, Inc.

Dossier provenance

Source snapshots represented here

  • openFDA Device Enforcement Report-date coverage June 20, 2012–July 08, 2026 Known gap: openFDA describes 2004-present coverage, but the current export has no report-date records in this interval.
  • openFDA Device Recall event_date_initiated coverage June 01, 1997–June 30, 2026

Enforcement coverage uses report dates; product initiation dates can precede those bounds. Device-enrichment coverage uses FDA event_date_initiated.

How coverage and grouping work

Complete imported group

Every recalled product in this event

1 official enforcement rows

Product dates, classifications, firms, and source wording remain attached to their individual rows. Opening this dossier never hides products that did not match a prior timeline filter.

device · product 1 of 1

Sunquest Laboratory SMART & Sunquest Laboratory SMART Select

Z-2216-2012
Recall number
Z-2216-2012
Initiated
April 28, 2011
Classification
Class III
Status
Terminated
Quantity
103 sites

App-derived interpretation

Unknown reason.no_named_rule · v1.0.0
In Online Entry (OEx) there are two scenarios where a Test result from one container may file to a Test on another container. In order for this to occur: 1) Site parameter SIT 1,2,1,26 (3,217) [Restrict resulting of tests to owner container (<Y>/N)]=Y. 2) The Tests are ordered on the same accession number and 3) The Test codes are defined to have the same upload code as either replicate or

These labels are deterministic app interpretations, not FDA categories.

Official device-enrichment evidence · Sourced

Software design

Compare all device evidence states

Inspect official wording and provenance

Reason for recall

In Online Entry (OEx) there are two scenarios where a Test result from one container may file to a Test on another container. In order for this to occur: 1) Site parameter SIT 1,2,1,26 (3,217) [Restrict resulting of tests to owner container (<Y>/N)]=Y. 2) The Tests are ordered on the same accession number and 3) The Test codes are defined to have the same upload code as either replicate or

Code information

Version 6.3.0 and Later

Distribution pattern

Nationwide Distribution