The Virobac II® Exhalation Filter is a viral/bacterial filter intended for use when the care provider desires to prevent the transmission of viruses or bacteria from patients receiving respiratory support.
Device Story
Ambu® Virobac II® Exhalation Filter is a single-patient-use, non-sterile viral/bacterial filter; connects to resuscitators via standard ISO conical connectors (30 mm ID/OD). Device utilizes electrostatic filtration to remove microbiological and particulate matter from expiratory air during resuscitation. Used by clinicians in clinical settings; device attaches to the expiratory port of a resuscitator. By filtering exhaled gases, the device reduces the risk of cross-contamination between patients and care providers, potentially improving safety during respiratory support procedures.
Clinical Evidence
No clinical data. Substantial equivalence is supported by non-clinical bench testing, including bacterial/viral filtration efficiency (BFE/VFE ≥ 99.99%), resistance to flow, leak testing, volume, weight, and connection integrity per ISO 5356-1, ISO 10651-4, ISO 23328-1/2, and ASTM F2101. Transportation simulation was performed per ASTM D4169.
Technological Characteristics
Electrostatic filtration; housing made of Methyl Methacrylate Butadiene Styrene; filter media made of polypropylene fibers. Dimensions include 30 mm ID/OD conical connectors per ISO 5356-1 and ISO 10651-4. Single-patient use; non-sterile; MR safe. Resistance < 1.2 cm H2O at 30 l/min and 15 l/min; volume < 80 ml; weight < 31 g.
Indications for Use
Indicated for adult and pediatric patients undergoing resuscitation to prevent the transmission of viruses or bacteria from patients receiving respiratory support.
Regulatory Classification
Identification
A breathing circuit bacterial filter is a device that is intended to remove microbiological and particulate matter from the gases in the breathing circuit.
Predicate Devices
Mercury Medical CPR Bag Exhalation Filter (K954490)
Submission Summary (Full Text)
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
April 30, 2026
Ambu A/S
% Sanjay Parikh
Senior Director, QA/RA
Ambu Inc.
6721 Columbia Gateway Drive
Suite 200
Columbia, Maryland 21046
Re: K251583
Trade/Device Name: Ambu® Virobac II® Exhalation Filter
Regulation Number: 21 CFR 868.5260
Regulation Name: Breathing Circuit Bacterial Filter
Regulatory Class: Class II
Product Code: CAH
Dated: August 22, 2025
Received: April 1, 2026
Dear Sanjay Parikh:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K251583 - Sanjay Parikh
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the
{2}
K251583 - Sanjay Parikh
Page 3
Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
**Dolly Singh** Digitally signed by Dolly Singh
For Katharine Segars, Ph.D.
Assistant Director
DHT4C: Division of Infection Control Devices
OHT4: Office of Surgical and Infection Control Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
# Indications for Use
Submission Number (if known)
K251583
Device Name
Ambu® Virobac II® Exhalation Filter
Indications for Use (Describe)
The Virobac II® Exhalation Filter is a viral/bacterial filter intended for use when the care provider desires to prevent the transmission of viruses or bacteria from patients receiving respiratory support.
Type of Use (Select one or both, as applicable)
☑ Prescription Use (Part 21 CFR 801 Subpart D)
☐ Over-The-Counter Use (21 CFR 801 Subpart C)
## CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
*DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
Department of Health and Human Services
Food and Drug Administration
Office of Chief Information Officer
Paperwork Reduction Act (PRA) Staff
PRAStaff@fda.hhs.gov
> "An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{4}
510(k) Summary – K251583
Date Prepared
30-April-2026
Company Name and Address
Ambu A/S
Baltorpbakken 13
DK-2750 Ballerup
Denmark
Tel: +45 7225 2000
Prepared and Submitted by:
Lenka Vaculčiaková
Regulatory Affairs Professional
Tel: +45 7225 2837
Email: leva@ambu.com
Official Contact:
Sanjay Parikh
Senior Director, QA/RA
Address: Ambu Inc.
6721 Columbia Gateway Drive, Suite 200
Columbia, Maryland 21046
Tel: +1 443 831 9844
Email: sap@ambu.com
Applicant Device
Trade Name: Ambu® Virobac II® Exhalation Filter
Common Name: Viral/Bacterial Filter
Classification Name: 21 CFR § 868.5260, Breathing circuit bacterial filter
FDA Product Code: CAH
Regulatory Class: II
Type of Submission: Traditional
Predicate Device
Trade Name: Mercury Medical CPR Bag Exhalation Filter
510(k) Number: K954490
This predicate has not been subject to a design-related recall, according to FDA's Medical Device Recall database.
Manufacturer Name: Mercury Medical Superior Solutions
Reference Device: No reference devices were used in this submission.
1. Device Description
The Ambu® Virobac II® Exhalation Filter is a stand-alone, non-sterile, single patient use viral/bacterial filter.
The Ambu® Virobac II® Exhalation Filter is intended for use when the care provider desires to prevent the transmission of viruses or bacteria from patients receiving respiratory support. The Ambu® Virobac II® Exhalation Filter is used in connection with a resuscitator to filter patient expiratory air during resuscitation. It connects to the resuscitator by a standard ISO conical connection and is comprised of a compact transparent housing with filter media.
Public
{5}
Page 2 of 4
2. Intended Use / Indications for Use
The Virobac II® Exhalation Filter is a viral/bacterial filter intended for use when the care provider desires to prevent the transmission of viruses or bacteria from patients receiving respiratory support.
3. Comparison of Technological Characteristics with the Predicate Device
| | Applicant (K251583)
Ambu® Virobac II® Exhalation Filter | Predicate Device (K954490)
Mercury Medical CPR Bag Exhalation Filter | Substantial equivalence assessment |
| --- | --- | --- | --- |
| | REGULATORY INFORMATION | | |
| Manufacturer | Ambu A/S | Mercury Medical Superior Solutions | N/A |
| Device trade name and model no. | Ambu® Virobac II® Exhalation Filter | Mercury Medical Exhalation Filter | N/A |
| Device depiction | | | N/A |
| 510(k) number | K251583 - application | K954490 | N/A |
| Product code | CAH | | Same |
| Regulation description | Filter, Bacterial, Breathing-Circuit | | Same |
| Regulation number | 868.5260 | | Same |
| Device Classification | Class II | | Same |
| | USE OF PRODUCT | | |
| Intended use/Indications for use | The Virobac II® Exhalation Filter is a viral/bacterial filter intended for use when the care provider desires to prevent the transmission of viruses or bacteria from patients receiving respiratory support. | The filter is intended to remove microbiological and particulate matter from the gases in the breathing circuit. | Equivalent to predicate (Ref. Note 1) |
| Target population | Adult and Pediatric patients undergoing resuscitation. | Not stated | Not stated for predicate (Ref. Note 2) |
| Device configuration | Straight | | Same |
Public
{6}
| | Applicant (K251583) Ambu® Virobac II® Exhalation Filter | Predicate Device (K954490) Mercury Medical CPR Bag Exhalation Filter | Substantial equivalence assessment |
| --- | --- | --- | --- |
| Rx Only | Yes | | Same |
| | TECHNOLOGICAL CHARACTERISTICS and SPECIFICATIONS | | |
| Principle of Operation | Electrostatic filtration method | | Same |
| Materials: - Housing - Filter | Housing: Methyl Methacrylate Butadiene Styrene
Filter media: Polypropylene fibers | Housing: Clear
Filter media: Proprietary spun polypropylene | Equivalent to predicate (Ref. Note 3) |
| Connectors | Standard conical connectors
ID 30 mm and OD 30 mm according to ISO 5356-1 and ISO 10651-4 (30 mm) | Standard conical connectors
30 mm I.D. (per ISO 5356-1) x 30 mm O.D. | Same |
| Delivered sterile | No | | Same |
| Device use designation | Single patient use | | Same |
| MR designation | MR safe | | Same |
| | GENERAL PERFORMANCE | | |
| Bacterial/ Viral Filtration Efficiency | BFE: ≥ 99.99%
VFE: ≥ 99.99% | BFE: 99.96% effective on particles with an approximate size of 3.1 microns
VFE: 99.81% effective on particles with an approximate size of 3.3 microns | Equivalent to predicate (Ref. Note 4) |
Note 1: Intended Use/Indications for Use
Both the applicant and predicate devices are designed to perform the same clinical function: the removal of microbiological and particulate matter. Both are used in similar clinical contexts (manual and mechanical ventilation) and are intended to reduce the risk of cross-contamination. The directions for use further confirm that the devices are functionally and operationally equivalent, explicitly listing the use on manual hand resuscitation exhalation ports. Therefore, the intended use is considered equivalent.
Note 2: Target population
There is no specified target population for the predicate device. However, based on the resuscitation catalog matrix by Mercury Medical, the Exhalation filter is being used together with ADULT, CHILD and INFANT BVM BAGS. Additionally, both applicant and predicate devices are attached to the expiratory port and thus do not contribute to mechanical dead space affecting gas exchange and ventilation efficiency. Therefore, specifying target population as 'adult and pediatric patients undergoing resuscitation' for the applicant device is considered equivalent to the predicate device.
Note 3: Materials
Both applicant and predicate devices use a multi-layered filter media material comprising of layers of polypropylene. The proprietary material of the predicate filter media is electrostatically charged to aid in attraction of particles. The applicant device has been tested to show viral filtration efficiency/bacterial filtration efficiency of at least 99.99%, which is similar to the efficiencies stated for the predicate device.
Public
{7}
The filter housings of both devices are comprised of clear, rigid plastic material with an upper and lower portion, thus considered equivalent. Methyl Methacrylate Butadiene Styrene material has enhanced clarity for aesthetic purposes and is commonly used in anesthesia devices.
# Note 4: Bacterial/ Viral Filtration Efficiency
Testing of the applicant device was performed by Nelson Laboratories, LLC. The particle size was $3.0 \pm 0.3$ $\mu \mathrm{m}$ . The applicant device complies with ISO 23328-1 and ASTM F2101 standards. The measured BFE and VFE are equivalent, or better than the predicate device.
# 4. Non-Clinical Tests Summary
| Test Standards | Test Performed | Acceptance Criteria | Results |
| --- | --- | --- | --- |
| ISO 23328-2 | Resistance | Resistance shall be less than 1.2 cm H2O at 30 l/min (0.5 L/sec) and 15 l/min (0.25 L/sec) | Pass |
| | Duration of Use | Resistance shall be less than 1.2 cm H2O at 30 l/min (0.5 L/sec) and 15 l/min (0.25 L/sec) | Pass |
| | Leak | Filter shall not leak more than 10 ml/min at 70 cm H2O ± 3.5 cm H2O | Pass |
| | Volume | Volume shall be less than 80 ml | Pass |
| N/A | Miscellaneous Inspections | No sharp edges. No visual defects. Presence of internal ribs preventing attachment to the ID of 30 mm OD connection. Flash ≤ 0.25 mm Internally and ≤ 0.50 mm Externally | Pass |
| | Weight | Weight shall be less than 31 g | Pass |
| ISO 5356-1 ISO 10651-4 | ISO connections | Connections shall meet ISO 5356-1 and ISO 10651-4 B.4.2 | Pass |
| ASTM F2101 | Bacterial/Viral Filtration efficiency | Product shall remove 99.99% of bacteria and viruses | Pass |
| ISO 23328-1 | NaCl Filtration | Product shall be tested according to ISO 23328-1: Salt test method to assess filtration performance. Testing shall be conducted prior to BFE/VFE testing. | Pass |
| ASTM D4169 | Transportation study | Product shall function after transport simulation using ASTM D4169 assurance level II | Pass |
# 5. Conclusions
Based on the intended use, technological characteristics and the non-clinical performance tests, the subject device demonstrates substantial equivalence to the predicate device.
Public
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.