The CuffGuard is an endotracheal tube cuff controller designed to continuously monitor and maintain user-defined endotracheal tube cuff pressure for patients (adults and pediatrics) who require mechanical ventilation and who are intubated with endotracheal tube including cuff in the ICU, OR and for intra-hospital transport.
Device Story
CuffGuard is an endotracheal tube cuff controller for ICU, OR, and intra-hospital transport use. Operated by trained physicians or nurses, it continuously monitors and automatically maintains user-defined cuff pressure. The device utilizes a pressure sensor and air pump to adjust cuff pressure via embedded software. It provides visual and audible alarms for leaks or pressure deviations. Output is displayed to the clinician to ensure cuff pressure remains within a safe, user-defined range (5–40 cmH2O), preventing complications associated with improper cuff inflation. The device is portable, powered by battery or AC, and intended for use on adult and pediatric patients.
Clinical Evidence
No clinical or animal studies were conducted. Substantial equivalence is supported by bench testing, including electrical safety (IEC 60601-1), electromagnetic compatibility (IEC 60601-1-2), and software verification and validation.
Technological Characteristics
Portable, software-controlled pressure controller. Features: pressure sensor, air pump, visual/audible alarms, battery/AC power. Pressure range: 5–40 cmH2O; control accuracy: +/- 2 cmH2O. Compliant with IEC 60601-1, IEC 60601-1-2, IEC 60601-1-6, and IEC 60601-1-8. No patient-contact materials.
Indications for Use
Indicated for adult and pediatric patients requiring mechanical ventilation who are intubated with an endotracheal tube. Contraindicated if the endotracheal tube itself is contraindicated.
Regulatory Classification
Identification
An inflatable tracheal tube cuff is a device used to provide an airtight seal between a tracheal tube and a patient's trachea.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
August 12, 2025
Idmed
Perrine Moelle
Quality & Regulatory Affairs Director
3 rue John Maynard Keynes
Marseille, 13013
France
Re: K243562
Trade/Device Name: CuffGuard
Regulation Number: 21 CFR 868.5750
Regulation Name: Inflatable Tracheal Tube Cuff
Regulatory Class: Class II
Product Code: BSK
Dated: July 7, 2025
Received: July 7, 2025
Dear Perrine Moelle:
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.
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"
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K243562 - Perrine Moelle
Page 2
(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 System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 systems (QS) regulation (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 Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic.
{2}
K243562 - Perrine Moelle
Page 3
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,
Bradley Q. Quinn -S
Bradley Quinn
Assistant Director
DHT1C: Division of Anesthesia, Respiratory, and Sleep Devices
OHT1: Office of Ophthalmic, Anesthesia, Respiratory, ENT, and Dental 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
Indications for Use
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
Submission Number (if known)
K243562
Device Name
CuffGuard
Indications for Use (Describe)
The CuffGuard is an endotracheal tube cuff controller designed to continuously monitor and maintain user-defined endotracheal tube cuff pressure for patients (adults and pediatrics) who require mechanical ventilation and who are intubated with endotracheal tube including cuff in the ICU, OR and for intra-hospital transport.
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}
idmed
an eye on your patient
# 510 (k) Summary
This summary of 510(k) information is being submitted in accordance with the requirements of 21 CFR 807.92.
# 1. Submitter
Submitter: IDMED
Hotel Technoptic
2 rue Marc Donadille
13013 Marseille France
+33 (0)974 980 541
Establishment Registration Number: N° DUNS 260233256
Contact person: Perrine MOLLE
Quality & Regulatory Affairs Director
E-mail : p.molle@idmed.fr
Date Summary Prepared: 2025/07/03
# 2. Device
Trade Name: CuffGuard (references CG-MU_ID and CG-MU_DR)
Common/Usual Name: Tracheal tube cuff Pressure Controller
Regulation Name: Inflatable tracheal tube cuff
Classification Regulation: 21 CFR 868.5750
Product Code: BSK
Regulatory Class: Class II
# 3. Predicate device
Predicate Device: Intellicuff, manufactured by Hamilton Medical, K150893
# 1.1. Device description
The CuffGuard is an endotracheal tube cuff controller designed to continuously monitor and maintain user-defined endotracheal tube cuff pressure for patients (adults and pediatrics) who require mechanical
510(k) - CuffGuard
{5}
idmed
an eye on your patient
ventilation and who are intubated with endotracheal tube including cuff in the ICU, OR and for intra-hospital transport.
It is used by health professionals (doctor or nurse) specifically trained in this tool.
The CuffGuard has a pressure sensor and software that can monitor and automatically adjust the cuff pressure.
The accessories associated include:
- Connection tube with filter
- Power supply
- Micro USB connection cable
- Fixation clamp and its tilt block)
At a high level, the comparison of the subject and predicate devices is based on the following table:
| Features | CuffGuard | Intellicuff |
| --- | --- | --- |
| Product code | BSK | BSK |
| Regulation number | 868.5750 | 868.5750 |
| Class | II | II |
| Indication for use | | |
| Intended use | The CuffGuard is an endotracheal tube cuff controller designed to continuously monitor and maintain user-defined endotracheal tube cuff pressure for patients (adults and pediatrics) who require mechanical ventilation and who are intubated with endotracheal tube including cuff. | The IntelliCuff device is intended to continuously measure and automatically maintain the user-set cuff pressure of an endotracheal tube (ETT) or tracheostomy tube (TT) during mechanical ventilation |
| Environment of use | In a professional health care setting such as hospital or health care facility: in an Intensive Care Unit, an Operating Room and during intra-hospital transportation. | Intensive care units, operating rooms, and during interhospital transport: - In the intensive care ward or in the recovery room - In the operation room during intubation narcosis - For emergency medical care or primary care - During transport within and outside of the hospital During transfer by rescue vehicles, ship, jet, or helicopter |
510(k) - CuffGuard
{6}
idmed
an eye on your patient
| Features | CuffGuard | Intellicuff |
| --- | --- | --- |
| Product code | BSK | BSK |
| Regulation number | 868.5750 | 868.5750 |
| Class | II | II |
| User | Health professional (doctor or nurse) specifically trained in this tool | Trained and qualified professionals under the supervision of a doctor and within the limits of the technical specifications indicated |
| Patient population | Adult and pediatric | Adults, pediatrics, and neonates, who are intubated with ETT or TT |
| Contraindication | None known.
Note that any contraindication to the use of the endotracheal tube will result in a contraindication to the use of the CuffGuard | None identified in the IFU |
| **Principle of operation and performances** | | |
| Principe of operation | Software-controlled pressure supervision and automatic pressure adjustment
Pressure sensor
Use of ambient / room air | Software-controlled pressure supervision and automatic pressure adjustment
Pressure sensor
Use of ambient / room air |
| Type of control | Automatic | Automatic |
| Pressure range | 5 – 40 cmH2O | 5 – 50 cmH2O |
| Accuracy of the control | +/- 2cmH2O | +/- 2cmH2O |
| Adjustment of accuracy | +/- 1cmH2O | +/- 1cmH2O |
| Display of accuracy | +/- 1cmH2O | +/- 1cmH2O |
| **Technology characteristics** | | |
| Leak alarm | Yes | Yes |
| Pressure alarm | Yes | Yes |
| Stop sound alarm | Yes | Yes |
| Audible alarm | Yes | Yes |
| Visual alarm | Yes | Yes |
| Deflate Cuff | Yes | Yes |
| Inflate Cuff | Yes | Yes |
| Time-limited hold | Yes | Yes |
| Choice of unit | Yes | Yes |
| Energy | Battery and AC power supply | Battery and AC power supply |
| Portable device | Yes | Yes |
510(k) – CuffGuard
5-3
{7}
idmed
an eye on your patient
| Features | CuffGuard | Intellicuff |
| --- | --- | --- |
| Product code | BSK | BSK |
| Regulation number | 868.5750 | 868.5750 |
| Class | II | II |
| General safety | Conpliant to IEC 60601-1, IEC 60601-1-2, IEC 60601-1-8 | Conpliant to IEC 60601-1, IEC 60601-1-2, IEC 60601-1-8, IEC 60601-1-12 |
| Biological characteristics | | |
| Patient contact material | NA, no patient contact | NA, no patient contact |
## 1.2. Indications for use
The CuffGuard is an endotracheal tube cuff controller designed to continuously monitor and maintain user-defined endotracheal tube cuff pressure for patients (adults and pediatrics) who require mechanical ventilation and who are intubated with endotracheal tube including cuff in the ICU, OR and for intra-hospital transport.
The following differences exist between subject and predicate device:
- The subject device is not indicated to be used on tracheostomy tube (TT)
- The subject device is not indicated to be used on neonate population of patient
- The subject device is not indicated to be used during transfer by rescue vehicles, ship, jet or helicopter
However, these differences do not raise questions of safety and effectiveness, because:
- the indication not applicable for the subject device (Tracheostomy tube),
- the population not applicable for the subject device (neonate),
- the environment of use not applicable for the subject device (transfer by rescue vehicles, ship, jet, or helicopter),
are not considered for the comparison.
The subject device and its predicate device are both used in the same clinical conditions or purposes (adult or pediatric patients requiring mechanical ventilation for whom the cuff pressure of an endotracheal tube (ETT) is monitored) and are used by the same kind of users (trained medical professional). They have the same principle of operation, using a pressure sensor and air pump).
## 4. Comparison of technological characteristics with the predicate device
The technological principle of the subject device is to maintain and automatically adjust thanks to embedded software, the cuff pressure of intubating tubes using a pressure sensor and a pump.
The following technological difference exists between subject device and its predicate device:
510(k) – CuffGuard
5-4
{8}
idmed
an eye on your patient
- The pressure range of the subject device is not as wide as its predicate device
However, this difference is supported by performance data (Software verification or safety test reports). Furthermore, this difference does not raise different questions of safety and effectiveness and does not negatively affect the clinical performances for the following reason:
- Difference of pressure range has been evaluated on the SW verification and validation. Furthermore, this difference is not clinically significant as the use of pressure range until 40 cm H2O appears as a realistic physiological limit and as a common clinical practice used as shown on various publications.
# 5. Performance data
The following performance data were provided in support of the substantial equivalence determination.
## Electrical safety and electromagnetic compatibility (EMC)
Electrical safety and EMC testing were conducted on the CuffGuard device. The system complies with the IEC 60601-1, IEC 60601-1-6 and IEC 60601-1-8 standards for safety and the IEC 60601-1-2 standard for EMC.
## Software Verification and Validation Testing
Software verification and validation testing were conducted and documentation was provided as recommended by FDA’s Guidance for Industry and FDA Staff, “Content of Premarket Submissions for Device Software Functions.” The documentation level for CuffGuard software is enhanced.
## Animal and Clinical Studies
No animal or clinical testing was required to demonstrate the substantial equivalence of this device to its predicate, nor its safety and effectiveness.
# 6. Conclusions
Based on its intended use, design principles, and technological characteristics, the CuffGuard device was found to be as safe, as effective, and performs comparably to the predicate device.
The technological differences identified do not raise new questions of safety and effectiveness as the non-clinical and clinical literature data support the safety of the device and the hardware and software verification and validation demonstrate that the CuffGuard device should perform as intended in the specified use conditions.
510(k) – CuffGuard
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.