cobas Strep A Nucleic acid test for use on the cobas Liat System (07341911190); cobas Strep A Quality Control Kit (07402678190)
Device Facts
| Record ID | K260047 |
|---|---|
| Device Name | cobas Strep A Nucleic acid test for use on the cobas Liat System (07341911190); cobas Strep A Quality Control Kit (07402678190) |
| Applicant | Roche Molecular Systems, Inc. |
| Product Code | PGX · Microbiology |
| Decision Date | Aug 28, 2026 |
| Decision | SESE |
| Submission Type | Traditional |
| Regulation | 21 CFR 866.2680 |
| Device Class | Class 2 |
Regulatory Classification
Identification
A Streptococcus spp. nucleic acid-based assay is a qualitative in vitro diagnostic device intended to simultaneously detect and identify various Streptococcus spp. nucleic acids extracted directly from clinical specimens. The device detects specific nucleic acid sequences for organism identification. The identification aids in the diagnosis of diseases caused by bacteria belonging to the genus Streptococcus and provides epidemiological information on these diseases. Pathogenic streptococci are associated with infections, such as sore throat, impetigo (an infection characterized by small pustules on the skin), urinary tract infections, rheumatic fever, and kidney disease.
Special Controls
(b) Classification. Class II (special controls). The special controls for this device are: 1) Premarket notification submissions must include detailed device description documentation, including the device components, ancillary reagents required but not provided, and a detailed explanation of the methodology including primer/probe sequence, design, and rationale for sequence selection. 2) Premarket notification submissions must include detailed documentation from the following analytical and clinical performance studies: Analytical sensitivity (Limit of Detection), reactivity, inclusivity, precision, reproducibility, interference, cross reactivity, carry-over, and cross contamination. 3) Premarket notification submissions must include detailed documentation from a clinical study. The study, performed on a study population consistent with the intended use population, must compare the device performance to results obtained from well-accepted reference methods. 4) Premarket notification submissions must include detailed documentation for device software, including, but not limited to, software applications and hardwarebased devices that incorporate software. 5) Premarket notification submissions must include database implementation methodology, construction parameters and quality assurance protocols, as appropriate. 6) The device labeling must include limitations regarding the need for culture confirmation of negative specimens, as appropriate. 7) A detailed explanation of the interpretation of results and acceptance criteria must be included in the device's 21 CFR 809.10(b)(9) compliant labeling. 8) Premarket notification submissions must include details on an end user device training program that will be offered while marketing the device, as appropriate.
*Classification.* Class II (special controls). The special controls for this device are:(1) Premarket notification submissions must include detailed device description documentation, including the device components, ancillary reagents required but not provided, and a detailed explanation of the methodology including primer/probe sequence, design, and rationale for sequence selection. (2) Premarket notification submissions must include detailed documentation from the following analytical and clinical performance studies: Analytical sensitivity (Limit of Detection), reactivity, inclusivity, precision, reproducibility, interference, cross reactivity, carry-over, and cross contamination. (3) Premarket notification submissions must include detailed documentation from a clinical study. The study, performed on a study population consistent with the intended use population, must compare the device performance to results obtained from well-accepted reference methods. (4) Premarket notification submissions must include detailed documentation for device software, including, but not limited to, software applications and hardware-based devices that incorporate software. (5) Premarket notification submissions must include database implementation methodology, construction parameters, and quality assurance protocols, as appropriate. (6) The device labeling must include limitations regarding the need for culture confirmation of negative specimens, as appropriate. (7) A detailed explanation of the interpretation of results and acceptance criteria must be included in the device's 21 CFR 809.10(b)(9) compliant labeling. (8) Premarket notification submissions must include details on an end user device training program that will be offered while marketing the device, as appropriate.
