Reference check: November 7, 2026 · AI-assisted original research guidance · No human author or editorial approval claimed.
A laboratory certificate action concerns an identified operator or site; a reagent recall concerns a defined product and scope. Neither should be relabeled as the other, and neither by itself proves financial distress. This guide explains how to read those records without inventing laboratory sanctions, patient harm or live alerts. No named CLIA suspension, revocation or state license-loss case is asserted here because an individual decision has not been checked.
What the primary records support
CMS describes CLIA oversight of human laboratory testing for health assessment and diagnosis, prevention or treatment, with requirements based on test complexity.[1]
Evidence limit: This is U.S. clinical-testing guidance, not a framework for every environmental, food, industrial or research laboratory. Certification does not establish solvency or reimbursement entitlement.
FDA describes weekly enforcement data from its Recall Enterprise System. Its disclaimer says the data should not be used for public alerts or tracking recall lifecycles and that reported status is not updated after classification.[2]
Evidence limit: A historical ongoing label is not confirmation that a recall remains active today. This guide is not a medical-care decision tool or safety-alert service.
Record Z-0997-2026 describes a firm-initiated Class II recall for specified Beckman Coulter bicarbonate reagent lots, with potential falsely high results associated with LDH interference. The record separates initiation, classification and report dates.[3]
Evidence limit: Only the specified products and lots are described. This is not evidence of company insolvency, a clinical laboratory sanction, present exposure or a current recall lifecycle status.
01 / analytical method
CLIA: identify the certificate, site and actual action
Use the CMS laboratory lookup linked from its program page to begin entity and certificate research. For any suspension or revocation report, obtain the underlying agency notice or decision, exact CLIA identifier, affected site, decision and effective dates, stated scope and any appeal or stay. A general program page or a directory result is not enough to announce a sanction. Record a missing decision as unresolved rather than inferring adverse action from absence in a search.
- Does the decision identify this laboratory and this certificate?
- Is the action proposed, effective, appealed, stayed or superseded?
02 / analytical method
State license loss is a separate evidence trail
Find the applicable state agency and individual order before describing a license suspension or loss. Preserve the jurisdiction, legal entity, site and authorization involved. Do not generalize an action in one state to every site in a national network or substitute CLIA terminology for a state licensing action. Where a laboratory responds or a later order changes the posture, retain both dates and the distinction between claim and determination.
- Which authority and authorization does the notice cover?
- What later response, appeal or order changes the original posture?
03 / analytical method
Worked recall ledger: product scope before headline
For the bicarbonate example in the references, build separate fields for recall number, product references, identified lots, initiation, classification, report date and dataset timestamp. Read the original product and reason fields together; do not extend the notice to unrelated reagents or all laboratories using the manufacturer's instruments. Use current manufacturer and agency instructions for operational decisions; this historical research summary neither issues a public alert nor directs medical care.
- Are the laboratory's product references and lots actually within the original notice?
- Which date describes the firm's action, FDA classification and public report?
04 / analytical method
Status, severity and financial consequence are not interchangeable
FDA's enforcement-data disclaimer limits lifecycle interpretation. Preserve the historical status text but do not use it as a confirmed current critical-risk signal. Recall classification is not a quantified probability of harm, and a recall does not demonstrate insolvency. Commercial implications such as supply interruption or rework require their own evidence. Keep the recall desk linked to accreditation and financial research without merging their conclusions.
- Is the displayed status a historical record or a freshly confirmed agency action?
- What independent evidence supports any asserted operational or financial consequence?
Full primary references
- [1] Clinical Laboratory Improvement Amendments · CMS · Original publication undated; page last modified November 2, 2026 · Source checked 2026-11-07.
https://www.cms.gov/medicare/quality/clinical-laboratory-improvement-amendments - [2] Device Enforcement Overview · FDA / openFDA · Undated guidance; displayed dataset coverage through October 28, 2026 · Source checked 2026-11-07.
https://open.fda.gov/apis/device/enforcement/ - [3] Device enforcement record Z-0997-2026 · FDA / openFDA · Recall initiated October 14, 2025; classification December 23, 2025; report December 31, 2025 · Source checked 2026-11-07.
https://api.fda.gov/device/enforcement.json?search=recall_number%3A%22Z-0997-2026%22&limit=1
Dates describe the original record or its stated revision, not a new event. Source checking is not legal advice, product certification, plagiarism clearance or human editorial approval. Editorial standards · Send a documented correction.