Skip to content

FDA product code · General Hospital

FRCIndicator, Biological Sterilization Process

Product code FRC covers Indicator, Biological Sterilization Process, a Class II device regulated under 21 CFR 880.2800. FDA has cleared 206 devices in this code, 2 of them in the last 12 months. Median review time across the 206 most recent decisions is 115 days. openFDA lists 40 recall records against this code.

Updated · ingest status · JSON

Class
Class II
Regulation
21 CFR 880.2800
Review panel
General Hospital
Clearances
206

What is happening in FRC right now?

FRC (Indicator, Biological Sterilization Process) has one finding. 2 recalls opened in the last 12 months and not yet terminated (Class II) (Z-2331-2026, Z-2332-2026).

Every factor behind the statement above, most consequential first, with the FDA records it came from.
FindingHow much it mattersFDA records
RecallClass II recallZ-2331-2026, Z-2332-2026

Sources checked: predicate ancestry, recalls, adverse events, new entrants, review time, crowding. Composed . Every finding carries the record ids it was derived from; nothing here is an estimate.

How many devices has FDA cleared in FRC?

FDA has cleared 206 devices under product code FRC since the 510(k) programme began in 1976, 2 of them in the last 12 months.

Source: openFDA device/510k · retrieved

Most recent 510(k) clearances in FRC, newest first.
510(k)DeviceApplicantDecision
K260766Celerity 5 HP Biological Indicator (LCB052)STERIS Corporation
K252680Celerity™ 20 HP Biological IndicatorSTERIS Corporation
K251122Terragene® Bionova® BT20 Biological IndicatorTerragene
K251452Celerity 5 HP Biological Indicator (LCB052); Celerity 5 HP Challenge Pack (LCB059); Celerity 20 HP Biological Indicator (LCB044); Celerity 20 HP Challenge Pack (LCB045)Steris
K250061Celerity IncubatorSTERIS Corporation
K250044Celerity 5 HP Biological Indicator (LCB052); Celerity 5 HP Challenge Pack (LCB059); Celerity 20 HP Biological Indicator (LCB044); Celerity 20 HP Challenge Pack (LCB045)STERIS Corporation
K2435013M™ Attest™ Super Rapid Steam Extended Cycle Clear Challenge Pack 1492PCDE; 3M™ Attest™ Auto-reader 490; 3M™ Attest™ Auto-reader 490H; 3M™ Attest™ Mini Auto-reader 490M3M Company
K242453Terragene® Bionova® Photon Process Challenge Device with unique-point integrator (PCD225-2);Terragene® Bionova® Photon Process Challenge Device with moving-front integrator (PCD225-C)Terragene S.A.
K2425383M™ Attest™ Super Rapid Readout Biological Indicator 1493; 3M™ Attest™ Super Rapid Steam Gravity Clear Challenge Pack 1493PCDG; 3M™ Attest™ Auto-reader 490; 3M™ Attest™ Auto-reader 490H; 3M™ Attest™ Mini Auto-reader 490M3M Company
K2419593M™ Attest™ Super Rapid Steam Clear Challenge Pack (1492PCD); 3M™ Attest™ Auto-reader (490); 3M™ Attest™ Auto-reader (490H); 3M™ Attest™ Mini Auto-reader (490M)3M Company

How long does FDA review take for FRC?

The median FDA review time for FRC is 115 days, measured across the 206 most recent decisions with both a received date and a decision date.

Review time here is decision date minus date received, as published by FDA. It is elapsed calendar time, not FDA review days — the two differ whenever the agency stops the clock for an additional information request.

Source: openFDA device/510k · retrieved

Are there recalls in FRC?

