False negative rate of COVID-19 PCR testing: a discordant testing analysis
Bibliographic record
Abstract
BACKGROUND: COVID-19 is diagnosed via detection of SARS-CoV-2 RNA using real time reverse-transcriptase polymerase chain reaction (rtRT-PCR). Performance of many SARS-CoV-2 rtRT-PCR assays is not entirely known due to the lack of a gold standard. We sought to evaluate the false negative rate (FNR) and sensitivity of our laboratory-developed SARS-CoV-2 rtRT-PCR targeting the envelope (E) and RNA-dependent RNA-polymerase (RdRp) genes. METHODS: SARS-CoV-2 rtRT-PCR results at the Public Health Laboratory (Alberta, Canada) from January 21 to April 18, 2020 were reviewed to identify patients with an initial negative rtRT-PCR followed by a positive result on repeat testing within 14 days (defined as discordant results). Negative samples from these discordant specimens were re-tested using three alternate rtRT-PCR assays (targeting the E gene and N1/N2 regions of the nucleocapsid genes) to assess for false negative (FN) results. RESULTS: During the time period specified, 95,919 patients (100,001 samples) were tested for SARS-CoV-2. Of these, 49 patients were found to have discordant results including 49 positive and 52 negative swabs. Repeat testing of 52 negative swabs found five FNs (from five separate patients). Assuming 100% specificity of the diagnostic assay, the FNR and sensitivity in this group of patients with discordant testing was 9.3% (95% CI 1.5-17.0%) and 90.7% (95% CI 82.6-98.9%) respectively. CONCLUSIONS: Studies to understand the FNR of routinely used assays are important to confirm adequate clinical performance. In this study, most FN results were due to low amounts of SARS-CoV-2 virus concentrations in patients with multiple specimens collected during different stages of infection. Post-test clinical evaluation of each patient is advised to ensure that rtRT-PCR results are not the only factor in excluding COVID-19.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.031 | 0.128 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".