FDA record research

Lateral Flow Immunochromatography Assay For Host Biomarkers Of Respiratory Infection (QXA) — FDA decisions, comparisons and evidence

The 2021–2025 analysis contains 1 selected substantially-equivalent FDA decisions under primary product code QXA. Use it to compare documented submissions and evidence with your product. A separate 2026 update contains 1 decisions through 2026-09-27. The latest selected decision across the acquired endpoint is dated 2026-03-24. Neither set establishes a suitable predicate or the route for your device. The complete-year window has 1 decisions; the separate all-observed-date count is 2. 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?

A device to detect and measure non-microbial analytes to aid in the detection and identification of localized human infections is identified as an in vitro device intended for the detection and qualitative measurement, quantitative measurement, or both of one or more non-microbial analytes in human clinical specimens to aid in the assessment, identification, or both of a localized microbial infection when used in conjunction with clinical signs and symptoms and other clinical and laboratory findings.

Compare the proposed indication, user, anatomy, technology and operating principle with this actual scope; record differences and unresolved facts.

Cited source

Which current section does the record cite?

§ 866.3230 Device to detect and measure non-microbial analytes to aid in the detection and identification of localized human infections. (a) Identification. A device to detect and measure non-microbial analytes to aid in the detection and identification of localized human infections is identified as an in vitro diagnostic device intended for the detection and qualitative measurement, quantitative measurement, or both of one or more non-microbial analytes in human clinical specimens to aid in the assessment, identification, or both of a localized microbial infection when used in conjunction with clinical signs and symptoms and other clinical and laboratory findings. (b) Classification. Class II (special controls). The special controls for this device are: (1) Any sample collection device used must be FDA-cleared, -approved, or -classified as 510(k) exempt (standalone or as part of a test system) for the collection of human specimens; alternatively, the sample collection device must be cleared in a premarket submission as a part of this device. (2) The labeling required under § 809.10(b) of this chapter must include: (i) An intended use with a detailed description of what the device detects and measures, the type of results provided to the user, the sample type, whether the measure is qualitative and/or quantitative, the clinical indications for the test use, and the specific population(s) for which the device is intended. (ii) A detailed description of the performance characteristics of the device for all intended specimen types from the analytical and clinical studies (as applicable) required under paragraphs (b)(3)(ii) and (iii) of this section. (iii) A detailed explanation of the interpretation of results, including acceptance criteria for evaluating the validity of individual runs ( e.g., assessment of internal and/or external quality controls, as applicable). (iv) The following limiting statements: (A) A statement that a negative test result does not preclude the possibility of infection; (B) A statement that the test results should be interpreted in conjunction with other clinical and laboratory data available to the clinician; (C) A statement that consistent device performance is dependent on adequate specimen collection, transport, storage, and processing. Failure to observe proper procedures in any one of these steps can lead to incorrect results; and (D) A statement that details any limitations associated with the samples, as appropriate ( e.g., collected on the day of admission to the intensive care unit). (3) Design verification and validation must include the following: (i) A detailed device description, including as appropriate, all device parts; control elements incorporated into the test procedure; instrument requirements; reagents required but not provided; and the principle of device operation and test methodology, including all preanalytical methods for the processing of specimens and the methodology from obtaining a sample to the result; design of primer/probe sequences; rationale for target analyte selection; and computational path from collected raw data to reported result ( e.g., how collected raw signals are converted into a reported result). (ii) Detailed documentation of analytical studies including analytical sensitivity (Limit of Detection, Limit of Quantitation, and Limit of Blank), inclusivity, cross-reactivity, microbial interference, interfering substances, competitive inhibition, carryover/cross-contamination, specimen stability, within-lab precision, reproducibility, and linearity, as applicable. (iii) Detailed documentation and results either from a clinical study, that includes prospective (sequentially collected) samples for each intended specimen type that are representative of the intended use populations and, when determined to be acceptable by FDA, additional characterized clinical samples; or, when determined to be acceptable by FDA, an equivalent sample set. The clinical study must compare the device performance to results obtained from an FDA-accepted reference method and/or FDA-accepted comparator method, as appropriate. Documentation from the clinical studies must include the clinical study protocol ( e.g., the predefined statistical analysis plan), clinical study report, testing results, and results of all statistical analyses. (iv) An evaluation of the level of the non-microbial analyte in asymptomatic patients with demographic characteristics ( e.g., age, racial, ethnic, and sex distribution) similar to the intended use population of the device. (v) Documentation of an appropriate end user device training program that will be offered as part of efforts to mitigate the risks of false results, failure to operate the device correctly, and failure to interpret test results correctly. (vi) An appropriate risk mitigation strategy to ensure that the device does not prevent any other device(s) with which it is indicated for use, including incorporated device(s), from achieving their intended use ( e.g., safety and effectiveness of the functions of the indicated device(s) remain unaffected). (vii) A detailed description of the impact of any software, including software applications and hardware-based devices that incorporate software, on the device's functions. [90 FR 19643, May 9, 2025]