openFDA lists 40 recall records against product code FRC. A recall record covers one firm's corrective action and may span many device lots.

  • Z-2331-2026Open, ClassifiedHF Acquisition Co. LLC

    Due to incorrect incubation process being performed on product.

  • Z-2332-2026Open, ClassifiedHF Acquisition Co. LLC

    Due to incorrect incubation process being performed on product.

  • Z-1248-2025Open, ClassifiedTERRAGENE S.A.

    Error in the IFU lists an incorrect incubation time on one occasion of 20 minutes rather than the correct incubation time of 60 minutes.

  • Z-1141-2025Open, ClassifiedHF Acquisition Co. LLC

    Spore test strip monitoring system, designed for routine monitoring of sterilization processes, may have a printing error on the return envelope that may cause spore test results to be reported to the incorrect customer's account.

  • Z-0837-2024Open, ClassifiedTERRAGENE S.A.

    Due to a discrepancy between the FDA-Cleared Indications for Use (IFU) and the actual IFU distributed with the products.

Showing the 5 most recently initiated of 40. Recall class comes from openFDA's enforcement endpoint, which does not carry every recall — where it is missing, none is shown rather than guessed. Status is FDA's own wording; a terminated recall is a closed one, and the total spans the code's whole history, not just what is open today.

Source: openFDA device/recall · retrieved

How many adverse events are reported for FRC?

MAUDE holds 40 adverse-event reports naming product code FRC, 6 of them received in the last 12 months.

MAUDE reports are submitted by manufacturers, importers, user facilities and the public. They are unverified, and a report is not proof that the device caused the event.

Source: openFDA device/event · retrieved

Is adverse-event reporting in FRC unusual?

FRC does not yet have twelve months of adverse-event history in our data, so there is no expected range to compare against. That is a gap in what we hold, not a statement about the device.

Monthly adverse-event reports naming FRC, against the expected range computed from this code's own history. Shaded band is the expected range; a bar above it is the month flagged. Retrieved 11 August 2026.
Reports received per month for FRC, with the expected range and whether the month fell outside it.
MonthReportsExpectedVerdict
2Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
3Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
16Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
2Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
2Insufficient historyNo expected range — too little history
1Insufficient historyNo expected range — too little history
3Insufficient historyNo expected range — too little history

17 months do not have a full, unbroken year of history before them, so no expected range is shown for those. Insufficient history is reported as insufficient rather than as zero: an empty baseline would turn a gap in our data into a spike.

What are the predicate devices in FRC?

FDA publishes no machine-readable predicate field, so no predicate chain is recorded for this code yet.

A predicate chain matters because a device inherits the safety history of what it was compared to. FDA publishes the chain only inside each 510(k) summary PDF, never as data — so where we have edges, they are read from those documents, and where we do not, we say so instead of showing an empty list.

Who files 510(k)s in FRC?

Across the 206 most recent decisions, these applicants filed most often in FRC.

Most frequent applicants in FRC among recent decisions.
ApplicantRecent clearances
STERIS Corporation33
3M Company31
Advanced Sterilization Products17
Raven Biological Laboratories, Inc.12
Spsmedical Supply Corp.9

Applicant names above are exactly as FDA published them, so one company can appear under several spellings.

The same makers, after name resolution

3 companies in FRC file under more than one spelling. Resolving them to one identity — across all six datasets, not just this one — is what makes a joined count possible at all.

Companies in FRC whose FDA filings use more than one spelling of the same name.
CompanyClearancesFDA spellings merged
Steris Corporation352
3M Company322
Spsmedical Supply Corp. A Division of Cantel Medical102

Merges are measured against a hand-labelled sample and held above 98% precision; pairs the matcher is unsure of are queued for a person rather than merged. See DeviceSignal.

Source: openFDA device/510k · retrieved

Watch FRC

Get an email the morning anything changes in FRC — a new clearance, a recall, or an adverse-event spike above this code's own baseline.

Start watching FRC

Data on this page comes from FDA's public openFDA API and is US public domain (CC0). DeviceSignal is an independent commercial service and is not affiliated with the U.S. Food and Drug Administration. Information only, not regulatory advice. Verify anything you rely on against open.fda.gov.