Devices Detecting Influenza A, B, And C Virus Antigens (PSZ) — FDA decisions, comparisons and evidence
The 2021–2025 analysis contains 4 selected substantially-equivalent FDA decisions under primary product code PSZ. Use it to compare documented submissions and evidence with your product. A separate 2026 update contains 2 decisions through 2026-09-27. The latest selected decision across the acquired endpoint is dated 2026-09-04. Neither set establishes a suitable predicate or the route for your device. The complete-year window has 4 decisions; the separate all-observed-date count is 73. These denominators describe different date ranges.
Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.
Recorded scope and its declared regulatory reference
An exact FDA-record regulation_number match to one acquired Title 21 section. Records with the same normalized scope definition, class, regulation and recorded submission/GMP flags are grouped. Sparse definitions and generic exemption boilerplate do not qualify. No text-similarity equivalence or legal applicability is inferred.
What scope does the FDA record describe?
An influenza virus antigen detection test system is a device intended for the qualitative detection of influenza viral antigens directly from clinical specimens in patients with signs and symptoms of respiratory infection.
Compare the proposed indication, user, anatomy, technology and operating principle with this actual scope; record differences and unresolved facts.
§ 866.3328 Influenza virus antigen detection test system. (a) Identification. An influenza virus antigen detection test system is a device intended for the qualitative detection of influenza viral antigens directly from clinical specimens in patients with signs and symptoms of respiratory infection. The test aids in the diagnosis of influenza infection and provides epidemiological information on influenza. Due to the propensity of the virus to mutate, new strains emerge over time which may potentially affect the performance of these devices. Because influenza is highly contagious and may lead to an acute respiratory tract infection causing severe illness and even death, the accuracy of these devices has serious public health implications. (b) Classification. Class II (special controls). The special controls for this device are: (1) The device's sensitivity and specificity performance characteristics or positive percent agreement and negative percent agreement, for each specimen type claimed in the intended use of the device, must meet one of the following two minimum clinical performance criteria: (i) For devices evaluated as compared to an FDA-cleared nucleic acid based-test or other currently appropriate and FDA accepted comparator method other than correctly performed viral culture method: (A) The positive percent agreement estimate for the device when testing for influenza A and influenza B must be at the point estimate of at least 80 percent with a lower bound of the 95 percent confidence interval that is greater than or equal to 70 percent. (B) The negative percent agreement estimate for the device when testing for influenza A and influenza B must be at the point estimate of at least 95 percent with a lower bound of the 95 percent confidence interval that is greater than or equal to 90 percent. (ii) For devices evaluated as compared to correctly performed viral culture method as the comparator method: (A) The sensitivity estimate for the device when testing for influenza A must be at the point estimate of at least 90 percent with a lower bound of the 95 percent confidence interval that is greater than or equal to 80 percent. The sensitivity estimate for the device when testing for influenza B must be at the point estimate of at least 80 percent with a lower bound of the 95 percent confidence interval that is greater than or equal to 70 percent. (B) The specificity estimate for the device when testing for influenza A and influenza B must be at the point estimate of at least 95 percent with a lower bound of the 95 percent confidence interval that is greater than or equal to 90 percent. (2) When performing testing to demonstrate the device meets the requirements in paragraph (b)(1) of this section, a currently appropriate and FDA accepted comparator method must be used to establish assay performance in clinical studies. (3) Annual analytical reactivity testing of the device must be performed with contemporary influenza strains. This annual analytical reactivity testing must meet the following criteria: (i) The appropriate strains to be tested will be identified by FDA in consultation with the Centers for Disease Control and Prevention (CDC) and sourced from CDC or an FDA-designated source. If the annual strains are not available from CDC, FDA will identify an alternative source for obtaining the requisite strains. (ii) The testing must be conducted according to a standardized protocol considered and determined by FDA to be acceptable and appropriate. (iii) By July 31 of each calendar year, the results of the last 3 years of annual analytical reactivity testing must be included as part of the device's labeling. If a device has not been on the market long enough for 3 years of annual analytical reactivity testing to have been conducted since the device received marketing authorization from FDA, then the results of every annual analytical reactivity testing since the device received marketing authorization from FDA must be included. The results must be presented as part of the device's labeling in a tabular format, which includes the detailed information for each virus tested as described in the certificate of authentication, either by: (A) Placing the results directly in the device's § 809.10(b) of this chapter compliant labeling that physically accompanies the device in a separate section of the labeling where the analytical reactivity testing data can be found; or (B) In the device's label or in other labeling that physically accompanies the device, prominently providing a hyperlink to the manufacturer's public Web site where the analytical reactivity testing data can be found. The manufacturer's home page, as well as the primary part of the manufacturer's Web site that discusses the device, must provide a prominently placed hyperlink to the Web page containing this information and must allow unrestricted viewing access. (4) If one of the actions listed at section 564(b)(1)(A)-(D) of the Federal Food, Drug, and Cosmetic Act occurs with respect to an influenza viral strain, or if the Secretary of Health and Human Services (HHS) determines, under section 319(a) of the Public Health Service Act, that a disease or disorder presents a public health emergency, or that a public health emergency otherwise exists, with respect to an influenza viral strain: (i) Within 30 days from the date that FDA notifies manufacturers that characterized viral samples are available for test evaluation, the manufacturer must have testing performed on the device with those viral samples in accordance with a standardized protocol considered and determined by FDA to be acceptable and appropriate. The procedure and location of testing may depend on the nature of the emerging virus. (ii) Within 60 days from the date that FDA notifies manufacturers that characterized viral samples are available for test evaluation and continuing until 3 years from that date, the results of the influenza emergency analytical reactivity testing, including the detailed information for the virus tested as described in the certificate of authentication, must be included as part of the device's labeling in a tabular format, either by: (A) Placing the results directly in the device's § 809.10(b) of this chapter compliant labeling that physically accompanies the device in a separate section of the labeling where analytical reactivity testing data can be found, but separate from the annual analytical reactivity testing results; or (B) In a section of the device's label or in other labeling that physically accompanies the device, prominently providing a hyperlink to the manufacturer's public Web site where the analytical reactivity testing data can be found. The manufacturer's home page, as well as the primary part of the manufacturer's Web site that discusses the device, must provide a prominently placed hyperlink to the Web page containing this information and must allow unrestricted viewing access. [82 FR 3618, Jan. 12, 2017]
Read the identification, classification, conditions and referenced limitations in the cited section. A numeric reference match is not a buyer classification or exemption determination.
All statistics in this section use decisions dated 2021-01-01 to 2025-12-31. The partial 2026 update below is excluded from these distributions.
4Selected decisions in these five years
WithheldMedian receipt-to-decision calendar days
4Valid date pairs in the distribution
There are 4 valid recent date pairs. Distribution summaries require at least 20; older records are not substituted for a current benchmark.
20210
20220
20232
20240
20252
Compare like submission types
Recorded type
Decisions
Valid date pairs
Median calendar days
Middle 50%
Dual Track
1
1
Withheld: n < 20
—
Traditional
3
3
Withheld: n < 20
—
Different submission types and evidence packages are not interchangeable. These selected records do not establish that a particular route is available for your product.
Deduplicate by official submission ID across the complete current manifest partitions. Select exact primary product code, K-number format and the stated SE decision codes with valid dates. Recent distributions use the five complete calendar years preceding the latest valid endpoint decision year. Partial-year counts compare equal January-to-cutoff periods. Quartiles use linear interpolation at (n-1)*p and are withheld below 20 valid date pairs. The analysis n describes only its declared complete-year window; selected_se_n separately counts all selected recorded dates through the cutoff.
73 selected records across all observed dates; 0 other/invalid identifier or decision-date records excluded. 0 missing or invalid date pairs in the five-year window.
Date fields: date_received → decision_date. Quantiles: Hyndman–Fan type 7: linear interpolation at (n − 1) × p; displayed to one decimal; n ≥ 20 valid pairs.
Receipt-to-decision calendar elapsed time includes time outside active FDA review; it is not FDA review time, a promised project timeline or an estimate of future clearance. This selected recorded cohort does not include all applications or establish a success probability, predicate suitability, market size, current market availability or legal authorization for another product.
Calculation fda-buyer-research-3 · database cutoff 2026-09-27. CSV rows identify each official K-number, cohort, date pair, exclusion reason and source version.
Separate partial-year update
2026 decisions through 2026-09-27
2 selected decisions from 2026-01-01 to 2026-09-27. The equivalent previous-year period contains 2 decisions through 2025-09-27. These counts describe the records; they are not market growth or submission success rates.
Named records to investigate
Latest decisions across the database
These dated records may come from 2026 or earlier years. They are a separate investigation list, not the five-year statistical cohort. Compare the actual indications and technology before considering a record as a comparator.
Official record / device
Recorded applicant
Decision
Recorded type
Calendar days
K254262 ↗Sofia Influenza A+B FIA; Sofia RSV FIA; Sofia Strep A+ FIA
Read the source context, then compare the evidence with your design. Topic locations below are text matches, including possible limitations or negative statements; they are not a mandatory test list.
Devices Detecting Influenza A, B, And C Virus Antigens [1]
Recorded scope
An influenza virus antigen detection test system is a device intended for the qualitative detection of influenza viral antigens directly from clinical specimens in patients with signs and symptoms of respiratory infection. [1]
Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.
Which specific part of the recorded scope fits or differs?
Put your proposed label and design beside the quoted definition. Record matching facts, differences and missing facts separately; naming the category alone cannot resolve scope.
Useful evidence: Proposed indication/design and a definition-to-product comparison with source locators.
Have the cited section and its limitations been reviewed?
Record the applicable paragraph, conditions and cross-referenced limitations after specialist review. Keep a claimed exemption separate from actual establishment, listing and quality-system responsibilities.
Useful evidence: Dated classification/route rationale and the current provisions relied on, with unresolved conditions.
Compare your intended use with a named decision
Choose a named record above. Put your proposed claim beside its actual indications-for-use statement. Record different patients, users, anatomy, settings and output claims; do not treat a shared code as proof of equivalence.
Useful evidence: Your draft indications for use + the selected official summary and its exact page.
Explain the technology and evidence differences
For each comparison, record the different materials, hardware, software functions and operating conditions. Link each difference to existing evidence or an unresolved evaluation task.
Useful evidence: A three-column matrix: comparator fact / your design fact / evidence or unresolved gap.
Prepare a scope-based schedule without a sparse timing benchmark
This recent cohort has fewer than 20 valid date pairs, so it supplies no median or percentile benchmark. Ask for a schedule based on actual preparation, evidence gaps, interactions and response assumptions; keep any historical decision context separately dated.
Useful evidence: Document/test readiness, unresolved route/evidence tasks and the assumptions behind the specialist’s proposed sequence.
Work packages and dependencies
Conditional: FDA 510(k) Submission Services — Review the supplied facts and evidence gaps before confirming the service scope.
Optional: Find FDA US Agent Services | Compare & Get Quotes — Include only if your product, actor and delivery needs justify this additional scope. Confirm the responsibility and evidence handoff with the coordinating specialist.
Optional: FDA QMSR Transition & Inspection Readiness (ISO 13485 Alignment) — Include only if your product, actor and delivery needs justify this additional scope. Confirm the responsibility and evidence handoff with the coordinating specialist.
What needs to happen first
FDA 510(k) Submission Services → Find FDA US Agent Services | Compare & Get Quotes: Confirm the main product/actor scope and evidence gaps before deciding whether to commission this additional service.
FDA 510(k) Submission Services → FDA QMSR Transition & Inspection Readiness (ISO 13485 Alignment): Confirm the main product/actor scope and evidence gaps before deciding whether to commission this additional service.
Questions for providers
Which of the named PSZ decisions are actually comparable to our proposed indications and technology, and which would you exclude?
Which evidence differences prevent us from using the comparison yet, and what deliverable resolves each one?
Does your schedule separate submission preparation, testing, FDA interactions and customer response time? What assumptions change it?
Sources and data dates
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.