Mers-Cov And Common Respiratory Pathogens Semi-Quantitative And Quantitative Multiplex Nucleic Acid Detection System (QDS) — FDA decisions, comparisons and evidence
The 2021–2025 analysis contains 2 selected substantially-equivalent FDA decisions under primary product code QDS. Use it to compare documented submissions and evidence with your product. A separate 2026 update contains 0 decisions through 2026-09-27. The latest selected decision across the acquired endpoint is dated 2024-11-06. Neither set establishes a suitable predicate or the route for your device. The complete-year window has 2 decisions; the separate all-observed-date count is 3. 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 Middle East Respiratory Syndrome Coronavirus (MERS-CoV) and common respiratory pathogens qualitative, semi-quantitative or quantitative multiplex nucleic acid detection system is an in vitro diagnostic test for the detection, identification, and quantification of MERS-CoV and common respiratory pathogens associated nucleic acids in human clinical specimens. The test is indicated for individuals meeting specific MERS-CoV clinical and/or epidemiological criteria. It aids in the differential diagnosis of MERS-CoV infection in conjunction with other clinical, epidemiologic, and laboratory data, in accordance with the guidelines provided by the appropriate public health authorities.
Compare the proposed indication, user, anatomy, technology and operating principle with this actual scope; record differences and unresolved facts.
§ 866.4001 A multiplex respiratory panel to detect and identify emerging respiratory pathogen(s) and common respiratory pathogens in human clinical specimens. (a) Identification. A multiplex respiratory panel to detect and identify emerging respiratory pathogen(s) and common respiratory pathogens in human clinical specimens is identified as an in vitro diagnostic device intended for the qualitative detection and identification of both emerging and common respiratory pathogens from individuals meeting specific emerging respiratory pathogen clinical and/or epidemiological criteria. For example, clinical signs and symptoms associated with infection of the emerging respiratory pathogen, contact with a probable or confirmed emerging respiratory pathogen case, history of travel to geographic locations where cases of the emerging respiratory pathogen were detected, or other epidemiological links for which testing of the emerging respiratory pathogen may be indicated. A device to detect and identify emerging respiratory pathogen(s) and common respiratory pathogens in human clinical specimens, and in turn to distinguish emerging respiratory pathogen(s) from common respiratory pathogens, is intended to aid in the differential diagnosis of the emerging respiratory pathogen infection, in conjunction with other clinical, epidemiologic, and laboratory data, in accordance with the guidelines provided by the appropriate public health authorities. (b) Classification. Class II (special controls). The special controls for this device are: (1) The intended use for the labeling required under § 809.10 of this chapter must include a description of what the device detects and measures, the specimen types, the results provided to the user, the clinical indications for which the test is to be used, the specific intended population(s), the testing location(s) where the device is to be used (if applicable), and other conditions of use as appropriate. (2) The labeling required under § 809.10 of this chapter must include: (i) A device description, including the parts that make up the device, ancillary reagents required but not provided, and an explanation of the methodology. (ii) Performance characteristics from analytical studies, including cut-off (if applicable), analytical sensitivity ( i.e., limit of detection), inclusivity, reproducibility, interference, cross-reactivity, instrument carryover/cross-contamination (if applicable), and specimen stability. (iii) Detailed instructions for minimizing the risk of potential users' exposure to the emerging respiratory pathogen(s) that may be present in test specimens and those used as control materials. (iv) Detailed instructions for minimizing the risk of generating false positive test results due to carry-over contamination from positive test specimens and/or positive control materials. (v) A warning statement that the interpretation of test results requires experienced healthcare professionals who have training in principles and use of infectious disease diagnostics and reporting of results, in conjunction with the patient's medical history, clinical signs and symptoms, and the results of other diagnostic tests. (vi) A warning statement that culture should not be attempted in cases of positive results for an emerging respiratory pathogen unless a facility with an appropriate level of laboratory biosafety ( e.g., BSL 3 and BSL 3+) is available to receive and culture specimens. (vii) A warning statement that device positive results for one or more common respiratory pathogens do not rule out bacterial infection, or co-infection with other common respiratory pathogens. (viii) A warning statement that respiratory pathogen(s) detected may not be the definite cause of disease. (ix) A warning statement that the use of additional laboratory testing ( e.g. bacterial culture, immunofluorescence, x-ray findings) and clinical presentation must be taken into consideration in order to obtain the final diagnosis of a respiratory infection. (x) A limiting statement that device negative results for the common respiratory pathogens do not preclude infection of a respiratory pathogen and should not be used as the sole basis for diagnosis, treatment, or other patient management decisions. (xi) A limiting statement that analyte targets ( e.g., pathogen nucleic acid sequences or other molecular signatures) may persist in vivo, independent of organism viability. Detection of analyte target(s) does not imply that the corresponding pathogen(s) is infectious, nor is the causative agent(s) for clinical symptoms. (xii) A limiting statement that detection of pathogen nucleic acid sequences or other molecular signatures is dependent upon proper specimen collection, handling, transportation, storage and preparation. Failure to observe proper procedures in any one of these steps can lead to incorrect results. There is a risk of false negative values resulting from improperly collected, transported, or handled specimens. (xiii) A limiting statement that there is a risk of false positive values resulting from cross-contamination by target organisms, their nucleic acids or amplified product, or from non-specific signals in the assay. (xiv) A limiting statement that there is a risk of false negative results due to the presence of nucleic acid sequence variants in the pathogen targets of the device. (xv) A limiting statement that device performance was not established in immunocompromised patients. (xvi) A limiting statement that positive and negative predictive values are highly dependent on prevalence. The device performance was established during one or more specific respiratory seasons. The performance for some respiratory pathogens may vary depending on the prevalence and patient population tested. False positive test results are likely when prevalence of disease due to a particular respiratory pathogen is low or non-existent in a community. (xvii) In situations where the performance of the device was estimated based largely on testing pre-selected banked retrospective clinical specimens and/or contrived clinical specimen, a limiting statement that the estimated device performance of that specific pathogen or pathogen subtype may not reflect the performance or prevalence in the intended use population. (xviii) For devices with an intended use that includes detection of emerging respiratory pathogen(s), a limiting statement that testing with the device should not be performed unless the patient meets clinical and/or epidemiologic criteria for testing suspected specimens of the emerging respiratory pathogen. (xix) For devices with an intended use that includes detection of emerging respiratory pathogen(s), a limiting statement that positive results obtained with the device for the emerging respiratory pathogen are for the presumptive identification of that pathogen and that the definitive identification of the emerging respiratory pathogen requires additional testing and confirmation procedures in consultation with the appropriate public health authorities ( e.g., local or state public health departments) for whom reporting is necessary. (xx) For devices with an intended use that includes detection of emerging respiratory pathogen(s), a limiting statement that negative results for the emerging respiratory pathogen, even in the context of device positive results for one or more of the common respiratory pathogens, do not preclude infection with the emerging respiratory pathogen and should not be used as the sole basis for patient management decisions. (xxi) For devices with an intended use that includes detection of emerging respiratory pathogen(s), a limiting statement that negative results for the emerging respiratory pathogen may be due to infection of the emerging respiratory pathogen at a specific respiratory tract location that may not be detected by a particular clinical specimen type. A negative result for the emerging respiratory pathogen in an asymptomatic individual does not rule out the possibility of future illness and does not demonstrate that the individual is not infectious. (xxii) For devices with an intended use that includes detection of emerging respiratory pathogen(s), a limiting statement that a nationally notifiable Rare Disease of Public Health Significance caused by an emerging respiratory pathogen must be reported, as appropriate, to public health authorities in accordance with local, state, and federal law. (3) Design verification and validation must include: (i) Performance results of an appropriate clinical study ( e.g., a prospective clinical study) for each specimen type, and, if appropriate, results from additional characterized samples. The clinical study must be performed on a study population consistent with the intended use population and must compare the device performance to results obtained using FDA-accepted comparator methods or to expected negative results if the infection is not generally expected in the intended use population. Clinical specimens evaluated in the study must contain relevant organism concentrations applicable to the specimen type(s) and the targeted analyte(s). Detailed documentation must be kept of that study and its results, including the study protocol, study report for the proposed intended use, testing results, and results of all statistical analyses. (ii) For devices with an intended use that includes detection of emerging respiratory pathogen(s) for which an FDA recommended panel is available, design verification and validation must include the performance results of an analytical study testing an FDA recommended reference panel of characterized samples that contain the emerging respiratory pathogen. Detailed documentation must be kept of that study and its results, including the study protocol, study report for the proposed intended use, testing results, and results of all statistical analyses. (iii) An appropriate risk mitigation strategy, including a detailed description of all procedures and methods, for the post-market identification of genetic mutations and/or novel respiratory pathogen isolates or strains ( e.g., regular review of published literature and annual in silico analysis of target sequences to detect possible mismatches. The required documentation for this device must also include all of the results, including any findings, from the application of this post-market mitigation strategy. (iv) For devices with an intended use that includes detection of multiple common respiratory pathogens, in addition to detecting emerging respiratory pathogen(s) in human clinical specimens, a detailed description of the identity, phylogenetic relationship, or other recognized characterization of the common respiratory pathogens that the device is designed to detect is addressed. Also, address in detail how the device results might be used in a diagnostic algorithm and other measures that might be needed for a laboratory diagnosis of respiratory tract infection. Perform an evaluation of the device compared to a currently appropriate and FDA accepted comparator method. Detailed documentation must be kept of that study and its results, including the study protocol, study report for the proposed intended use, testing results, and results of all statistical analyses. (v) A detailed device description, including the parts that make up the device, ancillary reagents required but not provided, and a detailed explanation of the methodology, including molecular target(s) for each analyte, design of target detection reagents, rationale for target selection, limiting factors of the device ( e.g., saturation level of hybridization and maximum amplification and detection cycle number), internal and external controls, and computational path from collected raw data to reported result ( e.g., how collected raw signals are converted into a reported signal and result), as applicable and appropriate. (vi) A detailed description of the device software, including software applications and hardware-based devices that incorporate software. (vii) For devices with an intended use that includes detection of Influenza A and Influenza B viruses and/or detection and differentiate between the Influenza A virus subtypes in human clinical specimens, in addition to detecting emerging respiratory pathogen(s), a detailed description of the identity, phylogenetic relationship, or other recognized characterization of the Influenza A and B viruses that the device is designed to detect, a description of how the device results might be used in a diagnostic algorithm and other measures that might be needed for a laboratory identification of Influenza A or B virus and of specific Influenza A virus subtypes, and a description of the clinical and epidemiological parameters that are relevant to a patient case diagnosis of Influenza A or B and of specific Influenza A virus subtypes. Perform an evaluation of the device compared to a currently appropriate and FDA accepted comparator method. Detailed documentation must be kept of that study and its results, including the study protocol, study report for the proposed intended use, testing results, and results of all statistical analyses. (4) For devices with an intended use that includes detection of Influenza A and Influenza B viruses and/or detection and differentiate between the Influenza A virus subtypes in human clinical specimens, in addition to detecting emerging respiratory pathogen(s), the labeling required under § 809.10 of this chapter must include the following: (i) Where applicable, a limiting statement that performance characteristics for Influenza A were established when Influenza A/H3 and A/H1-2009 (or other pertinent Influenza A subtypes) were the predominant Influenza A viruses in circulation. When other Influenza A viruses are emerging, performance characteristics may vary. (ii) Where applicable, a warning statement that reads if infection with a novel Influenza A virus is suspected based on current clinical and epidemiological screening criteria recommended by public health authorities, specimens should be collected with appropriate infection control precautions for novel virulent influenza viruses and sent to state or local health departments for testing. Viral culture should not be attempted in these cases unless a BSL 3+ facility is available to receive and culture specimens. (iii) Where the device results interpretation involves combining the outputs of several targets to get the final results, such as a device that both detects Influenza A and differentiates all known Influenza A subtypes that are currently circulating, the device's labeling required under § 809.10(b)(9) of this chapter must include a clear interpretation instruction for all valid and invalid output combinations, and recommendations for any required follow up actions or retesting in the case of an unusual or unexpected device result. (iv) A limiting statement that if a specimen yields a positive result for Influenza A, but produces negative test results for all specific influenza A subtypes intended to be differentiated ( e.g., H1-2009 and H3), this result requires notification of appropriate local, state, or federal public health authorities to determine necessary measures for verification and to further determine whether the specimen represents a novel strain of Influenza A. (5) The manufacturer must perform annual analytical reactivity testing of the device 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 labeling required under § 809.10(b) of this chapter 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 website where the analytical reactivity testing data can be found. The manufacturer's home page, as well as the primary part of the manufacturer's website that discusses the device, must provide a prominently placed hyperlink to the web page containing this information and must allow unrestricted viewing access. (6) If one of the actions listed at section 564(b)(1)(A)-(D) of the FD&C 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 labeling required under § 809.10(b) of this chapter 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 website where the analytical reactivity testing data can be found. The manufacturer's home page, as well as the primary part of the manufacturer's website that discusses the device, must provide a prominently placed hyperlink to the web page containing this information and must allow unrestricted viewing access. [90 FR 40711, Aug. 21, 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.
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.
3 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
0 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.
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.
Mers-Cov And Common Respiratory Pathogens Semi-Quantitative And Quantitative Multiplex Nucleic Acid Detection System [1]
Recorded scope
A Middle East Respiratory Syndrome Coronavirus (MERS-CoV) and common respiratory pathogens qualitative, semi-quantitative or quantitative multiplex nucleic acid detection system is an in vitro diagnostic test for the detection, identification, and quantification of MERS-CoV and common respiratory pathogens associated nucleic acids in human clinical specimens. The test is indicated for individuals meeting specific MERS-CoV clinical and/or epidemiological criteria. It aids in the differential diagnosis of MERS-CoV infection in conjunction with other clinical, epidemiologic, and laboratory data, in accordance with the guidelines provided by the appropriate public health authorities. [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 QDS 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.
