Residual clinical specimens from patients with signs and symptoms of HSV-1, HSV-2, or VZV infection
The sponsor used residual clinical specimens to evaluate the clinical sensitivity and specificity of the Savanna HSV 1+2/VZV Assay compared to an FDA-cleared nucleic acid amplification test.
Clinical Study #1; Retrospective evaluation of residual clinical specimens
Symptomatic patients suspected of HSV-1, HSV-2, or VZV infection; Sample Size: 590; Number of Sites: 3
FDA-cleared nucleic acid amplification test
Clinical sensitivity (PPA) and specificity (NPA)
Clinical Study #2; Retrospective evaluation of residual frozen clinical specimens
Symptomatic patients suspected of HSV-1, HSV-2, or VZV infection; Sample Size: 154
FDA-cleared nucleic acid amplification test
Clinical sensitivity (PPA) and specificity (NPA)
Indications for Use
The Savanna HSV 1+2/VZV Assay is an automated, rapid multianalyte real-time PCR test for the simultaneous qualitative detection and differentiation of herpes simplex virus type 1, herpes simplex virus type 2, and varicella-zoster virus DNA isolated from human cutaneous or mucocutaneous lesion samples obtained from symptomatic patients suspected of active herpes simplex virus 1, herpes simplex virus type 2 and/or varicella-zoster infection. This in vitro diagnostic test is intended to aid in the diagnosis of patients with signs or symptoms of herpes simplex virus type 1, herpes simplex virus type 2, and varicella-zoster virus infection. The Savanna HSV 1+2/VZV Assay is intended to aid in the diagnosis of herpes simplex virus 1, herpes simplex virus type 2 and varicella-zoster virus active infections. The results of this test should not be used as the sole basis for diagnosis, treatment or other management decisions and must be combined with clinical observations, patient history and/or epidemiological information. Negative results do not preclude herpes simplex virus type 1, herpes simplex virus type 2, or varicella-zoster virus infection that is not detected by a cutaneous or mucocutaneous lesion swab specimen. Positive results do not rule out co-infection with other organisms. Additional laboratory testing (e.g., viral culture, immunoassay, serology) may be necessary for patient evaluation. Savanna HSV 1+2/VZV Assay is for professional use. The Savanna HSV 1+2/VZV Assay is intended for use only with the Savanna instrument. Warning: The Savanna HSV 1+2/VZV Assay is not intended for use with the cerebrospinal fluid (CSF) or to aid in the diagnosis of HSV or VZV infection of the central nervous system (CNS). The Savanna HSV 1+2/VZV Assay is not intended for use in prenatal screening.
Device Story
Device is an automated, rapid, multianalyte real-time PCR assay for use on the Savanna instrument; detects and differentiates HSV-1, HSV-2, and VZV DNA from cutaneous/mucocutaneous lesion swabs. Process: swab specimen in transport media loaded into self-contained cartridge; instrument performs automated lysis (sonication), nucleic acid extraction using paramagnetic particles, and multiplex real-time PCR amplification/detection. Output: positive/invalid results displayed on instrument screen within ~24 minutes. Used in clinical settings by professionals; results aid diagnosis when combined with clinical/epidemiological data. Benefits: rapid turnaround time for active infection diagnosis.
Clinical Evidence
Two multi-site clinical studies evaluated 590 fresh and 154 frozen residual cutaneous/mucocutaneous lesion specimens. Compared to FDA-cleared RT-PCR methods. HSV-1 PPA ranged 92.0-100%, NPA 96.4-100%. HSV-2 PPA 92.9-100%, NPA 97.9-100%. VZV PPA 100%, NPA 99.4-100%. Studies confirm high diagnostic agreement.
Technological Characteristics
Real-time PCR technology; self-contained assay cartridge; target-specific primers and fluorescent-labeled probes; automated extraction, amplification, and detection; compatible with Copan UTM, Remel M4RT, M5, M6 transport media; professional use; Savanna instrument platform.
Indications for Use
Indicated for symptomatic patients suspected of active HSV-1, HSV-2, or VZV infection. For use with cutaneous or mucocutaneous lesion swab specimens. Not for CSF, CNS infection diagnosis, or prenatal screening.
Regulatory Classification
Identification
A herpes virus nucleic acid-based cutaneous and mucocutaneous lesion panel is a qualitative in vitro diagnostic device intended for the simultaneous detection and differentiation of different herpes viruses in cutaneous and mucocutaneous lesion samples from symptomatic patients suspected of Herpetic infections. Negative results do not preclude infection and should not be used as the sole basis for treatment or other patient management decisions. The assay is not intended for use in cerebrospinal fluid samples.
Special Controls
*Classification.* Class II (special controls). The special controls for this device are:(1) Premarket notification submissions must include detailed documentation for the device description, including the device components, ancillary reagents required but not provided, and a detailed explanation of the methodology including primer design and 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 of a clinical study using lesion samples in which Herpes Simplex Virus 1, Herpes Simplex Virus 2, or Varicella Zoster Virus DNA detection was requested. The study must compare the device performance to an appropriate well established reference method.
(4) 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.
(5) The device labeling must include a limitation statement that reads: “The device is not intended for use with cerebrospinal fluid or to aid in the diagnosis of HSV or VZV infections of the central nervous system (CNS).”
(6) Premarket notification submissions must include quality assurance protocols and a detailed documentation for device software, including, but not limited to, standalone software applications and hardware-based devices that incorporate software.
(7) The risk management activities performed as part of the manufacturer's 21 CFR 820.10(c) design and development activities must document an appropriate end user device training program that will be offered as part of efforts to mitigate the risk of failure to correctly operate the instrument.
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.