DEN000004 · Maet Industries, Inc. · MZT · Feb 29, 2000 · Anesthesiology
Device Facts
Record ID
DEN000004
Device Name
QUICKAIR CHOKE RELIEVER, MODEL 59-001A
Applicant
Maet Industries, Inc.
Product Code
MZT · Anesthesiology
Decision Date
Feb 29, 2000
Decision
DENG
Submission Type
Post-NSE
Regulation
21 CFR 868.5115
Device Class
Class 2
Attributes
Therapeutic
Indications for Use
The Quickair Choke Reliever, Model 59-001A, is intended for use in relief of choking in acute upper airway obstruction in victims who weigh approximately 80 pounds or more.
Device Story
Quickair Choke Reliever is a mechanical device for emergency relief of foreign body airway obstruction. Device consists of a raised, rounded pad applied to the abdomen; user pushes pad upward to generate expulsion pressure to dislodge obstruction. Intended for over-the-counter use by lay persons. Device design must ensure generated pressure does not cause internal organ damage. Clinical benefit is the removal of airway obstructions in choking victims. Performance is evaluated against the Heimlich maneuver regarding pressure generation, distribution, and duration. Operational context involves emergency use by lay rescuers.
Clinical Evidence
No clinical data. Bench testing required includes static load, mechanical shock, fatigue, and intra-abdominal pressure simulation. Human factors testing required to demonstrate lay user ability to follow instructions regarding device placement and applied force across a range of rescuer and victim sizes.
Technological Characteristics
Mechanical device consisting of a raised, rounded pad. Operates via manual application of force to the abdomen to generate expulsion pressure. Design controls required to evaluate pressure generation, distribution, and duration compared to the Heimlich maneuver. No energy source or software.
Indications for Use
Indicated for relief of choking in acute upper airway obstruction in victims weighing approximately 80 pounds or more. Intended for over-the-counter use.
Regulatory Classification
Identification
The device is a raised, rounded pad that, in the event of choking on a foreign body, can be applied to the abdomen and pushed upward to generate expulsion pressure to remove the obstruction to relieve acute upper airway obstruction.
Special Controls
*Classification.* Class II (special controls) (“Class II Special Control Guidance Document for Acute Upper Airway Obstruction Devices”). The device is exempt from the premarket notification procedures in subpart E of part 807 of this chapter, subject to § 868.9.
Therefore, the Quickair Choke Reliever is subject to the following special controls which when combined with the general controls of the act, will provide reasonable assurance of the safety and effectiveness of the device:
1. Labeling that includes instructions for reporting complications resulting from the use of the device directly to the manufacturer, as well as any applicable medical device reporting requirements (21 CFR 803).
2. Labeling for the lay user that includes adequate instructions for use including (i) a clear identification of the minimum victim size threshold (weight), as well as any device-specific limitations identified through application of design controls and (ii) instructions for use of the Heimlich maneuver.
3. Design controls that satisfactorily evaluate:
- The potential for excessive generation and application of pressure to the abdomen that can result in damage to the internal organs. The generated pressures and their distributions over the abdomen should be assessed for safety and compared to the Heimlich maneuver in a variety of victim sizes and user strengths;
- the initial and peak airway pressures and the duration of pressure application of the device as compared to the Heimlich maneuver;
- bench testing to include static load, mechanical shock, fatigue and intraabdominal pressure simulation; and
- human factors testing to demonstrate that the lay user is able to understand and follow the device instructions for use with respect to device placement and applied force. The testing should include a range of rescuer’s sizes, ages and educational levels, as well as an appropriate range of victim size and position.
Submission Summary (Full Text)
{0}
DEPARTMENT OF HEALTH & HUMAN SERVICES
Public Health Service
Food and Drug Administration
9200 Corporate Boulevard
Rockville MD 20850
# FEB 29 2000
Mr. Michael Chao
Maet Industries, Inc.
4215 Renoak Court
Mississauga, Ontario
Canada
Re: K993284- Evaluation of Automatic Class III Designation
Device Name: Quickair Choke Reliever, Model 59-001A
Classification Regulation: 21 CFR 868.5115
Regulatory Class: Class II, Exempt from Premarket Notification Requirements
Product Code: MZT
Dear Mr. Chao:
The Center for Devices and Radiological Health (CDRH) of the Food and Drug Administration (FDA) has completed its review of your petition for classification of the Quickair Choke Reliever, Model 59-001A, that is intended for use in relief of choking in acute upper airway obstruction in victims who weigh approximately 80 pounds or more. FDA concludes that this device, and substantially equivalent devices of this generic type, should be classified into class II, exempt from premarket notification. This order, therefore, classifies the Quickair Choke Reliever, and substantially equivalent devices of this generic type into class II under the generic name, Devices to Relieve Acute Upper Airway Obstruction.
FDA identifies this generic type of device as an anesthesiology device under 21 CFR 868.5115. This generic type of device is for over the counter use and consists of a raised, rounded pad that, in the event of choking on a foreign body, can be applied to the abdomen and pushed upward to generate expulsion pressure to remove the obstruction.
In accordance with section 513(f)(1) of the Federal Food, Drug, and Cosmetic Act (21 U.S.C. 360c(f)(1)) (the act), devices that were not in commercial distribution prior to May 28, 1976 (the date of enactment of the Medical Device Amendments of 1976 (the amendments)), generally referred to as postamendments devices, are classified automatically by statute into class III without any FDA rulemaking process. These devices remain in class III and require premarket approval, unless and until the device is classified or reclassified into class I or II or FDA issues an order finding the device to be substantially equivalent, in accordance with section 513(i) of the act
{1}
Page 2 - Mr. Michael Chao
(21 U.S.C. 360c(i)), to a predicate device that does not require premarket approval. The agency determines whether new devices are substantially equivalent to previously marketed devices by means of premarket notification procedures in section 510(k) of the act (21 U.S.C. 360(k)) and Part 807 of the FDA regulations (21 CFR 807). Section 513(f)(2) of the act provides that any person who submits a premarket notification under section 510(k) for a device may, within 30 days after receiving an order classifying the device in class III under section 513(f)(1), request FDA to classify the device under the criteria set forth in section 513(a)(1). FDA shall, within 60 days of receiving such a request, classify the device. This classification shall be the initial classification of the device. Within 30 days after the issuance of an order classifying the device, FDA must publish a notice in the Federal Register classifying the device.
On January 28, 2000, FDA filed your petition requesting classification of the Quickair Choke Reliever into class I or II. The petition was submitted under section 513(f)(2) of the act. In accordance with section 513(f)(1) of the act, FDA issued an order on December 29, 1999 automatically classifying the Quickair Choke Reliever in class III, because it was not within a type of device which was introduced or delivered for introduction into interstate commerce for commercial distribution before May 28, 1976, which was subsequently reclassified into class I or class II. In order to classify the Quickair Choke Reliever into class I or II, it is necessary that the proposed class have sufficient regulatory controls to provide reasonable assurance of the safety and effectiveness of the device for its intended use.
After review of the information submitted in the petition, FDA has determined that the Quickair Choke Reliever, intended in the event of choking to remove a foreign body airway obstruction through generation of expulsion pressure, can be classified in class II with the establishment of special controls. FDA believes that special controls, when combined with general controls, in particular the design control requirements outlined in 21 CFR 820.30, provide reasonable assurance of the safety and effectiveness of the device.
FDA has identified two risks to health associated with this type of device. These risks involve; 1) incorrect use resulting in damage to the internal organs of the thorax and/or the abdomen, and 2) faulty device design that generates and applies too much pressure to the abdomen resulting in patient injury. Therefore, the Quickair Choke Reliever is subject to the following special controls which when combined with the general controls of the act, will provide reasonable assurance of the safety and effectiveness of the device:
1. Labeling that includes instructions for reporting complications resulting from the use of the device directly to the manufacturer, as well as any applicable medical device reporting requirements (21 CFR 803).
{2}
Page 3 - Mr. Michael Chao
2. Labeling for the lay user that includes adequate instructions for use including (i) a clear identification of the minimum victim size threshold (weight), as well as any device-specific limitations identified through application of design controls and (ii) instructions for use of the Heimlich maneuver.
3. Design controls that satisfactorily evaluate:
- The potential for excessive generation and application of pressure to the abdomen that can result in damage to the internal organs. The generated pressures and their distributions over the abdomen should be assessed for safety and compared to the Heimlich maneuver in a variety of victim sizes and user strengths;
- the initial and peak airway pressures and the duration of pressure application of the device as compared to the Heimlich maneuver;
- bench testing to include static load, mechanical shock, fatigue and intraabdominal pressure simulation; and
- human factors testing to demonstrate that the lay user is able to understand and follow the device instructions for use with respect to device placement and applied force. The testing should include a range of rescuer’s sizes, ages and educational levels, as well as an appropriate range of victim size and position.
Section 510(m) of the act provides that FDA may exempt a class II device from the premarket notification requirements under section 510(k) of the act, if FDA determines that premarket notification is not necessary to provide reasonable assurance of the safety and effectiveness of the device. FDA has determined premarket notification is not necessary to provide reasonable assurance of the safety and effectiveness of this generic type of device, and therefore, the device type is exempt from the premarket notification requirements. Thus, persons who intend to market a device of this type do not need to submit a premarket notification to FDA and receive agency clearance prior to marketing the device.
A notice announcing this classification order will be published in the Federal Register. A copy of this order and supporting documentation are on file in the Dockets Management Branch (HFA-305), Food and Drug Administration, 12420 Parklawn Dr., rm. 1-23, Rockville, MD 20857 and are available for inspection between 9 a.m. and 4 p.m., Monday through Friday.
{3}
Page 4 - Mr. Michael Chao
As a result of this order, you may immediately market this device, subject to the general control provisions of the act and the special controls identified in this order.
If you have any questions concerning this classification order, please contact Carroll O'Neill at (301) 443-8262 extension 170.
Sincerely,
Philip J. Phillips
Deputy Director for Science and Regulatory Policy
Office of Device Evaluation
Center for Devices and Radiological Health
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.