Read the identification, classification, conditions and referenced limitations in the cited section. A numeric reference match is not a buyer classification or exemption determination.

Cited source

Records with the same supported scope and recorded classification context are grouped here: QXA, QGN. A shared definition does not establish interchangeability of devices.

Historical FDA comparison

2021–2025: five complete calendar years

Primary code QXA

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.

1Selected decisions in these five years
WithheldMedian receipt-to-decision calendar days
1Valid date pairs in the distribution

There are 1 valid recent date pairs. Distribution summaries require at least 20; older records are not substituted for a current benchmark.

20210
20220
20231
20240
20250

Statistical source: FDA openFDA 510(k) decision dataset. Partition 1 Download the identified records and dates (CSV).

Filters, exclusions and reproducible calculation

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.

2 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

1 selected decisions from 2026-01-01 to 2026-09-27. The equivalent previous-year period contains 0 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 / deviceRecorded applicantDecisionRecorded typeCalendar days
K260787 ↗FebriDx Bacterial/Non-bacterial AssayLumos Diagnostics, Inc.2026-03-24Dual Track14
K230917 ↗FebriDx Bacterial / Non-bacterial Point of Care AssayLumos Diagnostics, Inc.2023-06-30Traditional88

Supporting documents actually acquired

Go beyond the database row

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.

The documents are a bounded sample of acquired summaries, not complete evidence coverage of the cohort.

Recorded classification context

Known context: US. Match the intended use and design with the recorded category before treating it as applicable.

Source factRecorded value
FDA product codeQXA [1]
Generic device categoryLateral Flow Immunochromatography Assay For Host Biomarkers Of Respiratory Infection [1]
Recorded scopeA device to detect and measure non-microbial analytes to aid in the detection and identification of localized human infections is identified as an in vitro device intended for the detection and qualitative measurement, quantitative measurement, or both of one or more non-microbial analytes in human clinical specimens to aid in the assessment, identification, or both of a localized microbial infection when used in conjunction with clinical signs and symptoms and other clinical and laboratory findings. [1]
Recorded class2 [1]
Regulation866.3230 [1]
Medical specialtyMicrobiology [1]

Build a comparison that explains the differences

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

What needs to happen first

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

FDA openFDA — device classification records ↗

2026-10-05 · retrieved 2026-10-06

Audit details: precise locators and snapshot identifiers

Source key D01 · snapshot 936de5f5d47b9293b702fc32512a79173969fb788c74a63d9b91abe73f3b86a5

  • [1] device-classification-0001-of-0001.json:results[1160] · record 08b95f6a55be3324e73ee4dc47f86745369b55480f746a34b74b37e7d4cdb8fd

FDA 510(k) summary — K260787 ↗

Tue, 07 Apr 2026 11:34:14 GMT · retrieved 2026-10-06

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 5c80abd9658272f9127da9bba0f53a9c86082111b4884614b444b440bced1ea6

  • [2] PDF page 18 · record bdb5b42fc8091290ea935d5e7878cca2fea0849fa9645647fa3b4abaf908bc6d

FDA 510(k) summary — K230917 ↗

Sat, 01 Jul 2023 12:17:02 GMT · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 7011adfedc886e8a4f82308b4025c642cfe647d68e4ed8f96bf2723538407481

  • [4] PDF page 17 · record 0676b382958283bcc74db0d798212a5224e469e16c9f37e83079d96f386e504c

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare FDA 510(k) Submission Services

Find FDA US Agent Services | Compare & Get Quotes · FDA QMSR Transition & Inspection Readiness (ISO 13485 Alignment)